Architecture
Hosting, servers, services, data flow, and domain flow.
System Map
Vercel
Supabase
Hetzner
Redis
OpenRouter
OpenAI
DeepSeek
Stripe
Cloudflare
Telegram
Venture Factory Flow
idea→
venture genome→
trial page→
share→
feedback→
upgrade→
build workers→
launch support
Vercel
Public edge & dashboards
- • Public website
- • Dashboard
- • Pricing
- • Docs
- • Trial pages
Supabase / Postgres
Data & auth layer
- • Users & workspaces
- • Startup pages
- • Credits & referrals
- • Waitlists & feedback
- • Support data
Hetzner
Worker factory
- • Job queues
- • Telegram bot
- • Repo/build workers
- • Monitoring & logs
Redis
Queue & limits
- • Job queue
- • Rate limits
OpenRouter / OpenAI / DeepSeek
Model routing
- • Model routing
- • AI generation
- • Replaceable providers
Stripe
Billing
- • Plans
- • One-time passes
- • Subscriptions
- • Sprints
Cloudflare
DNS & domains
- • DNS
- • Wildcard subdomains
Telegram
Intake channel
- • Voice/text startup idea intake
System overview
AutoBuilder spans Vercel (edge), Supabase (data), Hetzner (workers), Redis (queue), AI providers, Stripe, Cloudflare, and Telegram.
User data flow
User submits idea → venture data → trial page → share → feedback/waitlist → credits/plan gates → paid workers.
- Structured venture genome in database
- Trial page renders from DB
- Upgrade unlocks deeper execution
What runs on Vercel
Public website, dashboard, pricing, docs, trial pages, Blitz HQ.
What runs on Supabase
Users, workspaces, pages, credits, referrals, waitlists, feedback, support.
What runs on Hetzner
Worker factory, queues, Telegram bot, repo/build workers, monitoring.
What runs in the worker queue
Scored jobs by priority lane; limited concurrent actives.
What must NOT run for free users
No repo read, patch, deploy, browser test, or expensive worker runs.
- Hard plan gates
- Admin kill switch for free generation