Built for Safety, Designed for Scale
BOB ORBIT runs independently — it can't break what it doesn't touch
3-Layer Architecture
The Revenue Engine
The Bridge
Shadow DB
Read-only replica
Sync Schedule
Every 6 hours
Method
PostgreSQL streaming
Safety
Auto-pause if latency >100ms
Unchanged & Protected
The Kill Switch
One environment variable. 60 seconds to full shutdown. Zero impact to core.
# To shut down BOB ORBIT:BOB_ORBIT_ENABLED=false# To restart:BOB_ORBIT_ENABLED=true
<60s
Full shutdown
Zero
Core impact
No
Code changes
Failure Scenarios
Shadow DB Sync Fails
Impact
Tags become stale (>6 hours old)
Response
Auto-pause new campaigns, send alert
Vercel Edge Outage
Impact
Brand dashboards unavailable
Response
Static fallback page served
Attribution Engine Bug
Impact
Incorrect order attribution possible
Response
Manual audit queue activated
ML Model Crash
Impact
No new tags generated
Response
Use last-known tags, restart model
Tech Stack
Frontend
- Astro (Static site generation)
- React + shadcn/ui + TailwindCSS
- Recharts (Data viz)
- Vercel Edge deployment
Backend
- Next.js API Routes (Serverless)
- Clerk (Auth)
- Upstash Redis (Rate limiting)
- Inngest (Webhooks)
Data
- Supabase (Postgres + Vector)
- PostgreSQL Read Replica
- Cloudflare KV (Cache)
- PostHog (Analytics)
Monitoring
- Axiom (Logs)
- Vercel Analytics + Grafana
- PagerDuty (Alerts)
- 99.9% SLA Uptime
Performance Metrics
<50ms
API Response
<2s
Dashboard Load
<30s
Attribution Time
2.3 hrs (avg)
Shadow DB Lag
99.9%
Uptime SLA
41 global
Edge Locations
Why Sidecar Wins
| Aspect | Integrated | Sidecar (BOB ORBIT) |
|---|---|---|
| Risk to Core | ! High | ✓ Zero |
| Deployment Time | 2-4 weeks | 48 hours |
| Downtime Required | ✓ Yes | ✕ No |
| Rollback Complexity | ! High | ✓ One button |
| Scaling | ! Coupled | ✓ Independent |
| Infrastructure Cost | ! Shared | ✓ Separate billing |