Vercel alternatives: choosing a host for your backend

The right Vercel alternative depends on what your application runs. Compare Lizard, 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.

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.

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.

A build-cost example you can reproduce

Assume 200 builds, each with exactly 3 billable minutes, on a Vercel Standard machine with 4 vCPUs. At $0.0035 per CPU-minute:

200 builds × 3 minutes × 4 vCPUs = 2,400 CPU-minutes
2,400 × $0.0035 = $8.40 before any applicable plan credit

This is a build charge, not the complete monthly bill. Basic builds are included on Vercel Hobby; plan eligibility and machine choice matter. A build performed inside a running Lizard service or Lizard Sandboxes consumes that resource's compute even though the separate hosted build step has no charge.

An allowance example

If a Lizard Pro account sends 200 GB during a billing period and has no other traffic using its 300 GB allowance, the egress overage is zero. Charging all 200 GB at the overage rate would misstate the bill.

For an illustrative Pro resource subtotal of $40, with all $29 of credit available and applicable, the total is 29 + max(0, 40 − 29) = $40 before tax. Adding the plan fee without subtracting its included credit would count part of the cost twice.

A savings comparison needs measurements from the same application on both hosts. We do not publish a savings ratio from assumed CPU and memory use.

Move one service before moving the whole app

1. List Vercel-specific dependencies: request handlers, image processing, cache behaviour, scheduled work, storage and environment variables.
2. Choose an API or worker that can run independently. Give it a production start command and a health endpoint where appropriate.
3. Deploy a test copy and connect it to a separate test database. Configure credentials through service settings.
4. Test authentication, retries, timeouts, file handling and restarts with representative traffic.
5. 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? That depends on measured use and the features you need. Compare the final invoice after fees, allowances and credits. A CPU rate alone cannot answer the question.

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.