WHO IT IS FOR
Same codebase.
Five reasons you are here.
The base does not change. What changes is which part of it saves you the most time — so start from the one that sounds like your week.
For AI-native developers
SaaS Boilerplate for Claude Code & Cursor Agents
Compiler-enforced DDD boundaries and typed end-to-end contracts your AI agent can't cross — so Claude Code and Cursor ship features without breaking auth, billing, or tenant isolation. Harness-ready: E2E Playwright gate, DDD boundaries lint-enforced.
For LATAM builders
SaaS Boilerplate with Native MercadoPago (+ Stripe & Polar)
The serious SaaS boilerplate with MercadoPago built in — recurring subscriptions (preapproval), signed async webhooks, and idempotency already solved. Stripe and Polar too. Real EN/ES/PT docs. Charge in pesos, reais, or MXN.
From prototype to production
From Mockup to Production: A SaaS Base That Won't Leak
Your AI agent got you to 80%. The last 20% — real auth, payments, security, multi-tenant — is where vibe-coded apps break and leak. Here it is already built, locked down, and CI-tested. Point your agent at this, not a blank repo.
For agencies & freelancers
Multi-Tenant SaaS Boilerplate for Agencies — Reuse It on Every Client
Workspace isolation, role-based permissions, per-organization billing, API keys — the week-of-work-each parts, already built and tested. Deliver faster, charge the same, and never ship insecurity under your client's name.
For rescue & due-diligence shops
Rebuild a Vibe-Coded App on a Base That Passes Due Diligence
Inherited an AI-built app with exposed keys, no idempotency, and RLS gaps? Don't patch the loop — rebuild on a DDD-layered, E2E-tested, typed-contract foundation with an audit-friendly event bus and observability. The rebuild target, not another rescue.