One-shot code, not governed modules
Output is a generated codebase with no module.json, no lockfile, no contract enforcing that the Stripe webhook is structured correctly. When it fails in production there's no safety gate or recovery path built in.
microservices.sh vs AI app builders
Lovable, v0, Bolt, and Replit are remarkable at turning a prompt into a working, deployed app fast. That's the first 70%. The last 30% — idempotent Stripe webhooks, token rotation, audit trails, tenant isolation — is what decides whether the app survives production, and it's delegated to whatever the model happened to generate.
Compared against: Lovable, v0, Bolt, Replit
Credit where due
The gap
Output is a generated codebase with no module.json, no lockfile, no contract enforcing that the Stripe webhook is structured correctly. When it fails in production there's no safety gate or recovery path built in.
Auth, payments, and audit are whatever the model wrote that session. No verification that token rotation is correct or that the audit log satisfies a security review.
Vercel, Supabase, or container infra — not Cloudflare Workers. No Workers-for-Platforms multi-tenant dispatch. Moving off means abandoning the workflow.
Side by side
| AI app builders | microservices.sh | |
|---|---|---|
| Output | One-shot generated codebase | Versioned, governed modules |
| Optimized for | Demo day (the first 70%) | Audit day (the production 30%) |
| Production parts | Whatever the model generated | Verified auth/webhooks/audit by contract |
| Runtime | Vercel / Supabase / containers | Cloudflare Workers / D1 |
| Upgrades | Re-prompt and hope | Reviewable lockfile upgrade |
| Relationship | Generates the app | Governs the infra under it — plug in via MCP |
You need the fastest possible path to a working prototype or to validate an idea.
You're taking an AI-built app to real customers and need the auth/payments/audit/tenant layer to be verified, not improvised.
AI app builders get you to demo day; modules get you through audit day — the idempotent webhook, the SOC2 audit log, the tenant isolation. Not mutually exclusive: microservices.sh can be the infrastructure layer their generated apps plug into.