A solo founder tech stack 2026 looks nothing like the bloated setups of five years ago. You don't need a DevOps hire, a Kubernetes cluster, or a $400/month infrastructure bill to ship a real product. You need leverage.
The one person startup stack has collapsed into a tight set of defaults: an AI-capable backend, an edge-first runtime, a boring but reliable registrar, and a mailer that doesn't end up in spam. That's the core. Everything else is optional.
This is the stack I'd hand to any indie hacker starting a SaaS, micro-app, or API product today. It's opinionated, but every choice has a reason. Nothing here is speculative vaporware. These are tools you can sign up for this afternoon.
The Core Principles Behind an Indie Hacker Stack
Before listing tools, let's establish the rules. A solo founder's stack is different from a team stack. You optimize for different things.
- Time to ship beats architectural purity. If a managed service saves you four hours a week, it's worth the markup.
- Predictable pricing beats marginal savings. Surprise bills kill solo projects faster than slow code.
- Boring infrastructure beats exciting infrastructure. Your database should not be a hobby.
- One vendor per concern. Two auth providers is one too many. Three payment processors is a cry for help.
Every tool in your stack should either save you time or make you money. If it does neither, cut it.
The indie hacker stack in 2026 is about subtraction. You're not building a resume. You're building a business.
The 2026 Stack, Layer by Layer
Runtime and Hosting: Edge-First Is the Default
For most solo founders, the backend runtime is now an edge function platform. Cloudflare Workers, Vercel Functions, and Deno Deploy are the three names that matter.
Cloudflare Workers gives you a generous free tier, a global network, and tight integration with their storage products. You can deploy a function to 300+ locations with wrangler deploy and never think about regions again.
Vercel is the smoother experience if you're building a Next.js or Astro frontend. The functions run on AWS Lambda under the hood, but the DX is excellent. Deno Deploy is the dark horse: native TypeScript, Web APIs, and a simple deployctl CLI.
Here's a minimal wrangler.jsonc for a solo founder's API:
{
"name": "my-saas-api",
"main": "src/index.ts",
"compatibility_date": "2026-01-01",
"observability": {
"enabled": true
},
"kv_namespaces": [
{ "binding": "CACHE", "id": "abc123" }
]
}
That's it. No Docker, no load balancers, no region selection. You write a function, you deploy it, it runs everywhere.
Database: Managed Postgres or a Serverless Alternative
The database choice splits into two camps.
Camp one: managed Postgres. Neon and Supabase are the clear leaders. Neon offers serverless Postgres with branch-based workflows, which means you can spin up a preview database for every pull request. Supabase bundles Postgres with auth, storage, and realtime subscriptions, which can replace three other tools.
Camp two: serverless-native databases. Cloudflare D1 (SQLite at the edge) and Turso (libSQL) are lighter and cheaper. They're not drop-in Postgres replacements, but for a solo founder building a read-heavy app, they're often enough.
| Database | Model | Free tier | Best for | Watch out |
|---|---|---|---|---|
| Neon | Serverless Postgres | 0.5 GB storage, 190 compute hours | SQL-heavy apps, migrations | Cold starts on inactive branches |
| Supabase | Managed Postgres + services | 500 MB database, 50K auth users | Fastest path to full-stack | Lock-in to their ecosystem |
| Cloudflare D1 | SQLite at the edge | 5 GB storage, 5M reads/day | Read-heavy, global apps | No stored procedures |
| Turso | libSQL (SQLite fork) | 9 GB storage, 500 databases | Embedded and edge use cases | Different SQL dialect than Postgres |
For most solo founders, Supabase is the pragmatic default. You get auth, storage, and a database in one project. That's three services you don't have to wire together.
AI Infrastructure: One Model Gateway, Not Five SDKs
The AI layer in a solo founder tech stack 2026 is not about training models. It's about calling them efficiently.
You need one gateway that routes to multiple models. OpenRouter is the most popular choice. It gives you a single API key that works with OpenAI, Anthropic, Google, Meta, and dozens of open-weight models. You can switch from gpt-4o to claude-sonnet-4-5 by changing one string.
Here's what a minimal AI call looks like through OpenRouter:
const response = await fetch("https://openrouter.ai/api/v1/chat/completions", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.OPENROUTER_API_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
model: "anthropic/claude-sonnet-4-5",
messages: [{ role: "user", content: "Summarize this feedback" }]
})
});
The alternative is direct API access to one provider. That's fine if you're all-in on Anthropic or OpenAI. But a gateway costs you nothing extra and gives you leverage when pricing shifts.
For embeddings and vector search, you have two paths. Use a hosted vector database like Pinecone or Supabase's pgvector. Or skip vectors entirely and use a managed retrieval service like LangChain's hosted offering. Most solo founders don't need a dedicated vector DB until they hit real scale.
Domain and Registrar: Boring Is Beautiful
Your registrar is the least exciting part of the stack, but it's the one you'll touch for years. You want a registrar that doesn't upsell you at every turn.
Cloudflare Registrar sells domains at wholesale cost. A .com costs around $10.44 per year, which is Cloudflare's actual cost from Verisign. No markup. The catch: you must use Cloudflare's DNS, which is fine because it's excellent.
Porkbun is the other strong choice. Their .com pricing hovers around $10.37 with occasional promotions. Their interface is clean, and they include free WHOIS privacy. Namecheap is fine but has more upsell noise.
- Cloudflare Registrar: wholesale pricing, requires Cloudflare DNS, no upsells
- Porkbun: near-wholesale pricing, free WHOIS privacy, clean UI
- Namecheap: reliable, frequent promotions, more clutter
- GoDaddy: avoid. Aggressive upsells and renewal price jumps.
Never register your domain through your hosting provider. If you ever want to move, you'll be fighting their support team. Keep domains at a dedicated registrar.
Email: Transactional and Marketing, Separated
Email is where solo founders get burned. You need two separate systems.
Transactional email (password resets, receipts, notifications) should go through a dedicated API. Resend is the current favorite. It's built on top of AWS SES but gives you a clean dashboard, webhook events, and a React-based template system. Postmark is the premium alternative with better deliverability tracking.
Marketing email (newsletters, product updates, drip campaigns) needs a different tool. Loops is the indie hacker favorite. It's designed for SaaS onboarding sequences and integrates cleanly with Resend. Buttondown is the minimalist choice if you just need a newsletter.
The mistake is using one tool for both. Transactional mailers throttle marketing sends. Marketing tools aren't reliable for time-sensitive notifications. Keep them separate.
Auth, Payments, and the Rest
A one person startup stack needs auth and payments without building them from scratch.
For auth, Supabase Auth or Clerk are the two sane choices. Supabase Auth is free and bundled with your database. Clerk is more polished and handles social logins, magic links, and session management with less code.
For payments, Stripe remains the default. Their new "Payment Links" and "Checkout" products mean you can start charging without a custom backend. Paddle is the alternative if you're selling globally and want to offload VAT and sales tax compliance.
The rest of the stack fills in with small, focused tools:
- Set up your domain with Cloudflare Registrar and point DNS at your runtime.
- Create a Supabase project for database, auth, and storage.
- Deploy your API to Cloudflare Workers or Vercel Functions.
- Add OpenRouter for AI calls and Resend for transactional email.
- Connect Stripe for payments and Loops for marketing email.
- Monitor everything with a simple uptime check like Better Stack or UptimeRobot.
That's six steps. You can do all of them in a weekend.
What to Skip in 2026
Just as important as what to include is what to leave out. The indie hacker stack is defined by its omissions.
Skip Kubernetes. Skip self-hosted databases. Skip building your own auth. Skip multi-cloud redundancy. Skip microservices. Skip a dedicated vector database until you have at least 100K documents. Skip a CRM until you have customers to manage.
Every skipped tool is time you spend shipping instead of maintaining.
A solo founder's competitive advantage is speed. Every infrastructure choice should serve that advantage. If a tool slows you down, it's the wrong tool, no matter how impressive it looks on a resume.
The solo founder tech stack 2026 is not about having the most sophisticated setup. It's about having the fewest moving parts that still get the job done. You can always add complexity later, when revenue justifies it.
FAQ
How much does a solo founder tech stack cost in 2026?
A typical one person startup stack costs between $0 and $50 per month before you have paying customers. Cloudflare Workers, Supabase, Resend, and OpenRouter all have free tiers that cover development and early traction. Once you cross roughly 1,000 monthly active users, expect to pay $50 to $150 per month for combined infrastructure. The biggest cost jumps come from database storage, AI token usage, and email volume, not from hosting.
Do I need to learn Kubernetes as a solo founder?
No. Kubernetes is a team tool for organizations managing dozens of services. A solo founder building a SaaS or API product gets zero benefit from Kubernetes in the first year. Managed platforms like Cloudflare Workers, Vercel, and Supabase handle scaling, deployment, and monitoring for you. If you ever reach a scale where Kubernetes makes sense, you'll have the revenue to hire someone who knows it.
What's the best AI model for a solo founder to use in 2026?
There's no single best model. The practical answer is to use a gateway like OpenRouter and route requests based on the task. Use Claude models for writing and reasoning, GPT models for coding and structured output, and smaller open models like Llama for high-volume, low-stakes tasks like classification. The key is to avoid locking yourself into one provider. Model pricing and quality shift every few months.
Should I use Supabase or build my own backend?
Use Supabase unless you have a specific reason not to. Building your own auth, database, and storage layer is a multi-week project that adds no value to your product. Supabase gives you all three with a Postgres database underneath, so you can always migrate to raw Postgres later. The main reason to avoid Supabase is if you need a very specific database feature or you're building something that doesn't fit the relational model.
How do I choose between Cloudflare Workers and Vercel?
Choose based on your frontend framework. If you're using Next.js or Astro, Vercel is the path of least resistance. The functions, preview deployments, and analytics are tightly integrated. If you're building a pure API or a framework-agnostic backend, Cloudflare Workers is cheaper at scale and has a better free tier. Both are excellent. The wrong choice is running your own Node.js server on a VPS because you think it's "more control."