Deployment.sh

AWS Amplify alternative for full stack teams

AWS Amplify Hosting builds and serves front ends and bills build minutes, stored data, bandwidth and server-side rendering usage. Deployment keeps git push deploys, rollbacks and zero-downtime releases, but runs the web app, API, workers and database on servers you control for a flat panel subscription from 49 USD. Your traffic stops being a line item, and the whole stack lives in one panel with roles and an audit log.

plan.sh

$ deployment plan

Paste a repository and get a deploy plan

Paste a public GitHub or GitLab repository. We read only the manifests and store nothing beyond the plan.

Environment

Your servers stay in your own cloud account. No card needed for the demo.

See pricing

$ deployment plan

Building your deploy plan

$ deployment plan

$ deployment plan

Private repository or no stack found

Choose the framework and runtime and we build the full plan anyway.

Deployment and AWS Amplify side by side

Amplify is a hosting service inside AWS. Deployment is a panel for servers you own. Amplify figures below come from aws.amazon.com/amplify/pricing, checked in November 2026.

DeploymentAWS Amplify Hosting
ModelPanel that manages servers in your cloud accountManaged build and hosting service inside AWS
PricingFlat subscription from 49 USD, servers billed by your providerUsage across build minutes, storage, bandwidth and SSR
Build minutesBuilds run on your server, no per-minute charge0.01 USD per minute on the standard instance
BandwidthYour provider traffic allowance0.15 USD per GB served beyond 15 GB a month
Stored dataYour server disks and backups0.023 USD per GB per month
Workers and queuesRun beside the app on the same serverSeparate AWS services, each billed on its own
DatabasePostgreSQL, MySQL and Redis on your server or a dedicated oneSeparate AWS service
Teams and auditRoles and audit log from Team, SLA on EnterpriseAWS accounts and IAM

Where the cost lines cross

Amplify is honestly cheap for a small site. AWS itself shows about 8 USD a month for a modest app. The same page prices a site with 10,000 daily users, 1.5 MB per page view and two updates a month at 65.98 USD, and 65.92 USD of that is bandwidth at 0.15 USD per GB. Double the traffic and the hosting line doubles.

A server with several terabytes of included transfer carries that traffic for a fixed price. One 8 GB server at 25 to 50 USD plus Deployment Starter at 49 USD is 74 to 99 USD a month, or 49 to 74 USD billed yearly, and it also runs your API, workers and database. The crossover sits where bandwidth and extra AWS services together pass that number. See the Deployment plan limits and the PaaS versus own server cost breakdown.

Why teams leave Amplify for their own servers

The pattern is familiar. A front end starts on Amplify, then an API, a queue worker, a scheduler and a database appear, and each lands in a different AWS service with its own console, permissions and invoice. Developers spend time on IAM and service wiring instead of releases. Teams also want predictable monthly cost, one deploy history and one place to see logs and environment variables. Agencies add one more reason, which is clients who want the workload in their own cloud account.

Where AWS Amplify still wins

If your backend is already built on AWS managed services such as Cognito or AppSync, Amplify ties them together with little glue code. Static and low traffic sites are very cheap, there is no server to patch, and global delivery comes built in. Deployment suits products with a real backend that want one bill and one panel. If the backend already runs on Beanstalk environments, the Elastic Beanstalk alternative on your own EC2 covers that half of the stack. For other platform comparisons read the Vercel alternative and Netlify alternative pages. If you also email customers from your app, a hosted parser such as one that turns forwarded emails into JSON keeps inbound mail out of your own queue code.

Move from AWS Amplify in four steps

Keep the Amplify app running while you validate the new setup.

  1. 1. Prepare a server

    Connect your AWS account or any other cloud, or add an Ubuntu or Debian server over SSH, sized for the web app, workers and database.

  2. 2. Connect code and settings

    Link the repository and copy the commands from amplify.yml into a build command and a start command. Move environment variables into encrypted settings.

  3. 3. Replace the managed pieces

    Point the app at the database on your server, run workers as managed processes and set the scheduler. Keep S3 for uploads if you want it.

  4. 4. Cut over

    Test on a temporary domain, lower DNS TTL, switch DNS and keep the Amplify app until traffic checks out.

AWS Amplify alternative questions

What is the best alternative to AWS Amplify?

Deployment is a strong AWS Amplify alternative when your product is more than a front end. It gives git push deploys, rollbacks and a team panel for web apps, APIs, workers and databases on servers you control, for a flat subscription. Amplify stays better for small sites inside an AWS-only stack.

How much does AWS Amplify cost?

Amplify Hosting bills usage. Build minutes on the standard instance cost 0.01 USD per minute, data served beyond 15 GB costs 0.15 USD per GB, and stored data costs 0.023 USD per GB. AWS lists a worked example of 65.98 USD a month for a site with 10,000 daily users.

Is AWS Amplify cheaper than running my own server?

For a small static site, Amplify is cheap, with AWS quoting about 8 USD a month in one example. Traffic changes that. The 10,000 daily user example costs 65.98 USD, almost all of it bandwidth, while a server with a generous transfer allowance bills a fixed amount.

Can I host a backend with workers and a database on Amplify Hosting?

Amplify Hosting serves front ends and server-rendered pages. Long-running workers, queues and a self-managed database belong to other AWS services, each with its own bill and setup. On Deployment, the app, workers, scheduler and database run on the same server or on dedicated ones.

How do I move from AWS Amplify to my own servers?

Connect a server, link the repository, copy the Amplify build settings into a build command and a start command, and move environment variables into encrypted settings. Test on a temporary domain, lower the DNS TTL, switch the domain and keep the Amplify app until traffic checks out.

Run the whole stack on servers you control

Try the repository demo, price your traffic against a fixed-cost server and connect your cloud account when you are ready.

Try the demo