Every platform here takes code from a Git repository, builds it and puts it online with HTTPS. That is the CI/CD part, and it no longer sets them apart. What does: whether your app can be a server or only functions, whether a database and a disk come with it, whether every change gets a preview, and how the bill behaves when traffic grows.
They come from two directions. Vercel, Netlify, Cloudflare Workers and AWS Amplify grew out of frontend hosting: a global CDN with functions beside it. Railway, Render, Fly.io, Heroku, DigitalOcean App Platform and Apposters run your app as a server in a container, closer to a classic host.
We scored all ten on fifteen criteria, from the side of the developer or founder who ships the app. The scores reward platforms that are cheap to start, run any kind of app, preview every change and keep the bill predictable.
Platform reviews
Ranked by average score. Each review covers what the table cannot: what the platform is built for, who it suits and where it hurts.
1. Railway
Best for: full-stack apps that need a database next to the server.
Railway runs every part of an app as a service on one canvas: the web server, a worker, a cron job, Postgres or Redis, each with its own volume when it needs one. It builds a repository with or without a Dockerfile, deploys on every push from GitHub, and can start a full copy of the environment for every pull request.
You pay for the memory, CPU, disk and traffic your services use, with $5 of usage included in the $5 Hobby plan, and a hard limit you set stops the services before the bill passes it. The free plan is a trial and a small monthly credit, not a place to keep an app online. Servers run in four regions, with no CDN in front of them.
Strong
- Databases, workers and volumes in one project.
- A copy of the environment for every pull request.
- Builds almost any repository with no config.
- A hard spending limit.
Weak
- No lasting free plan.
- Four regions and no CDN.
- GitHub is the only Git provider.
Pick it if you want the whole stack, database included, in one place for a few dollars.
Skip it if your app is a static frontend that a CDN would serve for free.
2. Cloudflare Workers
Best for: sites and APIs that should be fast everywhere and cheap at any traffic.
Cloudflare's hosting is two products growing into one: Pages for sites and Workers for code. Since 2025 a Worker can serve a whole site, static files included, and new features land on Workers first. Code runs in Cloudflare's network in hundreds of cities, with D1 (a SQL database), KV, R2 object storage and Durable Objects for state beside it.
The free plan allows commercial use and 100,000 requests a day, with static files free, and the paid plan starts at $5 a month. The catch is the model. Workers run on Cloudflare's own runtime rather than a Node.js server, so some libraries need a compatibility flag or a change, long-lived connections go through Durable Objects, and containers run only when a Worker starts them. The paid plan has no hard spending cap, only notifications.
Strong
- Hundreds of locations, no region to pick.
- A free plan that allows commercial use.
- A database, storage and state of its own.
- $5 a month for the paid plan.
Weak
- Not a regular server: some code needs changes.
- Containers only behind a Worker.
- No hard spending cap.
Pick it if you want speed everywhere and a tiny bill, and your code fits the runtime.
Skip it if your app is an ordinary server with long-running processes.
3. DigitalOcean
Best for: containers, workers and jobs at a fixed price per month.
App Platform is DigitalOcean's managed layer over its cloud. Point it at a repository on GitHub or GitLab and it builds from the Dockerfile or detects the language with buildpacks, then runs web services, background workers, scheduled jobs and functions as parts of one app.
Pricing is per container size, from $5 a month, with bandwidth beyond the included amount charged extra, so the bill is easy to predict. Up to three static sites are free. Databases are DigitalOcean's managed ones, from a small development database upwards. What it lacks is a preview for every pull request, which takes a GitHub Action, and a disk: files the app writes are gone after a redeploy, so storage goes to Spaces or a database.
Strong
- Web services, workers, jobs and functions in one app.
- Fixed prices per container.
- Dockerfile or buildpacks, both with no config.
- Managed databases next door.
Weak
- No disk that survives a redeploy.
- No built-in pull request previews.
- A CDN for static files only.
Pick it if you want servers at a predictable price and may grow into the rest of DigitalOcean.
Skip it if you want a preview of every pull request out of the box.
4. Render
Best for: teams moving off Heroku who want servers, workers and Postgres.
Render is the closest thing to Heroku's model on a newer platform: web services, background workers, cron jobs and private services, built from a Dockerfile or from your code and deployed on every push from GitHub, GitLab or Bitbucket. It detects the language and suggests the build and start commands, which you confirm once.
The free plan runs a web service that sleeps after 15 minutes without traffic and takes about a minute to wake, and the free Postgres database expires after 30 days. Paid instances start at $7 a month and can have a persistent disk. Pull request previews are built in for single services, while preview environments for the whole stack need a Blueprint file and a paid team plan. Servers run in five regions, with a CDN for static sites.
Strong
- Servers, workers, cron jobs and Postgres on one platform.
- Builds from a Dockerfile or your code.
- Fixed instance prices.
- Rollback to any earlier deploy.
Weak
- Free services sleep and the free database expires.
- No functions, and no scaling to zero on paid plans.
- Disks only on paid instances.
Pick it if you want a classic server platform that works like Heroku and costs less.
Skip it if you need servers in many regions at once.
5. Netlify
Best for: frontend teams who want a preview of every change.
Netlify made the Git-to-CDN workflow popular: push a branch, get a deploy preview with its own address, merge, and the site is live on a global CDN. It detects most frontend frameworks, runs serverless and edge functions next to the site, and publishes any earlier deploy again in one click.
Since 2025 new accounts are billed in credits. The free plan pauses a site when its credits run out instead of charging, and paid plans start at $9 a month. Netlify DB, a Postgres database run by Neon, and Netlify Blobs cover storage. What Netlify does not do is run a server: no Docker, no WebSockets, no process that outlives a function.
Strong
- Deploy previews for every pull request.
- A free plan that allows commercial use.
- Functions and edge functions next to the site.
- One-click rollback to any deploy.
Weak
- No servers or containers.
- The database is a partner's.
- Credits take some reading to predict.
Pick it if you build frontends and want every change previewed.
Skip it if your app needs a long-running server.
6. Fly.io
Best for: apps that should run close to their users in many regions.
Fly.io runs your Docker image as small virtual machines, called Machines, in regions around the world, behind an anycast network that sends each user to the nearest one. Its command-line tool reads the repository, writes a Dockerfile and a config file when it needs to, and deploys. Volumes, private networking and Managed Postgres are part of the platform.
There is no free plan for new accounts, only a trial, and no fixed plan either: you pay per second for each machine, from about $2 a month for the smallest, and nothing caps the bill. Machines can stop when idle and start on the next request. Most of the work happens in the command line. Deploys on push and previews for pull requests go through a GitHub Actions workflow you add, and going back means deploying an earlier image.
Strong
- Servers in many regions at once.
- Docker images with volumes and private networking.
- Machines that stop when idle.
- Low prices per machine.
Weak
- No free plan for new accounts.
- No spending cap.
- Git deploys, previews and rollbacks are left to you.
Pick it if latency matters and you are at home in the command line.
Skip it if you want a dashboard that does everything for you.
7. Vercel
Best for: Next.js and other frontend frameworks.
Vercel makes Next.js and is the best home for it: every push gets a preview address, the framework's features work without setup, and pages are served from a global CDN with functions in a region you pick. Dozens of frameworks build with no config, and Git deploys work with GitHub, GitLab and Bitbucket.
It ranks seventh because of what it is not. The free Hobby plan is for personal, non-commercial projects, so a business pays $20 a month per member. Functions have a time limit and no WebSockets, there is no Docker, storage is Vercel Blob rather than a disk, and databases come from partners in its marketplace. Spend Management can pause projects at a limit you set, which matters on a usage-based bill.
Strong
- Preview deploys and instant rollback.
- The best support for Next.js.
- Zero-config builds for most frameworks.
- A global CDN with functions in many regions.
Weak
- The free plan is non-commercial.
- No servers or containers.
- Databases only through partners.
Pick it if you build with Next.js or another frontend framework and want the smoothest workflow.
Skip it if your backend is a long-running server.
8. AWS Amplify
Best for: teams that already run on AWS.
Amplify Hosting builds frontend and server-rendered apps from GitHub, GitLab or Bitbucket, serves them through CloudFront and gives pull requests a preview. Amplify's backend side, defined in TypeScript since its second generation, adds a DynamoDB data layer, sign-in, storage on S3 and Lambda functions.
It has no plan of its own: you pay per build minute, per gigabyte served and per request, and AWS's credits for new accounts cover a small app for a while. Nothing caps the bill, though budgets can send alerts. There is no Docker and no long-running server, and going back to an earlier version runs its build again.
Strong
- The whole of AWS within reach.
- Previews for pull requests.
- Data, sign-in and storage defined in code.
- Pay only for what you use.
Weak
- No servers or containers.
- No spending cap.
- The AWS console and permissions take time to learn.
Pick it if your company is on AWS and the frontend should live there too.
Skip it if you want one simple bill and one simple dashboard.
9. Heroku
Best for: teams that want a mature platform with fixed prices.
Heroku made push-to-deploy famous and still does it well. Buildpacks detect the language, dynos run web processes and workers, and Heroku Postgres, Key-Value Store and hundreds of add-ons attach in a click. Pipelines, review apps for pull requests and rollback to any release are built in, and a Dockerfile works too, with a heroku.yml file.
Free dynos ended in November 2022, so the cheapest dyno is the $5 Eco plan that sleeps, and an always-on Basic dyno is $7 a month. The file system is wiped on every restart, there are no functions, and the common runtime has two regions, the US and Europe. In return the bill is flat: dynos and add-ons have fixed monthly prices.
Strong
- Buildpacks that detect most languages.
- Workers, Postgres and add-ons in a click.
- Fixed monthly prices.
- Rollback to any release.
Weak
- No free plan.
- No persistent disk.
- Two regions on the common runtime.
Pick it if you want a proven platform and a bill that never surprises.
Skip it if you want a free plan or files that stay on disk.
10. Apposters
Best for: a GitHub repository that should go live as a product, app and site together.
Apposters runs the app from your repository at /app on its own address, built from your Dockerfile, or without one for Node.js, Python, Go and static sites, and puts a product site written by AI from the repository around it: a landing page, About, FAQ and Sign In. When a build fails it explains why in plain words and can rewrite the Dockerfile for you, and a setup step reads the settings the app asks for from the repository's own files.
The site is free at your-name.apposters.com with HTTPS. Embed App, the app hosting, is a flat $19 a month per app with 512 MB of memory, one CPU and 3 GB of disk, more of either at a fixed price, and a volume that survives redeploys. It ranks last here because it is younger and narrower: a deploy is started from the dashboard or the API rather than by a push, there are no previews, functions or managed databases, a custom domain is a paid add-on, and everything runs from one location without a CDN.
Strong
- The app and its product site from one repository.
- A flat price per app, nothing metered.
- A Dockerfile fix from the AI when a build fails.
- A disk that survives redeploys.
Weak
- No deploy on push and no previews.
- No managed database.
- One location, no CDN.
Pick it if you have a repository and want it live as a product, app and site, at a fixed price.
Skip it if you need preview deploys, a database or users on several continents.