Architecture

A monorepo designed for clarity.

How the apps, the API and the configuration layer fit together.

saas-core/

├─ apps/

│ ├─ marketing-site/ # Next.js

│ ├─ web-app/ # React + Vite

│ └─ admin-panel/ # React + Vite

├─ api/ # .NET 8

├─ config/

│ ├─ branding.json

│ ├─ product.json

│ ├─ pricing.json

│ └─ features.json

├─ database/

├─ docs/

├─ scripts/

└─ shared/

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.

How a request flows

From the public site to the operational panel.

Marketing SiteVisitor lands, sees pricing from the catalog

Web ApplicationCustomer signs up and uses the product

.NET APISingle source of truth for catalog, users and billing

Database · Auth · PaymentsPostgreSQL, Supabase Auth, Stripe and Paddle

Admin PanelOperators configure products, plans and providers

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"
}

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.

Get SaaS Core View Documentation