OpenSaaS Svelte

OpenSaaS Svelte is proof that you don’t need to pay $149+ for a solid SaaS starter. Built on Better Auth — the new kid on the Svelte auth block — it ships with social logins, magic links, and session management that just works.

The Stripe integration covers the essentials: subscription plans, customer portal, and webhook handling. It’s not as deep as paid alternatives (no metered billing, no per-seat pricing), but for most early-stage products, it’s more than enough.

What stands out

The landing page. Most open-source starters ship a README and call it marketing. This one includes a genuinely nice homepage with pricing cards, feature sections, and a blog powered by MDX. Fork it and you’re halfway to launch.

Better Auth is a smart choice — it’s lighter than Lucia while covering the same ground, and the session handling with SvelteKit hooks is elegant.

The Better Auth integration specifically provides email/password, Google OAuth, and GitHub OAuth out of the box, with a magic link flow as a fourth option. Session tokens are stored as HTTP-only cookies and validated in a handle hook, so protected routes require only a one-line check in +page.server.ts. The email verification flow and password reset are fully wired — not just stubbed — using Resend for transactional email. Compared to rolling your own Lucia setup, you save roughly a full day of boilerplate.

Where paid alternatives like SvelteSaaS charge $149 for the same stack, OpenSaaS Svelte delivers comparable core features — auth, Stripe subscriptions, a landing page, and a dashboard shell — at zero cost. The trade-off is polish: SvelteSaaS includes admin analytics, per-seat billing logic, and a more finished UI theme. But if you are pre-revenue, OpenSaaS gives you the same architecture to build on without the upfront investment.

Where it could improve

No multi-tenancy. If your SaaS has teams, organizations, or workspaces, you’ll need to build that layer yourself. This is a single-user-per-account starter.

Prisma is well-supported but adds build-time overhead and a larger dependency footprint. Developers who prefer Drizzle’s lighter approach may find the migration tedious.