Tool Decision Kit

Alternatives

• React · Pick it when your app is mostly interactive screens and you don't need built-in server features yet (a pure front-end app, built with Vite).
• Vite · Pick it as the build tool under a pure React front-end app (a SPA) when you don't need built-in server features yet.
• Astro · Pick it when your app is content-heavy, like a blog, docs, or a marketing site, and speed and search ranking matter more than rich interactivity.
• SvelteKit · Pick it (or Remix or Nuxt) when you or your AI builder prefer that ecosystem; they're the same frontend-and-backend-together idea on a different underlying tool.
• Remix · Pick it when you want a frontend-and-backend framework like Next.js but prefer its React-based approach.
• Nuxt · Pick it when you want a frontend-and-backend framework like Next.js but built on Vue.

Alternatives

• shadcn/ui · Pick it when you want polished, ready-made pieces (buttons, forms, dialogs) you drop in; it actually sits on top of Tailwind.
• Material UI · Pick it when you want a complete component library with a mature, established look out of the box.
• Chakra UI · Pick it when you want ready-made components with a friendly, accessible default style.
• Bootstrap · Pick it when you want a familiar, batteries-included look and don't need a custom style.

Alternatives

• Netlify · Pick it when you prefer its workflow or its add-ons; it's very similar to Vercel with simple Git-based deploys.
• Cloudflare Pages · Pick it when you want Cloudflare's fast global network and pricing (needs a little extra setup for full Next.js features).
• Railway · Pick it (or Render or Fly.io) when you outgrow the serverless model or want your app, database, and background jobs in one place.
• Render · Pick it when you want a host that can run always-on servers and databases, not just front-ends.

Alternatives

• Auth0 · Pick it when you need advanced enterprise features or strict compliance; it's the long-time enterprise standard with every login method.
• Supabase · Pick it (Supabase Auth) when you're already using Supabase or want one company for both identity and data.
• Auth.js · Pick it (formerly NextAuth) when you want to own the whole setup, open-source, with no per-user fee.
• Better Auth · Pick it when you want login you run yourself with full control and no usage-based pricing.

Alternatives

• Supabase · Pick it when you want one dashboard for your whole backend (Postgres with auth and file storage bundled in).
• PlanetScale · Pick it when you expect millions of rows and heavy traffic; it's built to stay fast even with enormous tables.
• MongoDB · Pick it when your data is unpredictable and every record can look different (NoSQL, flexible JSON-style documents).
• Firebase Firestore · Pick it when you need data that updates live across devices, like a chat or a shared board (Google's real-time NoSQL).

Alternatives

• Cloudflare R2 · Pick it when you serve lots of large files and want to avoid bandwidth (egress) bills; it doesn't charge when files are downloaded.
• Amazon S3 · Pick it when you're already on AWS or need its huge ecosystem of integrations; it's the original, most widely supported file storage.
• Supabase Storage · Pick it when you want storage bundled with the rest of your Supabase backend.
• UploadThing · Pick it when you want a turnkey upload widget that wires uploads up with the least work.

Alternatives

• react-i18next · Pick it when you're outside Next.js or want the most battle-tested option; it's the most popular React translation library.
• FormatJS · Pick it (FormatJS / react-intl) when a real translation workflow matters, with strong support for plurals and dates.
• Lingui · Pick it when you want a standards-based library built for handing text to professional translators.

Alternatives

• RabbitMQ · Pick it when you run your own servers and want a mature, full-featured, very flexible queue.
• Apache Kafka · Pick it when you're moving huge volumes of events or feeding analytics, not just running a few background jobs.
• Amazon SQS · Pick it (or Google Cloud Tasks) when you're already on AWS or Google and want a managed queue with no server to run.
• Google Cloud Tasks · Pick it when you're already on Google Cloud and want a managed queue with no server to run, like QStash but tied to Google.
• Inngest · Pick it (or Trigger.dev) when your background work gets complex and you want retries, scheduling, and multi-step workflows handled for you.
• Trigger.dev · Pick it when your background work gets complex and you want a 'jobs as code' tool that handles retries, scheduling, and multi-step workflows for you.

Alternatives

• Lemon Squeezy · Pick it when you want a well-known indie Merchant of Record, or you sell things like templates and ebooks alongside subscriptions.
• Paddle · Pick it when you're scaling up and want a more enterprise-grade Merchant of Record (note: it requires business approval before live payments).
• Stripe · Pick it when your revenue is big enough that lower per-transaction fees outweigh bolting on a separate tax tool; you're the seller, so you handle sales tax yourself.

Alternatives

• Postmark · Pick it when getting receipts and alerts reliably into inboxes is critical; it's laser-focused on transactional email with excellent deliverability.
• SendGrid · Pick it (or Mailgun) when you need both transactional and bulk or marketing email at large scale.
• Mailgun · Pick it when you need both transactional and bulk or marketing email at large scale, a long-established alternative to SendGrid.
• Amazon SES · Pick it when you send huge volumes and want the lowest cost (powerful, but with more setup).
• Loops · Pick it when you want product emails and marketing emails together in one simple place.

Alternatives

• Better Stack · Pick it (the default uptime half of the pair) to ping your site on a schedule and alert you the moment it stops responding.
• Rollbar · Pick it (or Bugsnag or Highlight) when you prefer its pricing or pairing with session replay; it captures crashes with the full detail of what broke and who it affected, like Sentry does.
• Bugsnag · Pick it when you want crash reporting with the full detail of what broke and who it affected, an alternative to Sentry for catching errors.
• Highlight · Pick it when you want error catching that pairs nicely with session replay, so you can watch what the user did right before the crash.
• UptimeRobot · Pick it for a generous free tier when all you need is a simple uptime ping.
• Pingdom · Pick it when you want a well-known uptime monitor that pings your site on a schedule and alerts you the moment it stops responding.
• Checkly · Pick it when you want browser-level checks that click through your app like a real user, not just a simple ping.
• Datadog · Pick it (or New Relic or Grafana) when you outgrow separate tools and want errors, uptime, performance, and logs in a single pane of glass.
• New Relic · Pick it when you want errors, uptime, performance, and logs combined into one pricier platform, a single pane of glass.
• Grafana · Pick it when you want to combine errors, uptime, performance, and logs into a single dashboard once you outgrow separate tools.

Alternatives

• Mixpanel · Pick it (or Amplitude) when product analytics is your main focus and you want mature, powerful funnel and retention reports.
• Amplitude · Pick it when product analytics is your main focus and you want deep, mature funnel and retention reports, much like Mixpanel.
• Plausible · Pick it (or Fathom) when you just want lightweight, privacy-friendly traffic stats with no cookie banner.
• Fathom Analytics · Pick it when you want simple, privacy-friendly website analytics: page views and where traffic came from.
• Google Analytics · Pick it (GA4) when you want the standard free option and marketing-style traffic reports.

Alternatives

• Podman · Pick it when you want better security defaults out of the box, or you'd rather not have a program running in the background all the time; same commands as Docker.
• Cloud Native Buildpacks · Pick it when you want a container built from your code automatically, with no recipe file to write yourself.
• Nixpacks · Pick it when you want your container built automatically from your code; many hosting platforms use it behind the scenes already.

Alternatives

• HAProxy · Pick it when load balancing is the main job and you want maximum control over how traffic gets split; very fast and very configurable.
• Traefik · Pick it (or Caddy) when you want less manual config and automatic HTTPS certificates set up for you.
• Caddy · Pick it when you want a modern reverse proxy that configures itself and handles HTTPS automatically.
• AWS Elastic Load Balancing · Pick it (or Google Cloud Load Balancing) when you're already on a cloud and don't want to manage the balancer yourself.
• Google Cloud Load Balancing · Pick it when you're already on Google Cloud and want a managed load balancer that scales on its own with nothing for you to run.

Alternatives

• Amazon Web Services · Pick it (or Google Cloud or Azure) when you need a specific managed service or your team already uses it; the big three, most services, steepest learning curve.
• Google Cloud · Pick it when you need a specific Google managed service or your team already uses it; one of the big three.
• Microsoft Azure · Pick it when you need a specific Microsoft managed service or your team already uses it; one of the big three.
• Hetzner · Pick it (or DigitalOcean or Linode) when you just want a solid plain server with predictable pricing, without the complexity of the big clouds.
• DigitalOcean · Pick it when you want a simple, developer-friendly server with predictable pricing.
• Akamai Cloud (Linode) · Pick it when you just want a solid plain server with predictable pricing, simpler than the big clouds.
• Fly.io · Pick it (or Railway or Render) when you want cloud power that runs your container close to your users with very little setup.

Alternatives

• Cypress · Pick it when you want a polished, very popular end-to-end alternative with great docs and developer experience.
• Selenium · Pick it when you need broad language or browser support, or legacy compatibility; the original browser-automation tool.
• Vitest · Pick it (or Jest) alongside Playwright to test small pieces of logic quickly, without opening a browser.
• Jest · Pick it when you want a widely used tool to check small pieces of logic fast.

Alternatives

• GitLab CI/CD · Pick it when your code lives on GitLab; it runs your tests and deploys automatically in the same place.
• CircleCI · Pick it for its speed and config flexibility when you want a dedicated CI service.
• Travis CI · Pick it when you want another hosted service that runs your tests and deploys automatically, like GitLab CI or CircleCI.
• Jenkins · Pick it when you want to run your own automation server and have complex, endlessly customizable pipelines.
• Docker Hub · Pick it to store your built boxes (images) in the most widely used public registry.
• GitHub Container Registry · Pick it (GitHub Container Registry) to store your built boxes (images) right next to your code on GitHub.
• Amazon ECR · Pick it (Amazon ECR) to store your built boxes (images) when you host on AWS.
• Google Artifact Registry · Pick it to store your built boxes (images) when you host on Google Cloud.

Alternatives

• Codex · Pick it when you already live in the OpenAI world or prefer their models; it's OpenAI's coding agent, the same idea as Claude Code.
• Cursor · Pick it when you like seeing every file change live in an editor; it's an AI code editor with a builder agent built in, same job, slightly different shape.

Alternatives

• Anthropic (Claude) · Pick it (Anthropic's Claude) when you want a top-tier brain with its own cheap-to-premium ladder; one of the three main brains your app can call.
• OpenAI · Pick it (OpenAI's GPT) when you prefer their models or already have an account; one of the three main brains your app can call.
• OpenRouter · Pick it when you want one key and one doorway to almost every model, so you can switch between Claude, Gemini, and GPT with a single setting and always route to the cheapest model that's good enough.
• Groq · Pick it (or Together or Fireworks) when speed and cost matter more than having the absolute smartest model; these hosts run open models extremely fast and cheap.
• Together AI · Pick it when you want to run open models extremely fast and cheaply, like for high-volume tagging or tiny summaries.
• Fireworks AI · Pick it when you want a host that runs open models extremely fast and cheaply, an alternative to Groq or Together.
• Llama · Pick it (or Mistral or Qwen) when you have heavy, predictable volume and want to stop paying per request, or need to keep data fully in-house; open-weight models you can run yourself.
• Mistral AI · Pick it when you want an open-weight model you can download and even run on a server you control.
• Qwen · Pick it when you want an open-weight model that's free to download and can run on a server you control.

Alternatives

• XState · Pick it when a flow has many states and you want to see and enforce them explicitly, with a visual diagram.
• Temporal · Pick it (or Inngest) when a process spans minutes, hours, or days and must never lose its place; a durable workflow that survives crashes and picks up where it left off.
• Inngest · Pick it when a long, multi-step process must run reliably and survive crashes, picking up where it left off.
• AWS Step Functions · Pick it (or Google Workflows) when you're on that cloud and want managed, visual orchestration of steps.
• Google Cloud Workflows · Pick it when you're on Google Cloud and want a managed, visual way to wire steps together.

Alternatives

• GitLab · Pick it when you want everything in one place or to host it yourself; an all-in-one DevOps platform with built-in CI/CD that you can also self-host.
• Bitbucket · Pick it when your team already lives in Atlassian tools; it pairs tightly with Jira and Trello.