Skip to content
AppwritevsAWS Amplify

One project, not a stack of AWS services._

Amplify assembles your backend from Cognito, AppSync, DynamoDB, Lambda, and S3, each with its own console, limits, and bill, and it only runs on AWS. Appwrite gives you auth, five database models, storage, functions in 13+ runtimes, messaging, and hosting in one open-source platform.

Start building for freeView pricing

npx ampx sandbox

One Amplify backend
  1. Amazon Cognito · User poolCREATE_COMPLETE
  2. Amazon Cognito · Identity poolCREATE_COMPLETE
  3. AWS IAM · Roles and policiesCREATE_COMPLETE
  4. AWS AppSync · GraphQL APICREATE_COMPLETE
  5. Amazon DynamoDB · Model tablesCREATE_COMPLETE
  6. AWS Lambda · FunctionsCREATE_COMPLETE
  7. Amazon S3 · Storage bucketCREATE_COMPLETE
  8. AWS CloudFormation · Nested stacksCREATE_COMPLETE

The same backend on Appwrite

1 project
  • Auth
  • Databases
  • PostgreSQL
  • Storage
  • Functions
  • Realtime
  • Messaging
  • Sites
  • Domains
  • Firewall

Illustrative. Amplify Gen 2 deploys your backend as AWS CloudFormation stacks across these services.

Pricing_

One plan instead of seven meters_

Every AWS service behind Amplify bills on its own. Appwrite Pro starts at $25/mo with allowances for each resource, including 2TB of bandwidth that would cost about $300 a month on Amplify Hosting.

An Amplify month

  • Amplify HostingBuild minutes, bandwidth, SSRMetered
  • Amazon CognitoMonthly active usersMetered
  • AWS AppSyncRequests and realtime minutesMetered
  • Amazon DynamoDBReads, writes, and storageMetered
  • AWS LambdaRequests and durationMetered
  • Amazon S3Storage and requestsMetered
  • AWS WAFPer app, plus usage$15+

Seven meters, seven sets of limits, one AWS invoice to decode.

An Appwrite month

Appwrite Pro$25/mo
  • 200,000 monthly active users
  • 2TB bandwidth
  • 150GB storage
  • 3.5M function executions
  • Firewall rules included

Pay as you go above the allowances, up to a budget cap you set.

Databases_

More than DynamoDB behind a GraphQL API_

Amplify Data puts every model in DynamoDB, and SQL means running your own database. Appwrite gives you five database models in one project: TablesDB on serverless or dedicated compute, plus DocumentsDB, VectorsDB, PostgreSQL, and MySQL on dedicated compute.

Database models in one Appwrite project
5
AWS Amplify: Amazon DynamoDB
1
AppwriteAWS Amplify

  • TablesDB

    Relational tables

    ServerlessDedicated

    AWS Amplify: Not offered

  • DocumentsDBBeta

    JSON documents

    Dedicated

    AWS Amplify

    Amazon DynamoDB

    Serverless, behind AppSync

  • VectorsDBBeta

    Vectors and embeddings

    Dedicated

    AWS Amplify: Not offered

  • PostgreSQLBeta

    Native SQL

    Dedicated

    AWS Amplify

    Bring your own database

    Provisioned and run by you

  • MySQLBeta

    Native SQL

    Dedicated

    AWS Amplify

    Bring your own database

    Provisioned and run by you

Amplify Data stores models in DynamoDB. SQL works only by connecting a PostgreSQL or MySQL database you provision, scale, and back up yourself.

Functions_

Any language, no CDK required_

Amplify functions are defined for Node.js, and every other language means writing custom CDK code. Appwrite Functions run in 13+ runtimes with Git deploys, cron, events, and local development built in.

Appwrite

13runtimes

  • Node.js
  • Python
  • Go
  • Bun
  • Deno
  • Dart
  • PHP
  • Ruby
  • Rust
  • .NET
  • Java
  • Kotlin
  • Swift

AWS AmplifyNode.js

Other languages need custom CDK code

Messaging_

Push notifications with no end-of-support date_

Amplify analytics and push notifications run on Amazon Pinpoint, which reaches end of support on October 30, 2026. Appwrite Messaging is part of the platform, next to your users and data.

Amplify messaging timeline

  1. May 20, 2025

    Amazon Pinpoint stops accepting new customers

  2. October 30, 2026

    Pinpoint reaches end of support, and Amplify analytics and push notifications stop working

Appwrite Messaging

  • Push

    FCM and APNs

  • Email

    SMTP and email providers

  • SMS

    Global SMS providers

One API for push, email, and SMS, with topics, scheduling, and your users and teams as targets.

Open source_

Your backend should not need an AWS account_

Amplify libraries are open source, but everything behind them runs only on AWS. Appwrite is open source end to end, so the same backend runs on Appwrite Cloud, any other cloud, or your own servers.

GitHub stars
57.6K
Contributors
800+

Self-host in one command

$docker run -it --rm … --entrypoint="install" appwrite/appwrite:2.3.0

  • No lock-in

    Move between Appwrite Cloud and your own servers by changing one endpoint.

  • Run it anywhere

    Self-host on any cloud or on premises for data residency and compliance.

  • Nothing hidden

    Read the code that handles your users and data, and audit how it works.

  • Fix it, extend it

    Patch, extend, or contribute back instead of waiting on a vendor roadmap.

AWS Amplify · Runs only on AWS

The Amplify libraries are open source, but every backend service behind them runs only on AWS.

Appwrite vs AWS Amplify_

The full-stack features, without the AWS overhead_

Both cover auth, data, storage, functions, and hosting. The difference is how many services, consoles, and bills it takes.

Checked against public pricing and documentation in October 2026.

Appwrite
AWS Amplify
Platform
Where it runs
Appwrite Cloud or any server

Same APIs, SDKs, and Console

AWS only

Libraries are open source, services are not

Consoles to manage
One

Every product in one project

Several

Amplify, Cognito, AppSync, DynamoDB, Lambda, S3, IAM

Backend definition
Console, CLI, or Terraform

Plus SDKs in 13+ languages

TypeScript with AWS CDK

Deployed as CloudFormation stacks

Per-seat pricing
No
No
Backend
Authentication
Yes

Appwrite Auth, 40+ OAuth providers, MFA, teams

Yes

Amazon Cognito

Database models
5

Tables, documents, vectors, PostgreSQL, MySQL

1

DynamoDB through AppSync GraphQL

Managed PostgreSQL and MySQL
Yes
Partial

Bring a database you run yourself

Function runtimes
13+
Node.js

Other languages through custom CDK code

Realtime subscriptions
Yes

Every service, one socket

Yes

GraphQL subscriptions on AppSync

Email, SMS, and push messaging
Yes

One API, 12 providers

Partial

Pinpoint-backed features end on October 30, 2026

Hosting
Git deploys, previews, and SSR
Yes
Yes
Bandwidth on the base plan
2TB included

On Pro

$0.15 per GB

After 15GB a month

Web application firewall
Yes

Rules per project, included

$15/mo per app

Plus AWS WAF usage

Buy and manage domains
Yes
Partial

Through Route 53

Pricing
Billing model
One plan with allowances

From $25/mo, budget caps

Per service, per request

Each AWS service is metered separately

Hard budget cap
Yes
No

AWS Budgets sends alerts

Fair play_

When Amplify might still fit_

Amplify is a capable way into AWS. It may still suit you if these describe your project.

  1. 01

    Your company already runs on AWS and wants every resource inside its own accounts and IAM policies.

  2. 02

    You want to define your backend in TypeScript and extend it with any AWS service through CDK.

  3. 03

    You rely on AWS credits, enterprise agreements, or compliance programs tied to AWS.

  4. 04

    Your data model fits DynamoDB access patterns and GraphQL through AppSync.

Why developers choose Appwrite over AWS Amplify_

For most teams that want to ship rather than operate AWS, yes. Appwrite gives you auth, five database models, storage, functions in 13+ runtimes, realtime, messaging, and hosting in one open-source project, with one Console and one bill. Amplify wires the same features together from Cognito, AppSync, DynamoDB, Lambda, and S3, each with its own console, limits, and pricing.

Go deeper_

See why teams make the switch_

Guides, deep dives, and product pages from the Appwrite team.

BlogChoosing the right platform to deploy your web apps: Vercel, Netlify, Amplify, and Appwrite Sites comparedHosting, previews, and pricing across four platforms.BlogHow to evaluate backend tools without locking yourself inA practical framework for keeping your options open.BlogNative databases vs Appwrite databases: which one should you pick?Tables, documents, vectors, and native SQL compared.ProductAppwrite SitesStatic, SSR, and CSR deploys from Git.ProductAppwrite MessagingEmail, SMS, and push from one API.DocsSelf-hostingRun the whole platform on your own servers.

Compare_

See how Appwrite stacks up elsewhere_

Appwrite vsSupabasePostgres development platformHosting, messaging, and permissions without SQL policies.Appwrite vsFirebaseApp development platformOpen source, self-hostable, and a free migration path.Appwrite vsVercelFrontend cloudFrontend hosting with the backend in the same project.Appwrite vsNetlifyWeb hosting platformYour site and its backend, in one project.Appwrite vsNeonServerless PostgresPostgres plus the whole backend around it.Appwrite vsAuth0Identity platform3x the free monthly active users and no growth penalty.Appwrite vsConvexReactive TypeScript backendActually open source, in any language.Appwrite vsCloudinaryMedia platformPay per origin image, not per variant.Appwrite vsClerkUser management and authenticationUsers and data in one place, no webhooks to sync.Appwrite vsPlanetScaleManaged MySQL and PostgresPostgres and MySQL, plus the backend around them.PricingOne plan for your whole backend and hosting.Compare plans

Ship a full stack from one Console_

Create a project and get auth, databases, storage, functions, messaging, and hosting, with no AWS account required.

Start building for freeView pricing