VerdantStack

Three maintained SvelteKit starters for teams shipping multi-tenant B2B.

The boring 80% of a B2B app — organizations, roles, invites, seat billing and an append-only audit log — verified absent from every free alternative we checked, at the schema level. Three databases to pick from: Cloudflare D1/SQLite, Supabase, or any Postgres.

The Postgres starter running on a real database: an organization dashboard listing Northwind Labs with its role, member count and seat state.This is the Postgres demo, running — click to open it.

What you can check before you buy

Three demos run on real infrastructure against a real database, reset daily. The clip below is the Postgres demo refusing a member a request its role does not allow — the same code path a paying customer runs.

  • 1438 automated tests across the three kits (475 + 509 + 454). Re-measured 2026-10-21: 100% of statements, functions and lines in all three, and 100% of branches in two of them — 99.26% in the Postgres kit. That figure covers the server domain layer, src/lib/server/** minus the handful of wiring files each kit excludes, so route handlers are not in the metric and we are not claiming they are.
  • Docs, API reference and architecture notes are public in the GitHub repos — source code is not.
  • A dated changelog — 46 releases, parsed from the kits' own release files, not typed by hand.
  • 30-day refund, no questions asked.

Included for AI coding agents

Every starter ships an AGENTS.md describing its own architecture, commands, and conventions, plus a TypeDoc API reference generated from the source, so tools like Claude Code, Cursor, and Copilot work from the real surface instead of guessing. These files are here because they cost nothing to include and make the kit more usable — not because they are unusual. Svelte's own CLI (npx sv add ai-tools) scaffolds a framework-level AGENTS.md into any SvelteKit project; ours is the product-specific layer on top of that.

AGENTS.md

Ships in every kit — architecture, commands, and conventions for that codebase

TypeDoc API ref

Generated, compiler-verified — never drifts from the code

llms.txt

Site-level index — every guide, comparison, and doc URL, machine-readable

Service layer map

How orgs → members → invites → RBAC → billing → audit fit together, and which layer owns what

Read the guide: Make your codebase AI-agent-friendly

What's shipped

Documentation & guides

Why buy when AI can generate?

An agent will happily write your tenant-isolation policy, your seat gate, and your audit writer in an afternoon. What it cannot tell you is whether they are right — whether a policy that reads tight still leaks a row across tenants, whether a retried billing webhook charges a seat twice, whether anyone can mutate the audit trail. Those are the parts that are slow to review and expensive to be wrong about, and the failure is yours, not the model's. These kits ship that layer already wired and covered, so the thing you build on is the risky part instead of a fresh copy of it.

If wiring it up yourself would take you a few weeks — your own estimate, not ours — it pays for itself before you write a line of your own product.

Why not a free starter?

Free starters are good, and one of them is probably the first thing you found. The difference shows up after you build on it: dependencies get CVEs, framework majors land, and a kit that stopped shipping is a kit you maintain yourself. These kits have shipped46 dated releasessince 26 August 2026 — a count parsed from the kits' own release files at build time, with every release listed where you can read it. Lifetime updates and 12 months of support are included with a purchase; the changelog is how you hold that promise to account, and it exists for exactly that reason. If you want the full answer to "what is a SvelteKit SaaS boilerplate actually made of" — the layers the free ones leave out, and what each one costs to build —that is written up here.

The free alternative most people compare against,CMSaasStarter, has no tagged release, and at the last check behind this page (2026-10-02) its most recent commit was dated 21 March 2026. Check the link rather than trusting the sentence — if it has shipped since, this paragraph is wrong and the link is how you would know.

Status, stated plainly

No countdowns, no pre-orders, no invented traction. Every product above is shipped, live with a working demo and instant download after purchase. If a problem above is yours, buy the product directly or reach out with questions — we aim to respond within 48 hours.

Get in touch

Questions about the product, team licenses, or anything else? We'll aim to respond within 48 hours.

Max 2000 characters

Stored in our own database — no third party. Deleted on request.

Not buying yet? Get told when something new lands.

Every guide, comparison and changelog entry published on this site is written about a real implementation decision — multi-tenancy, seat billing, audit logs, RLS, deploys. Leave an address and you get a message when a new one is published. Nothing else, and no schedule to keep up with.

Stored in our own database — no third party, no newsletter service. Deleted on request.

Currently VerdantStack publishes by hand, so this is occasional rather than scheduled. That is why no cadence is promised above.