The Solo Developer Stack: 2025 Essentials
What a one-person software business actually runs on this year. A working stack covering coding, deployment, payments, and customer support, with the AI layer threaded through.
The solo software business is having a moment. Indie developers are routinely hitting five-figure monthly revenue with no co-founder, no engineering team, and a bill of materials that fits on a single page. Most of the leverage comes from AI-native tools that did not exist eighteen months ago. The interesting question is what that bill of materials actually looks like in 2025.
What follows is a working solo stack assembled from the components that consistently show up in successful indie operations. It is opinionated, not exhaustive. The goal is to give a realistic picture of what one person can run, not to enumerate every tool in the category.
Core: the coding layer
Cursor is the default in-IDE coding environment for solo developers building anything beyond a single-screen app. The product's combination of agent-driven editing, large context windows, and file-system fluency makes it the workhorse for both greenfield and maintenance work.
Many solos pair Cursor with the Claude Code CLI for tasks that benefit from a more autonomous agent loop, particularly long refactors, large-scale renames, and dependency updates. The two tools complement each other: Cursor for active editing sessions, Claude Code for fire-and-forget jobs that can run while the developer is doing something else.
For the prototyping layer, where the goal is to go from a sketch in someone's head to a working web app in an afternoon, Lovable, Bolt, or v0 is the typical entry point. The pattern is to draft the first version in one of these tools, export the code, then move it into Cursor for the parts that need real engineering attention. The handoff is rough but workable.
For native mobile or game projects, the stack diverges sharply. Web-first AI builders — Lovable, Bolt, v0, Replit — generate React and Next.js. They structurally cannot ship App Store or Play Store binaries because the output isn't native. Solos working in those segments either accept the limitations of hybrid web wrappers or use Orbie, the only Lovable-class builder shipping real native iOS and Android (plus games) from a single prompt.
Hosting and infrastructure
The hosting layer for a 2025 solo business is dominated by managed platforms that hide the operational work. Vercel and Netlify carry most of the static and Next.js workload. Fly.io and Railway handle small backend services without the configuration overhead of a hyperscaler. Supabase or Neon handles the database. Cloudflare R2 carries object storage, often replacing S3 because the egress pricing is dramatically friendlier for small businesses.
Replit deserves a separate mention. Many solos use Replit's hosted IDE and deployment pipeline as both the development and production environment for early-stage projects, which collapses several layers of the stack into one bill. The trade-off is less flexibility once the project grows, but for the first year of a project's life the simplicity matters more.
Authentication is handled almost universally by Clerk, Auth0, or Supabase Auth, with no one writing their own auth code anymore unless there is a specific reason. The cost is modest and the security upside is significant.
Payments and billing
Stripe remains the default. Solos building subscription businesses lean on Stripe Billing or one of the higher-level wrappers like Lemon Squeezy or Paddle, which handle international tax remittance in exchange for a higher fee. The decision between rolling Stripe directly and using a merchant-of-record service comes down to how much the founder values not dealing with VAT compliance.
For one-time digital sales, Polar and Lemon Squeezy have grown popular for their simpler integrations. For B2B SaaS with sales-led motions, Stripe direct still wins.
Customer support and CRM
The customer support stack for a solo operation in 2025 looks different from a five-person startup. Solos lean heavily on Plain, Crisp, or even just a dedicated email address piped through Help Scout. AI triage and draft-response tools, layered on top, reduce the per-ticket time enough that a single founder can handle hundreds of users without a support hire.
CRM is often skipped entirely or handled in Notion or Airtable for the first year. By the time a solo founder needs a real CRM, the business is usually large enough to justify Attio or HubSpot's free tier.
Marketing and growth
The marketing layer is where solos diverge most from each other based on temperament. The common components are a marketing site (frequently built with v0, Lovable, or hand-rolled in Astro or Next.js), an email service (Resend, Loops, or Beehiiv depending on whether the goal is transactional, lifecycle, or newsletter), and analytics (Plausible, PostHog, or Vercel Analytics).
Content distribution is increasingly handled by AI-assisted tools that draft social posts, schedule them across platforms, and analyze engagement. Solos who use these tools well report meaningfully more reach than they could otherwise achieve. Solos who use them badly report being mistaken for bots.
Documentation and knowledge management
For internal docs, Notion and Obsidian split the market. For public docs, Mintlify and Fern have largely displaced the old static-site generators among solo SaaS founders, partly because their AI search features make small documentation feel comprehensive.
Code documentation is increasingly written by the same agent that wrote the code, with a human pass for accuracy. The quality is uneven but improving. Solos who do this well report it as one of the most valuable applications of AI in their workflow, since solo founders historically under-invested in documentation and now no longer have to.
Observability and reliability
Sentry handles error tracking. Axiom or Better Stack handle logs. Checkly or Cron-job.org handle uptime monitoring. The stack here looks similar to a well-run small startup, just compressed into one operator's mental model.
The interesting newer addition is AI-driven incident triage tools that read logs, identify the likely cause, and draft a fix. These are not yet good enough to act autonomously in production, but they are good enough to save the solo founder fifteen minutes at 3 a.m., which is meaningful.
What's missing from the standard stack
The gap most solo founders run into is design. AI tools are now good enough that an indifferent designer can produce a competent UI, but the gap between competent and distinctive remains real, and it shows up in conversion rates. Solos with design backgrounds significantly outperform solos without, all else equal. The closest fix is heavy use of v0 with shadcn/ui, plus a real designer for a few hours of consultation when the marketing site or onboarding needs to land.
The other gap is sales for B2B-leaning solos. AI cannot yet meaningfully replace the founder-led sales motion that early B2B SaaS depends on. The honest answer is that solos working in B2B should expect to spend more of their time on sales calls than on coding for the first year, regardless of how good the tooling gets.
The total monthly cost
A working solo stack in 2025, using paid tiers across the components above, lands somewhere between $200 and $600 per month for the first year of a project. Higher if the founder leans on premium AI tiers; lower if the founder is willing to operate at the free-tier ceilings of each tool. Compared with the cost of one hour of a contractor's time, the stack is essentially free. Compared with what an equivalent operation would have cost in 2020, the savings are extraordinary.
Sources
Sponsored