Every Tool I Use as a Solo Operator
Every Tool I Use as a Solo Operator
One of the most common questions I get is "what tools do you use?" Here's the full answer — not a curated list of sponsors, but the actual tools that are open on my machine right now.
I'll keep this post updated as things change. Last updated: April 2026.
Development
Cursor — My primary code editor. It's VS Code with AI capabilities built in. I use it for all hands-on editing, debugging, and code exploration. The inline edit feature alone is worth the switch from vanilla VS Code.
Claude Code — My AI development partner. I use it for anything that touches multiple files or requires thinking about architecture. New features, complex refactors, debugging sessions that span the whole codebase. It's the most capable AI coding tool I've used.
GitHub — Version control and repository hosting. Nothing fancy here — it's the standard, and it integrates with everything else.
Vercel — Deployment platform. Git push to deploy. Preview deployments for every branch. Free tier covers most solo projects. I've never had to think about infrastructure.
The Blog Stack
Astro — Static site generator for this blog. Ships zero JavaScript by default, which means fast pages and great SEO scores. The developer experience is excellent — components feel familiar if you've used React or Vue.
Keystatic — The CMS powering this blog. It gives me a web-based admin panel for writing posts, but stores everything as markdown files in the git repo. No database, no monthly bill, full ownership of content.
Tailwind CSS — Utility-first CSS framework. I resisted it for years, then tried it, and now I can't go back. Building UI is dramatically faster when you're not context-switching between HTML and CSS files.
Design
Figma — For anything that needs visual planning before I build it. Wireframes, component designs, quick mockups. I'm not a designer, but Figma is forgiving enough for developer-level design work.
v0 by Vercel — When I need a UI component and I know roughly what it should look like but don't want to build it from scratch. I describe it, get a starting point, and adapt it to my project.
Productivity
Linear — Project management. Fast, keyboard-driven, well-designed. I use it even as a solo operator because externalizing my task list into a proper tool keeps me focused on the right things.
Notion — Long-form notes, documentation, planning docs. It's where I think through ideas before they become code or blog posts.
Arc Browser — My daily browser. The workspace and profile features help me keep personal, work, and project contexts separated.
Communication
Slack — For communities and collaborations. Most indie hacker communities I'm part of live here.
Twitter/X — Building in public, connecting with other builders, sharing what I'm working on. The indie hacker community on Twitter is still the best place to find like-minded people.
What I've Intentionally Left Out
No monitoring tool, no analytics dashboard, no error tracking service. Not yet. These are important, but premature optimization of your tool stack is just as real as premature optimization of your code.
I'll add these as the projects I'm building actually need them. Right now, Vercel's built-in analytics and deploy logs tell me everything I need to know.
The Philosophy
My tool selection follows three rules:
- Does it reduce friction? Every tool should make a specific task faster or easier. If it adds complexity without clear benefit, it's out.
- Can I operate it solo? Tools that require a team to manage are disqualified. I want tools that get out of my way.
- Is the free tier honest? I'm not opposed to paying for tools, but I want to start free and upgrade when I've proven the value. Tools that paywall essential features behind enterprise pricing aren't built for solo operators.
The best tool stack is the one you actually use. Not the one you read about in a "top 10 tools for developers" blog post. Use what works, drop what doesn't, and don't feel guilty about it.