Among the three backend-as-a-service SDKs (aws-amplify, firebase and supabase-js), Amplify went from 21.4% of monthly npm downloads in November 2024 to 3.5% in October 2026, while Supabase went from 15% to 75%. Inside Amplify, the Gen 1 CLI is still downloaded more than twice as often as the Gen 2 backend package. The data, and what it does and doesn't tell you.
aws-amplify
firebase
@supabase/supabase-js
Share of monthly npm downloads among aws-amplify, firebase and @supabase/supabase-js. Source: npm registry downloads API.
Amplify's downloads didn't fall. aws-amplify went from about 3.0 million a month to 7.1 million. Everything else grew faster: firebase 4.9 times, supabase-js 70 times. The whole registry has grown sharply as CI systems and AI coding tools install packages, which is why shares say more than raw counts.
Monthly downloads in October 2026 divided by November 2024. Source: npm registry downloads API. Log scale.
Gen 2's share of @aws-amplify/backend plus @aws-amplify/cli downloads. Source: npm registry downloads API.
The Gen 1 CLI's downloads were flat across two years (1.25 million a month, then 1.29 million), and it still outnumbers the Gen 2 backend package by more than two to one. Most Amplify projects in the wild are Gen 1 apps being maintained, not new Gen 2 builds.
Downloads count installs, including CI runs and caches, not developers or apps. A project with a busy pipeline downloads more than one without.
npm doesn't say who downloads. We suspect some of Supabase's growth is AI app builders generating Supabase projects, but the data can't confirm it.
Shares among three SDKs ignore everyone who uses none of them, which is most backends.
The direction is consistent across every series we pulled: Amplify is a maintained platform with a shrinking share of new work.
We'll look at what you have and tell you whether to keep it, upgrade it or move off, and what each costs. Free, 30 minutes.
Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.
Book a free 30-minute call about it. Bring your setup and your bill; you'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Or keep reading
What an Amplify Gen 2 App Actually Deploys, and the Same App Without Amplify
Behind a few TypeScript files, an Amplify Gen 2 backend is Cognito, AppSync, a DynamoDB table per model, Lambda functions, S3 and nested CloudFormation stacks. Two diagrams: what Amplify creates, and the same app built directly, with a table of each piece, what replaces it, and how hard the move is.
Read
Leaving AWS Amplify and AppSync: When It Is Time, and How to Do It Without a Rewrite
Amplify gets a startup to launch fast. The trouble starts later: list queries that scan, resolvers that can't throw or call out, a 30-second ceiling, and a data model that was never designed. The signs it is time to leave, what to move to, what to keep, and a cutover that doesn't log anyone out.
Read
As of November 4, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.