AWS Amplify is AWS's toolkit and hosting service for web and mobile apps, whose Gen 2 backends run on Cognito, AppSync, DynamoDB, Lambda and S3. Pages here cover moving to self-hosted Supabase or Appwrite.
Comparing an Amplify Gen 2 backend, defined in TypeScript on the AWS CDK and spread across Cognito, AppSync, DynamoDB, Lambda and S3, with self-hosted Supabase on Postgres: data model, auth, functions, realtime, cost visibility and lock-in.
Moving an Amplify backend to self-hosted Supabase: exporting DynamoDB tables to S3 and reshaping them into Postgres tables, moving Cognito users (whose passwords cannot be listed), replacing AppSync resolvers and Lambda functions, and copying S3 files.
Cost of ownership by component: Amplify Hosting build minutes, storage, data served and SSR charges plus separately billed Cognito, AppSync, DynamoDB, Lambda and S3, against servers running self-hosted Supabase or Appwrite and the time to operate them.
What an Amplify exit involves: DynamoDB export to S3 (which needs point-in-time recovery) in DynamoDB JSON or Ion, Cognito user attributes through ListUsers without passwords, S3 objects, and the backend TypeScript and CDK code to rewrite.
Replacing Amplify Hosting's builds, CDN and server-side rendering for Next.js and other frameworks with Coolify or Dokploy on your own servers: build minutes and SSR charges against fixed servers, preview deployments and custom domains.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.