Production-ready SaaS foundation

Build your SaaS on a foundation made to ship.

A production-ready SaaS foundation with authentication, billing, admin tools, a customer web app, .NET APIs, testing and deployment workflows already structured.

React + TypeScript.NET 8 APIi18n includedCI/CD ready
Marketing SitePublic pages, pricing and SEO
Web ApplicationCustomer area with auth and billing
.NET APIProducts, plans, features and payments
Database · Auth · PaymentsPostgreSQL, Supabase, Stripe + Paddle
Admin PanelOperate products, plans and PSPs
Why a foundation

Stop rebuilding the same SaaS foundation.

Start with the parts that make your product unique — the rest is already structured.

Starting from scratch

  • Design, build and test authentication
  • Design, build and test session handling
  • Design, build and test admin structure
  • Design, build and test product and pricing models
  • Design, build and test global payments with two providers
  • Design, build and test internationalization
  • Design, build and test tests
  • Design, build and test ci/cd
  • Design, build and test deployment structure
  • Design, build and test documentation

Starting with SaaS Core

  • Authenticationalready structured
  • Session handlingalready structured
  • Admin structurealready structured
  • Product and pricing modelsalready structured
  • Global payments with two providersalready structured
  • Internationalizationalready structured
  • Testsalready structured
  • CI/CDalready structured
  • Deployment structurealready structured
  • Documentationalready structured
What's inside

Every layer of a real SaaS, already in place.

Three frontends, one API and the operational plumbing between them.

Marketing Site

Public site with pricing, SEO structure and i18n, connected to the product catalog.

Included

Customer Web App

Authenticated customer area: dashboard, plan, usage and billing foundation.

Included

Admin Panel

Operate products, plans, features, users, subscriptions and PSPs.

Included

.NET API

.NET 8 API with EF Core, PostgreSQL and versioned endpoints.

Included

Authentication

Supabase-backed auth with sessions and protected routes across apps.

Included

Product Management

Products, plans and catalog managed from the admin panel.

Included

Pricing & Features

Plans, feature flags and plan-feature bindings ready to model your offer.

Included

Payment Providers

Stripe and Paddle wired end to end: checkout, signed webhooks and entitlements, with checkout binding per plan.

Included

Internationalization

Locale routing, translation files and language selectors in every frontend.

Included

Automated Testing

Unit tests with Vitest on frontends and test structure on the API.

Included

Deployment

Vercel-ready frontends and a containerized API you can deploy anywhere.

Included

Centralized Configuration

Branding, product, pricing and features driven by config files.

Extensible
Global billing

Sell worldwide without a local entity in every market.

Domestic customers are charged through Stripe. Everyone else goes through Paddle as merchant of record, so VAT and sales tax are handled for you.

  • Country-to-provider routing rule, configured in the admin panel
  • Signed webhooks from both providers unlock the same entitlements
  • One checkout endpoint — the API resolves which provider to use
Buyer's countryConfirmed at checkout
Routing ruleDomestic, international, fallback
StripeYour domestic account
PaddleMerchant of record
Webhook → accessEntitlement granted
Architecture

One monorepo. Clear boundaries.

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.

Explore the full architecture
Stack

A stack teams already know.

No exotic dependencies. Proven tools, typed end to end.

Frontend

ReactViteTypeScriptReact Routeri18nextVitest

Backend

.NET 8C#EF CorePostgreSQLSupabase Auth

Quality & Infra

Automated TestsVercelMigrationsEnv Config
How it works

From clone to deploy, without detours.

Branding, product, pricing and features are centralized configuration — not scattered constants.

Clone the foundation

One monorepo with frontends, API, database and scripts.

Configure your brand

Set name, colors and locale in config/branding.json.

Define products and pricing

Model plans and features from the admin panel or config files.

Connect auth and payments

Plug in Supabase credentials and your Stripe and Paddle keys — the integrations are already built.

Build your unique experience

Spend your time on the product, not on the boilerplate.

Deploy

Ship to Vercel or any host you choose — no lock-in.

config/branding.json
{
  "productName": "Your SaaS",
  "defaultLocale": "en-US",
  "currency": "USD"
}
Guided onboarding

A guided path from zero to your first payment

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.

Who it's for

Built for people who ship SaaS.

Different goals, same starting point.

Solo founders

Validate your idea with a real product surface instead of a prototype.

SaaS developers

Skip the plumbing and work on features that differentiate.

Freelancers

Deliver client SaaS projects with a professional baseline from day one.

Software agencies

Standardize how your team starts every SaaS engagement.

Internal product teams

Launch internal tools with auth, admin and billing structure ready.

Serial builders

Reuse the same foundation across multiple products without re-learning it.

In detail

What the foundation covers.

Grouped by the areas that matter when you're shipping.

Monorepo structure
Shared conventions
Centralized configuration
Documentation
Preview

Three frontends, one visual language.

Same design system, different jobs.

Marketing Site

Sell the product: hero, pricing and SEO-ready pages.

Customer Web App

Simple, value-oriented area for the end customer.

Admin Panel

Dense, operational cockpit for whoever runs the SaaS.

Extensibility

Change configuration, not scattered code.

Product identity and commercial rules live in versioned config files.

config/product.json
{
  "productName": "Your SaaS",
  "defaultLocale": "en-US",
  "currency": "USD"
}
config/pricing.json
{
  "plans": [
    {
      "name": "Starter",
      "price": 29
    }
  ]
}

Illustrative examples — check the repository for the exact configuration contracts.

Pricing

One foundation. Pick your license.

Plans come straight from the product catalog — manage them in the admin panel.

SaaS Core

Pacote completo

Template completee

$347 one-time purchase
SaaS Core Updates

Updates

Continuous access to SaaS Core updates, improvements, bug fixes, and new modules. Cancel anytime — your purchased version remains yours.

$7 /month

Licensing terms are summarized on the license page

FAQ

Frequently asked questions

No. It's a code-first foundation for developers: a monorepo with React frontends, a .NET API and configuration files you own and extend.

Your next SaaS should start with the product — not the boilerplate.

Get the foundation and spend your first week on what makes your product different.