The Self-hosted Indie Stack
A stack for builders who would rather own their infrastructure than rent managed everything, with costs that do not scale punitively with success. Portable pieces, no per-seat auth bills, no proprietary database API.
- 01SVMeta FrameworksFramework
SvelteKit
Full-stack framework with a small runtime and little boilerplate. It compiles away the framework, so the shipped app stays lean.
- 02PODatabasesDatabase
PostgreSQL
The open relational standard you can run anywhere, from a cheap VPS to a managed host, with no proprietary API to lock you in.
- 03BEAuthAuth
Better Auth
Open-source auth you own and self-host. No per-active-user pricing that scales against you as the product grows.
- 04LEPaymentsPayments
Lemon Squeezy
Merchant of record so global tax is handled, with a flat, predictable cut and no enterprise sales process to start selling.
- 05RAHostingHosting
Railway
Simple deploys with usage-based pricing you can read in advance, and an exit to a raw VPS later without rewriting anything.
Why this combo
This stack is for builders who would rather own their infrastructure than rent managed everything, and who want costs that do not scale punitively with success. Every piece is portable: PostgreSQL and Better Auth run on any host, SvelteKit compiles to a lean output, and Railway is a convenience you can walk away from for a plain VPS without touching application code. Lemon Squeezy is the one managed dependency kept on purpose, because handling global sales tax yourself is rarely worth the time it saves. The theme throughout is no per-seat auth bills, no proprietary database API, and no lock-in you cannot unwind later.
This stack optimizes for ownership and predictable cost over maximum convenience. It accepts a little more setup in exchange for the ability to move every piece, and for a bill that grows with usage rather than with the number of users you succeed in signing up.
What this costs to start
Four of the five pieces are free and open source; the only fixed cost is hosting, which starts low on Railway and is fully portable to a cheaper VPS as you grow. The deliberate contrast with managed stacks is in how the cost curve bends: self-hosted Better Auth has no per-active-user fee, and self-managed Postgres has no managed-tier ceiling, so success does not trigger a pricing renegotiation. Lemon Squeezy’s transaction cut is the one usage-based fee, accepted because tax compliance is the one job genuinely worth outsourcing.
What to swap when you scale
- Hosting: Railway is the easy start; moving to a VPS or dedicated host is a deployment change, not an application change, because nothing depends on a proprietary platform API.
- Database: the same Postgres runs on a managed host if you want backups and failover handled, or on your own server if you want full control and lower cost.
- Auth: Better Auth scales with your infrastructure rather than a per-user invoice, so growth in users does not change the auth bill.
Where it is not the right call
If you have no appetite for any operational work, a fully managed stack will get you to launch faster, and that speed is worth more than ownership when you are still validating the idea. This stack pays off once you have traction and want the cost curve and the lock-in profile on your side rather than the vendor’s.