GitHub Copilot alternatives

Warp

A terminal that treats each command and its output as a block you can navigate, copy and share, rather than an endless scroll. Input behaves like a text editor, history is searchable, and an assistant can read a failing command and suggest the fix. Workflows save parameterised commands for a team. Some of it requires an account, which is the objection people raise most.

Cursor

VS Code rebuilt around a model that can see the whole repository. Beyond autocomplete it edits across files from an instruction, answers questions about unfamiliar code, and applies a diff you review before it lands. Keybindings and extensions carry over from VS Code, so switching costs an afternoon. The multi-file edit is the feature people stay for.

Vercel

Deploys a frontend by pushing to a branch, with a preview URL for every pull request, the workflow most React teams now expect by default. Built by the maintainers of Next.js, which it supports first and best. Edge functions, analytics and image optimisation are included. Costs are predictable until traffic is not, and bandwidth is the line to watch.

Railway

Deploys services, databases and cron jobs from a repository with no infrastructure config to write. Connect a repo, pick a region, and it infers the build. Environments, private networking between services and one-click Postgres or Redis are included. It suits small teams and side projects that have outgrown a single host and do not want Kubernetes.

Sentry

Catches errors in production and tells you what you need to fix them: the stack trace with source maps applied, the release that introduced it, the browser or runtime, and how many users hit it. Groups duplicates so one bug is one issue. Performance monitoring and session replay sit alongside. Most teams install it after the outage that made the case for it.

Supabase

Postgres with the things an application needs bolted on: authentication, row-level security, file storage, realtime subscriptions and auto-generated APIs. It is a real Postgres database, so `pg_dump` and any Postgres client work and leaving is a migration rather than a rewrite. Popular as a Firebase replacement for teams that would rather own SQL than a proprietary document store.

Postman

Builds, tests and documents an API without writing a client first. Collections capture requests with environments and variables, tests run in CI through Newman, and mock servers stand in for endpoints that do not exist yet. Documentation generates from the collection, which is how it stays current. Ubiquitous enough that a Postman collection is a normal way to hand over an API.

Stripe

Payments, subscriptions, invoicing and payouts, with documentation good enough that people copy from it as a matter of habit. Handles cards, wallets, bank debits and local methods across most of the world, plus fraud tooling, tax calculation and a billing engine. The default choice for software businesses. You remain the merchant of record, which is the difference from Paddle or Lemon Squeezy.

ShipFast

A Next.js starter with the parts everyone rebuilds already wired together: authentication, Stripe payments, a database, transactional email, SEO and a landing page. Sold as a one-time purchase with lifetime updates. The pitch is days saved on plumbing; the caveat is inheriting someone else's architecture along with it.

Mixpanel

Event analytics for questions that begin with 'how many users who'. Funnels, retention curves, cohorts and flows are the core, built on events with properties rather than pageviews. Strong at behavioural questions and weaker at the simple traffic reporting a marketing team wants, which is why it often sits beside a web analytics tool.

Amplitude

Behavioural analytics built around cohorts, retention and the paths users take through a product. Comparable to Mixpanel and generally chosen for the depth of its retention and journey analysis. Experimentation and customer data tooling sit alongside. Aimed at product teams with enough volume for the analysis to mean something.

Intercom

Support inbox, help centre and an AI agent that resolves a meaningful share of conversations before a human sees them. Messenger, tickets, articles and automation share one workspace, so an answer written once serves the article, the bot and the reply. Sold on deflection rate; priced accordingly, with resolution-based billing for the agent.