The right Vercel alternative depends on what your application runs. Compare Lizard (lizard.build), Railway and Render for services that stay active between requests. Consider Cloud Run for an HTTP service that can scale down when demand falls. Keep Vercel on your shortlist when its frontend workflow and request-driven compute fit your app.
This comparison comes from Lizard. We checked the linked product documentation and billing terms on 9 September 2026. The calculations below are examples with stated inputs, not performance tests or customer savings figures.
Start with the runtime you need
A Dockerfile describes how to package an application. It does not tell you how a hosting service schedules, stops or bills that application.
Vercel now supports container images for Functions. Its Services documentation says Services use Function compute and inherit Function limits. Check the current duration, filesystem and connection limits for the specific feature and plan you intend to use.
For a conventional queue consumer, a process that keeps a connection open, or a scheduler that runs outside HTTP requests, test that lifecycle before moving. A managed queue or workflow can solve the same business problem, but it can also require changes to your code.
| Your requirement | Options to evaluate | What to test first |
|---|---|---|
| Frontend previews and a request-driven backend | Vercel | Framework behaviour, cache rules and production limits |
| API plus a separate queue consumer | Lizard, Railway, Render | Worker restarts, retries and database access |
| An HTTP container with uneven traffic | Cloud Run | Cold starts, concurrency and minimum instances |
| Direct control of a server | A VPS with a deployment tool | Patching, backups and your response to failures |
These are starting points for a trial. None establishes a universal winner. Our PaaS comparison covers the broader choice.
Where Lizard fits
Lizard runs web services and workers, offers Managed Postgres, Managed Redis and Managed Object Storage, and exposes deployment and operations through the Lizard CLI.
That fits a backend with a familiar process model: start the API, run the worker separately, and give each service its own configuration. A coding agent can read structured deployment output, inspect logs and run a specific command inside a service. It still needs to check the result; a successful build alone does not prove that logins, jobs and database writes work.
Provisioning a database and connecting your application are separate steps. Your application must read the connection variable you configure. Keep app data in the database or an attached Persistent Volume, according to the service's needs. A writable container filesystem by itself is not a backup or a promise of durability across deployments.
When Vercel is a better fit
Stay with Vercel when your team depends on its preview workflow, frontend tooling or managed request lifecycle and those features already meet your needs. Replacing a working deployment system has a cost even if another provider advertises a lower CPU rate.
An application with little traffic can also benefit from compute that does not remain active between requests. A running Lizard service can still consume memory while waiting for work. Compare the actual workload and latency requirements, including whether you are willing to accept cold starts.
You can keep the frontend on Vercel and move only the worker or API. In that design, include cross-provider data transfer, authentication and request latency in the test.
Compare bills after fees, credits and allowances
The monthly total depends on more than runtime CPU. Record the plan, billing period, region, seats, database, storage, requests, traffic and builds. Apply each allowance to its own meter and each credit once.
| Billing term | Lizard | Vercel Pro |
|---|---|---|
| Base plan | No monthly subscription | $20/month with one deploying seat |
| Included usage credit | $10 trial credit, valid for 31 days; purchased credits do not expire | $20 per team, not per seat |
| Additional deploying seats | No separate seat charge | $20/month each |
| Internet transfer | $0.045/GB from the first byte | Current Pro terms include a Flat Rate CDN tier with 1 million CDN requests and 1 TB of data transfer |
| Hosted builds | Builds are billed | Paid build machines bill by CPU-minute |
Sources: Lizard pricing, Vercel Pro terms and Vercel build billing. CDN transfer, origin transfer and Function invocations are distinct Vercel meters. Check the terms your account uses before reusing an older estimate.
Hosted build costs: Lizard and Vercel
Lizard charges for builds. Include those charges when comparing deployment costs.
For a paid Vercel Standard machine with 4 vCPUs, 200 builds at exactly 3 billable minutes each use 2,400 CPU-minutes. At $0.0035 per CPU-minute, that is $8.40 before plan credit and tax, or $0.042 per build. Vercel build rates, checked 15 September 2026.
Vercel credits can cover some or all of this usage, so $8.40 is not necessarily an extra payment on top of the plan. Basic builds are included on eligible Vercel Hobby projects. This is a Vercel build-cost example, not a build-speed comparison or the full monthly bill.
Where no subscription lowers the bill
Lizard charges 200 GB of outgoing traffic at 200 × $0.045 = $9. There is no bundled traffic allowance to subtract. Vercel Pro includes a CDN allowance, so compare that meter separately from Function and origin traffic.
For an illustrative small app running for 720 hours, assume average measured use of 0.01 vCPU and 0.1 GB of memory, plus 10 GB of outgoing traffic. No database, retained storage or paid add-ons are included. At Lizard rates:
Lizard costs less for this small-app example than the $20 Vercel Pro monthly minimum, provided Lizard top-up fees allocated to this usage stay below the $18.47 difference. Three deploying seats raise that Pro minimum to $60. These are paid-plan comparisons before tax and trial credits; Vercel Hobby can cost $0 for an eligible project. We do not assume identical resource consumption across the two runtimes. Vercel Pro terms, checked 15 September 2026.
Purchased credits pay for usage and do not expire. A top-up can exceed this month’s usage because the unused balance stays available; the top-up screen shows its fee and total charge.
This example shows a specific price advantage from having no monthly minimum. For a larger app, compare measured resource use, included CDN traffic and required features on both hosts before estimating savings.
Move one service before moving the whole app
- List Vercel-specific dependencies: request handlers, image processing, cache behaviour, scheduled work, storage and environment variables.
- Choose an API or worker that can run independently. Give it a production start command and a health endpoint where appropriate.
- Deploy a test copy and connect it to a separate test database. Configure credentials through service settings.
- Test authentication, retries, timeouts, file handling and restarts with representative traffic.
- Measure cost and latency, then plan the database and domain cutover. Keep a rollback path until you have checked writes on the new deployment.
For a GitHub repository, start with the Git deployment guide. For a local project, use the upload deployment guide. The CLI configuration reference explains how to keep deployment settings repeatable.
FAQ
Can Vercel run a Dockerfile? Yes. Vercel documents container-image support for Functions. Check the runtime limits as well as the packaging support before treating it as a replacement for an always-running backend.
Is Railway billed as a flat server tier? No. Railway meters resource consumption and applies the paid plan's subscription fee toward usage. Its billing model differs from buying a fixed instance size. See the Railway pricing documentation.
Can I keep Vercel for the frontend? Yes. A separate API or worker can run elsewhere. Test cross-origin requests, cookie settings, authentication and network costs as part of that split.
Which option is cheapest? For the small app priced above, Lizard’s resource cost is about $1.53 plus payment fees, below Vercel Pro’s $20 monthly minimum. Lizard also has no seat fee. Vercel Hobby may be free for an eligible project, and included CDN traffic can change the result for a larger app.
What should an AI coding agent verify after deployment? The live URL, health checks, logs and a real user flow. For a backend, also check database writes, worker execution and recovery after a restart. The Claude Code deployment guide shows that workflow.
Originally published at Lizard (lizard.build).
Top comments (0)