The AI stack for indie hackers in 2026
The exact tools — models, code assistants, infrastructure, and MCP servers — a solo builder actually needs. No survey. A prescription.
The most confusing thing about building with AI in 2026 isn't the technology — it's the noise around it. Every week brings a new model, a new framework, a new primitive that promises to change everything. Most of it does not matter at indie scale.
This is not a list of every option. It is a recommendation — a stack you can hold in your head, ship with over a weekend, and not regret in three months. Everything here has been through real projects, not demos. Where there's a fork in the road, I'll tell you which way I'd go and why.
How to read this
Each section ends with the specific tools I'd reach for. Pick one per layer and move on. The fastest way to stall a solo project is to keep re-litigating decisions that don't move the product forward.
Pick one model and commit to it
The model layer feels like a weekly decision. It isn't. Switching models mid-build means re-testing every prompt, re-tuning every output parser, and re-learning a new set of failure modes — all for a marginal quality delta that your users will never notice. Choose once, at the start, based on the job in front of you.
For most indie work, Claude Sonnet is the right call. It reads code like a senior engineer, follows multi-step instructions without losing the thread, and rarely invents APIs you then have to go and verify. When you're optimizing for cost at volume — classification, extraction, the boring high-throughput stuff — GPT-4o mini is fast and cheap and good enough. And when the bill needs to be zero, Gemini 2.5 Flash has a free tier that is genuinely usable for prototyping.
Choosing a model is not a technology decision. It's a decision to stop choosing, so you can start building.
Your code assistant stack
This is the one place I'll tell you to run two tools at once, because they do genuinely different jobs. Cursor is where you live: navigating the file tree, making edits in context, asking questions about code you're staring at. Claude Code is the terminal-first agent you hand the bigger, scarier tasks to — a migration across ten files, adding a whole feature, a refactor that needs to hold context no editor tab can.
They complement each other; don't try to make one do the other's job. If Cursor's pricing rubs you the wrong way, Windsurf is a real alternative with the same model access and a slightly different collaboration philosophy — worth a week of side-by-side before you commit.
Infrastructure that disappears
The best infrastructure for a solo builder is the kind you forget exists. You want to push code and have it be live; you want a database that's already there; you want auth, storage, and cron without standing up a single server. In 2026 that's a two-product answer for the vast majority of projects.
Vercel for the frontend and API routes — Next.js on its home turf, zero-config deploys, built-in cron, edge middleware. Supabase for everything behind it: Postgres, auth, file storage, realtime, and Edge Functions. Free to roughly $25/month carries most indie projects end to end. Reach for Railway only when you need to run something always-on or off the serverless happy path — deploy any Dockerfile, no platform ceremony.
Auth in a morning, not a month
Do not build auth from scratch. The attack surface is real, the edge cases are endless, and the maintenance tail outlives the dopamine of getting login working. This is a solved problem — buy or borrow the solution and spend your hours on the thing only you can build.
- Clerk — the fastest path for most projects. Prebuilt React components handle email, OAuth, passkeys, and MFA; the free tier runs to 10,000 monthly active users.
- Better Auth — the open-source, self-hosted alternative. Same feature set, your database, no vendor lock-in. Reach for it when owning the session data matters.
The MCP servers worth wiring up now
Model Context Protocol is the emerging standard for giving an AI agent structured access to tools and data. The ecosystem is large and growing, but you do not need most of it. Three servers cover the majority of what a coding agent needs to be genuinely useful — wire these into Claude Code (or any MCP client) before you reach for anything fancier.
// claude_desktop_config.json — three servers, most of the value
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/project"]
},
"fetch": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-fetch"]
}
}
}The filesystem server lets the agent read and write files by path — the foundation of any real coding workflow. Fetch lets it make HTTP requests and read the response, which turns it into a capable API tester and researcher. And the Supabase server lets it query and mutate your database rows directly in the conversation, so "add a column and backfill it" becomes a sentence instead of a chore.
Skip LangChain. Use the Vercel AI SDK.
This one is opinionated, so let me be direct. LangChain adds abstraction that only pays off at team scale — chains, agents, callbacks, and retrieval components that take longer to understand than the API calls they wrap. On a one-person project, that's a tax with no return.
On Next.js, the Vercel AI SDK is the right abstraction: streaming, tool calling, and multi-step agent loops behind a small, readable API, maintained by the same team as your deployment platform. For pure backend work with no UI, skip the framework entirely and call the provider SDK directly — the orchestration overhead rarely earns its keep solo.
The frameworks-as-resume-padding trap
Adopting a heavy orchestration framework because it's what "serious" teams use is a common way to lose a weekend. Match the tool to the project in front of you, not the company you imagine you'll become.
The stack isn't what makes a product — the product makes the product. But the right stack gets out of your way and keeps the decision load low. Every tool here has one job, does it well, and won't become a liability when you need to move fast. Pick one per layer, ship something this weekend, and find them all on the Radar.
Find these on the Radar
Every tool here lives on Kapyn Radar. Save the ones that fit into a Loadout and find them again.
