Tools every agentic developer should know.

Every tool is a worry you no longer own

That's the real skill of agentic development. Your AI coding tool writes the code, and a small set of trusted services carries the weight underneath it. Your job is knowing which service to reach for, and when.

Before the list, one rule that makes sense of all of it: each tool below exists to delete an entire category of problems from your life. GitHub deletes "I broke my code and can't get it back." Clerk deletes "how do logins even work?" RevenueCat deletes "Apple's billing documentation." When you're deciding whether to adopt a tool, ask one question: what would I stop worrying about? If the answer is "a lot," it's probably worth the afternoon it takes to set up.

Don't try to learn everything at once. Skim this now, then come back when you hit each stage.

Stage 1 · Build — your AI coding tool

This is your pair-programmer, and today it's where most of the actual code comes from. You describe what you want in plain English; the AI writes it, runs it, and fixes it with you.

Claude Code and Cursor are the two most popular choices for people who want to work close to the code — Claude Code lives in your terminal or desktop and works like an autonomous teammate; Cursor is a full code editor with AI woven through it. Replit puts the whole experience in your browser, nothing to install. Lovable, Bolt, and v0 specialize in going from a sentence to a working web app astonishingly fast — great for prototypes and first versions.

Stage 2 · Save — GitHub

GitHub is your project's home base: every version of your code, saved in the cloud, forever. Made a change that broke everything? Roll it back to yesterday. Want to try a risky idea? Branch off, experiment, and merge it in only if it works.

Two reasons this is non-negotiable, even for a solo beginner. First, AI coding tools occasionally make sweeping changes — version history is your undo button for entire sessions. Second, nearly every other tool in this guide connects through GitHub: Vercel deploys from it, Railway runs from it. Set it up on day one and every future step gets easier.

Stage 3 · Ship — getting your app in front of people

Where your app "lives" depends on what you're building. Three clean cases — plus one thing every app needs.

Stage 4 · Store & sign in — your backend

Almost every real app needs two things: a place to keep data, and a way for users to sign in. This is historically where beginners drown. These three tools are the life raft.

Stage 5 · Grow — add these when you feel the pain

Everything here solves a problem you will have eventually, but probably don't have on day one. The healthy pattern: feel the pain, then add the painkiller.

Getting paid

Payments split cleanly by platform. Selling on the web? Stripe is the industry standard — powerful, trusted, and supported by every tutorial on earth. Its one catch: you're responsible for collecting sales tax around the world. Lemon Squeezy and Polar solve exactly that — they act as the "merchant of record," so they handle global taxes and compliance for you.

Selling inside a mobile app? RevenueCat is the default. Apple and Google each have their own gnarly billing systems; RevenueCat wraps both in one friendly SDK, manages subscriptions and receipts, and shows your revenue in a single dashboard. You never touch StoreKit.

Sending email — Resend

The moment your app has users, it needs to send email: password resets, receipts, welcome messages. Resend makes this about five lines of code, and its companion React Email lets you design emails the same way you build your app. Sending email reliably so it doesn't land in spam is genuinely hard — a classic "rent it, don't build it."

Knowing what's happening — PostHog & Sentry

Once strangers use your app, you're flying blind without these. PostHog shows what users actually do — which features they use, where they get stuck, even session replays — plus feature flags for rolling things out gradually. Sentry watches for crashes and alerts you the moment something breaks, with the exact line of code responsible. Together they answer the two questions every founder asks: "is anyone using this?" and "is it broken right now?"

File uploads — UploadThing & Cloudflare R2

The first time a user uploads a profile photo, you'll discover file storage is weirdly annoying. UploadThing is the easy button — uploads working in minutes, no AWS account required. Cloudflare R2 is the budget powerhouse for when you're storing a lot: dirt-cheap and, unlike Amazon's S3, it charges nothing when people download your files.

AI features — OpenRouter & Replicate

Adding AI to your own app? OpenRouter gives you a single API key that works with nearly every model from every provider — so when a better or cheaper model ships next month, you swap one line instead of rewriting your app. Replicate does the same for image, audio, and video models: describe what you want generated, and it runs on their GPUs, not yours.

Tools to explore as you grow

Everything above is the core toolkit. The tools below are worth knowing exist so you recognize the moment you need them — but don't go set them up now. File this section under "come back to me later."

Background & scheduled jobs — Inngest or Trigger.dev

The moment you want "email this user three days after they sign up," "run cleanup every night at midnight," or "process this big upload without freezing the app," you've reached background jobs. Doing this reliably by hand is genuinely tricky; these tools make it approachable, and it's a common early surprise for vibe coders.

Making it look polished — Tailwind + shadcn/ui

The reason some vibe-coded apps look sharp and others look generic. Tailwind is a styling system and shadcn/ui is a set of beautifully pre-made components (buttons, menus, dialogs) you drop straight in. Good news: most AI coding tools already lean on these, so you may be using them without realizing it — worth knowing by name when you want to fix "why does my app look a bit off?"

Protecting your costs — Upstash

Once you have real traffic — especially if your app calls AI models — you'll want caching (so you don't redo expensive work) and rate-limiting (so no single user, or bot, can run up your bill). Upstash is the beginner-friendly way to add both. A "when the traffic and invoices show up" tool.

Connecting to other apps — Zapier, Make, or n8n

If your app needs to talk to Slack, Google Sheets, a CRM, or hundreds of other services, these let you wire things together with little or no code — especially handy for internal tools and automations rather than a classic app.

Three starter stacks

If you want a shortcut, here are three combinations that just work.

The whole journey, on one map

Everything above, as a single flowchart. Follow the path from idea to shipped product — you don't need every tool, you need the right one at the right stage.

The Vibe Coder's Tool Map — a 2026 snapshot. Free tiers and pricing move fast; confirm on each tool's own site.

The golden rule

Every tool in this guide has a free tier generous enough to build and launch on. So resist the urge to sign up for everything today — that's its own kind of procrastination. Start with a coding tool and GitHub. Add a backend when your app needs to remember things. Add payments when someone wants to pay you. Add analytics when you have users to analyze.