How cloudflare/vibesdk works
Project Type & Purpose
• This is an open-source, full-stack AI webapp generator (“Cloudflare VibeSDK”).
• Frontend: React + Vite + TypeScript + Tailwind SPA.
• Backend: Cloudflare Workers + Durable Objects + REST/WebSocket API.
• Database: D1 (SQLite via Drizzle ORM), KV, R2.
• AI: Multi-model calls via AI Gateway.
• Sandboxed containers: live app previews & builds.
• CI/CD: bun scripts, GitHub Actions, Wrangler deploy.
File Structure & Architectural Indicators
• Top-level:
• src/ → Frontend code (App.tsx, routes, components, hooks, contexts)
• public/, index.html → Static assets
• worker/ → Serverless backend (api controllers, routes, services, middleware, durable objects, database)
• container/ → Scripts & types for sandboxed containers (CLI, storage, monitoring)
• shared/types → Cross-cutting TS definitions
• migrations/ & drizzle.config.*.ts → DB schema & migrations
• scripts/ → deploy.ts, setup.ts, undeploy.ts
• wrangler.jsonc → Cloudflare Workers configuration
• Backend layering: controllers → routes → services → database → durable objects.
• Use of middleware for auth, rate-limiting, security.
• Debug-tools/ for analytics and testing.
Key README Insights
• Durable Objects manage stateful AI agents.
• Workers for Platforms dispatch namespace serves generated apps.
Components
A. Frontend SPA
• Browser
• React/Vite app (src/)
• API client & WebSocket client
B. Cloudflare Edge Layer
• Workers HTTP/API layer (worker/app.ts)
• Durable Objects cluster (CodeGeneratorAgent, etc.)
• Middleware (auth, security, rate-limit)
C. Services & Data Stores
• D1 via Drizzle ORM (migrations + services)
• KV (sessions, rate-limit store)
• R2 (templates, assets)
• AI Gateway (external LLM providers)
D. Container Sandbox Cluster
• Container service (container/*)
• Build & runtime environments for live previews
• Monitor & storage service
E. Worker for Platforms Dispatcher
• Dispatch namespace routing to user-deployed apps
F. External Integrations
• GitHub OAuth & Export
• Google/GitHub OAuth for login
• Cloudflare APIs (Workers, Durable Objects, R2, KV)
Relationships & Data Flows
• User → Frontend (HTTP, WS) → Workers API
• Workers API → Durable Objects (WebSocket)
• Durable Objects → AI Gateway (LLM calls)
• Controllers → Services → D1/KV/R2
• API triggers sandbox service → spin up container → R2 asset store
• Live preview served via Workers for Platforms / Dispatch
• User feedback loops back through WebSocket to agents
• Deploy action → Deployer service → Cloudflare Workers for Platforms or GitHub
Architectural Patterns & Principles
• Layered MVC-style backend
• Stateful agents via Durable Objects
• Micro-service style “services” directory
• Domain-driven agent workflows (planning, codegen, QA phases)
• Event-driven & streaming (WebSocket, NDJSON)
• Infrastructure as code (wrangler.jsonc, scripts)
• CI/CD automation via GitHub Actions & bun scripts