Marketing Site
Public site with pricing, SEO structure and i18n, connected to the product catalog.
A production-ready SaaS foundation with authentication, billing, admin tools, a customer web app, .NET APIs, testing and deployment workflows already structured.
Start with the parts that make your product unique — the rest is already structured.
Three frontends, one API and the operational plumbing between them.
Public site with pricing, SEO structure and i18n, connected to the product catalog.
Authenticated customer area: dashboard, plan, usage and billing foundation.
Operate products, plans, features, users, subscriptions and PSPs.
.NET 8 API with EF Core, PostgreSQL and versioned endpoints.
Supabase-backed auth with sessions and protected routes across apps.
Products, plans and catalog managed from the admin panel.
Plans, feature flags and plan-feature bindings ready to model your offer.
Stripe and Paddle wired end to end: checkout, signed webhooks and entitlements, with checkout binding per plan.
Locale routing, translation files and language selectors in every frontend.
Unit tests with Vitest on frontends and test structure on the API.
Vercel-ready frontends and a containerized API you can deploy anywhere.
Branding, product, pricing and features driven by config files.
Domestic customers are charged through Stripe. Everyone else goes through Paddle as merchant of record, so VAT and sales tax are handled for you.
Every app has a single responsibility, and shared concerns live in one place.
apps/Three frontends with the same design language: marketing, customer app and admin.
api/.NET 8 backend — products, plans, features, users, subscriptions and payment providers.
config/branding.json, product.json, pricing.json and features.json drive the whole product.
shared/ · docs/ · scripts/Conventions, documentation and automation shared by every project.
No exotic dependencies. Proven tools, typed end to end.
Branding, product, pricing and features are centralized configuration — not scattered constants.
One monorepo with frontends, API, database and scripts.
Set name, colors and locale in config/branding.json.
Model plans and features from the admin panel or config files.
Plug in Supabase credentials and your Stripe and Paddle keys — the integrations are already built.
Spend your time on the product, not on the boilerplate.
Ship to Vercel or any host you choose — no lock-in.
{
"productName": "Your SaaS",
"defaultLocale": "en-US",
"currency": "USD"
}Your purchase includes a 15-step onboarding trail - in English, Spanish, and Portuguese - that takes you from an unopened package to a deployed product taking real payments. Every step ends with a verifiable check, written to be executed with an AI coding agent.
Different goals, same starting point.
Validate your idea with a real product surface instead of a prototype.
Skip the plumbing and work on features that differentiate.
Deliver client SaaS projects with a professional baseline from day one.
Standardize how your team starts every SaaS engagement.
Launch internal tools with auth, admin and billing structure ready.
Reuse the same foundation across multiple products without re-learning it.
Grouped by the areas that matter when you're shipping.
Same design system, different jobs.
Sell the product: hero, pricing and SEO-ready pages.
Simple, value-oriented area for the end customer.
Dense, operational cockpit for whoever runs the SaaS.
Product identity and commercial rules live in versioned config files.
{
"productName": "Your SaaS",
"defaultLocale": "en-US",
"currency": "USD"
}{
"plans": [
{
"name": "Starter",
"price": 29
}
]
}Illustrative examples — check the repository for the exact configuration contracts.
Plans come straight from the product catalog — manage them in the admin panel.
Template completee
Continuous access to SaaS Core updates, improvements, bug fixes, and new modules. Cancel anytime — your purchased version remains yours.
Licensing terms are summarized on the license page
No. It's a code-first foundation for developers: a monorepo with React frontends, a .NET API and configuration files you own and extend.
Get the foundation and spend your first week on what makes your product different.