Commercial SaaS starter
Makerkit Alternative: build SaaS with source-owned modules.
Compare Makerkit with StackFoundry when you want production SaaS modules as editable source instead of a paid all-in-one starter.
Teams that want a broad, opinionated SaaS app foundation with many decisions made up front.
What Makerkit is known for
Next.js and Remix starter paths
Supabase or Firebase-backed app foundations
Auth, organizations, billing, docs, blog, and testing guidance
A paid template license model
Where StackFoundry differs
Free to use and MIT-licensed with no paid template license fee
Installs modules into an existing app instead of asking you to adopt a whole starter
Leads with the API SaaS recipe: keys, usage, credits, billing, docs, and webhooks
Keeps providers as adapters around source-owned product systems
When to choose StackFoundry instead
You like the SaaS category coverage but want smaller source modules, recipe dry-runs, and normal code review before anything lands in your app.
Makerkit alternativeMakerkit free alternativeNext.js SaaS starter
Source Registry
Dry-run a complete SaaS recipe before adopting any app shape.
Start with API SaaS, inspect the exact source files, then decide whether the modules belong in your app.
pnpm stackfoundry add recipe api-saas-starter --target ./my-app --dry-run