0 Get started
These two are more alike than anything else on this list: both are code you write that defines infrastructure in an account you already own, and neither is a hosted data plane. The differences are which cloud, how much of it you inherit, and what the kit gives you above the primitives.
Choose Amplify
When you are on AWS, and you intend to stay.
A TypeScript backend definition with end-to-end types, hosting with SSR, and an escape hatch to the CDK that puts every AWS service within reach. If your company's compliance, billing and expertise are already AWS-shaped, nothing here outweighs that.
Choose Pithy
When you want the primitives to be few and the capabilities to be many.
Cloudflare gives you a handful of pieces — a Worker, SQLite, object storage, a Durable Object — and Pithy composes payments, games, secrets, audit and support on top of them. Fewer moving parts underneath, considerably more written for you above.
Where they overlap
If a feature is standard for a modern backend, assume both have it. We are not going to dress one up as a differentiator.
Both define the backend in code with real types. Neither should claim it against the other.
Both provision into an account you own. There is no third-party data plane in either.
Cognito there, the auth capability here. Table stakes.
S3 there, R2 here.
Lambda there, Workers here.
Amplify Hosting there; `pithy ui` puts the client in the Worker here.
The difference underneath
Amplify is a friendlier surface on AWS. Your backend definition becomes Cognito user pools, AppSync APIs, DynamoDB tables, S3 buckets and Lambda functions — and when the surface is not enough, the CDK escape hatch puts the rest of AWS behind it. That is enormous reach, and it is also the whole complexity of AWS sitting one layer down.
Cloudflare's primitives are deliberately few: a Worker, D1 for SQLite, R2 for objects, a Durable Object for coordination, Vectorize for embeddings. Pithy composes on top of those, and the leverage comes from the capabilities rather than from the breadth underneath.
So the choice is roughly: do you want a thin, typed layer over a very large cloud, or a thick layer of written capabilities over a small one?
Feature by feature
| Feature | Amplify | Pithy |
|---|---|---|
Runtime & data | ||
| Relational SQL Amplify: DynamoDB by default; relational means adding RDS or Aurora yourself Pithy: D1 is SQLite, and it is the default | Partial | Yes |
| Realtime subscriptions Amplify: AppSync subscriptions Pithy: Durable Objects for authoritative state | Yes | Partial |
| No cold starts Amplify: Lambda, mitigated but present Pithy: Workers do not have them in the same sense | No | Yes |
| Reach beyond the framework Amplify: the CDK escape hatch reaches the rest of AWS Pithy: Cloudflare's primitives, and what you write on them | Yes | Partial |
| Runs at the edge Amplify: CloudFront in front of regional services Pithy: Workers, by construction | Partial | Yes |
What the kit adds | ||
| Payments on five rails, one entitlement Pithy: Apple, Google, Stripe, Paddle and Lemon Squeezy | No | Yes |
| Per-user balance ledger Pithy: atomic, idempotent, overdraft-safe by CHECK constraint | No | Yes |
| Games infrastructure Pithy: authoritative sessions, matchmaking, rating and leaderboards | No | Yes |
| Audit trail attributed to an actor Amplify: CloudTrail covers the account, not your app's actions Pithy: a queryable trail of the actions that matter | Partial | Yes |
| Encrypted secrets with rotation Amplify: Secrets Manager, wired by you Pithy: a registry, per environment, with at-rest rotation | Partial | Yes |
| Support inbox in your own database Pithy: inbound mail, classified on your own AI binding | No | Yes |
Operations | ||
| A preview environment per branch Amplify: sandbox and branch deployments Pithy: a worktree, ports and ephemeral resources, torn down afterwards | Yes | Yes |
| One runtime to learn, not a catalog of services Amplify: several AWS services, and the CDK when you leave the path Pithy: a Worker and four primitives | Partial | Yes |
| No charges for egress Amplify: AWS bills data transfer out Pithy: R2 does not | No | Yes |
| Everything drivable by an agent Pithy: every command takes flags, requires no prompt and speaks `--json` | Partial | Yes |
| A polished platform console Amplify: the AWS console, and it is deep Pithy: Cloudflare's own, and it is very good — the console the account already uses for Workers, D1, R2 and the logs | Yes | Yes |
| Panes for users, money and the trail Amplify: Cognito users in one console, and the rest spread across the others Pithy: users, entitlements, purchases, subscriptions, support and the trail — and a user can be comped, revoked or signed out everywhere | Partial | Yes |
The saffron tick marks where Pithy leads — not that the other column is absent. Every claim about Amplify was checked against their own documentation on 2026-08-25; both products change, and this page is a snapshot rather than a maintained contract.
Where Pithy pulls ahead
Amplify is very good at provisioning a database, a bucket and an auth pool. It has nothing to say about what a subscription is, how an entitlement resolves across three stores, or who is allowed to submit a score. That is the layer this kit is.
DynamoDB is the default data store, and a relational one means bringing RDS or Aurora and the connection management that comes with them. D1 is SQLite from the first command.
The CDK escape hatch is Amplify's greatest strength and its sharpest edge: the moment you use it, you are doing AWS. Cloudflare's surface is small enough to hold in your head.
AWS bills data transfer out of almost everything. R2 does not, and for anything serving files that is most of the difference in the bill.
Lambda's cold starts are manageable and they are still a thing you think about. Workers are not that shape.
Where Amplify wins
Queues, streams, ML, data warehousing, anything. One escape hatch and the largest cloud in the world is available to you.
Billing, compliance, networking and expertise all in one place is worth more than any feature comparison on this page.
SAML, OIDC federation and user pool complexity that a passwordless kit does not attempt.
Amplify Hosting deploys modern frameworks with server rendering. `pithy ui` puts a SPA in the Worker, which is a narrower answer.
AWS Support is a product you can buy. With the kit, Cloudflare is on call for the primitives and you are on call for the Worker.
At genuinely large scale a distributed key-value store is the right shape and D1 is not. Say that plainly.
If your organization is on AWS, stay on AWS — no comparison page should talk anyone into a cloud migration for a nicer developer experience. The argument for the kit is for greenfield work where nobody has picked a cloud yet, and where what you need is not access to two hundred services but a backend that already knows what a subscription, a match and an audit event are.