• Docs
  • Talk to an expert
Blog
Blog
BlogProductCase studiesNewsInsights
Blog

Vercel alternatives for full-stack applications (2026)

cloud application platformPaaSdatapreview environmentscloudTask containers
16 November 2026
Share
This post is also available in German and in French.

Note: pricing and features may have changed since publication. Check each provider’s documentation for current details.

Vercel alternatives for full-stack applications fall into three groups, based on how each platform runs the backend:

  • Application platforms (Upsun Cloud, Render, Railway) run the frontend, backend, workers, and databases as long-running services in one project.
  • Frontend clouds with functions (Netlify) pair frontend hosting and deploy previews with serverless functions and a managed Postgres database.
  • Edge and microVM platforms (Cloudflare Workers, Fly.io) run code close to users, with more assembly needed for data and background work.

Vercel itself added more backend features in 2026, including Services, container images, Queues, and Daemons, several of which are still in beta. Which alternative fits depends on where the application's data lives, how much background work it runs, and how many cloud providers the team already uses.

Why do teams look for Vercel alternatives for full-stack applications?

Vercel's strengths are well established. It created Next.js, gives every push a preview deployment, serves frontends from its global network, and bills functions on Fluid compute by active CPU time. In 2026, it also moved further into backends:

  • Vercel Services, introduced in June 2026 as a public beta, deploys several frontends and backends from one project on a shared domain.
  • Container images let Vercel Functions run any Dockerfile. The container runtime is in beta.
  • Vercel Queues is in public beta, and Vercel Workflows is generally available for durable, multi-step jobs.
  • Vercel Daemons, in public beta since October 2026, runs always-on background workers from container images.

Full-stack teams still run into a few limits:

  • Request length: Vercel Functions default to 300 seconds and can run for up to 800 seconds on Pro and Enterprise plans.
  • Databases from partners: Vercel no longer offers its own Postgres database. Databases come from Marketplace providers such as Neon, Supabase, and AWS Aurora, billed through Vercel but run by another company.
  • Workers in beta: during the beta, Daemons run only in production, with no autoscaling, inbound HTTP or TCP traffic, or persistent local storage, and preview deployments do not start them.

How do the Vercel alternatives compare at a glance

Platform

Backend runs as

Databases

Background work

Preview environments

Runs on

Upsun CloudApps in containersPostgreSQL, MySQL, Redis, and more in the projectWorkers, cron jobs, task containersEvery Git branchAWS, Azure, Google Cloud, OVHcloud
NetlifyFunctionsNetlify Database (Postgres)Background functions, 15 minDeploy PreviewsNetlify's network
RenderAlways-on servicesRender Postgres, Key ValueWorkers, cron jobs, WorkflowsProfessional plan and above5 regions
RailwayAlways-on servicesPostgres, MySQL, RedisServices, cron jobsPR environments4 regions
Fly.ioMachines (microVMs)Managed PostgresMachinesSet up through CIRegions worldwide
CloudflareWorkers and ContainersD1, or Postgres through HyperdriveQueues, Workflows, Cron TriggersPreview URLsCloudflare's global network

What are the main Vercel alternatives for full-stack applications?

1. Upsun Cloud

Upsun Cloud runs the whole application from one .upsun/config.yaml file in the Git repository. Frontends and backends run as apps, next to managed services such as PostgreSQL, MySQL, Redis, and OpenSearch. Workers run continuously, cron jobs run on a schedule, and task containers run on demand for up to 24 hours against the app's own database. Every Git branch can have its own environment that runs the same apps and services.

The same configuration deploys to regions on AWS, Azure, Google Cloud, and OVHcloud. That helps teams whose applications are already spread across providers, each with its own pipeline, runbook, and audit process, keep one workflow for all of them.

Trade-off: apps run as always-on containers in the project's region. Upsun Cloud does not run code on a global edge network, apps do not scale to zero, and there are no GPUs.

2. Netlify

Netlify offers a frontend workflow close to Vercel's, with Deploy Previews, serverless functions, and Netlify Database, a managed Postgres database that became generally available in April 2026 on credit-based plans.

Trade-off: synchronous functions run for up to 60 seconds, scheduled functions for 30 seconds, and background functions for 15 minutes. There is no always-on worker.

3. Render

Render runs web services, private services, background workers, and cron jobs as always-on instances, with Render Postgres, Render Key Value, and Render Workflows for durable tasks. Preview environments are included on the Professional plan and above.

Trade-off: paid instances bill while they run, whether or not they receive traffic, and services run in five regions: Oregon, Ohio, Virginia, Frankfurt, and Singapore.

4. Railway

Railway deploys services, databases such as Postgres, MySQL, and Redis, and cron jobs from a visual project canvas, with pull request environments and usage-based billing. Plans start at $5 a month for Hobby and $20 a month for Pro.

Trade-off: services run in four regions: California, Virginia, Amsterdam, and Singapore.

5. Fly.io

Fly.io runs applications as Machines, lightweight microVMs that bill by the second and can be placed in regions around the world. Managed Postgres v2 reached general availability in mid-2026.

Trade-off: teams handle more of the setup themselves, Managed Postgres is available in fewer regions than Machines, and preview environments are set up through CI rather than built in. 

Fits: latency-sensitive applications that need to run close to users in several regions.

6. Cloudflare Workers

Cloudflare runs Workers on its global network, with Containers (generally available since April 2026) for workloads that need a full Linux environment. D1, R2, Queues, Workflows, and Durable Objects cover data and background work, and Hyperdrive connects Workers to an external Postgres database.

Trade-off: Workers have 128 MB of memory and their own runtime, and a D1 database is limited to 10 GB. 

Fits: applications that run most of their logic at the edge. 
 

What should a full-stack team check before moving off Vercel?

Where does the database live?

On Vercel, Netlify, and Cloudflare, the database is a separate product: a Marketplace partner on Vercel, Netlify Database (Postgres) on Netlify, and D1 or an external Postgres on Cloudflare. 

On Upsun Cloud, Render, and Railway, the database runs in the same project as the app. On Upsun Cloud, it is declared as a service in .upsun/config.yaml and connected to the app through a relationship.

What does a preview environment include?

Vercel and Netlify preview the frontend and functions on every push, and database branching depends on the database provider. For example, Neon's Vercel integration creates a database branch for each preview deployment. 

On Upsun Cloud, a branch environment runs the same apps, workers, and services as production, and it can clone the parent environment’s data, including databases and files, when it is created. Teams that copy production data into previews define their own sanitization script in a deploy hook. 

How long can background work run?

Vercel Functions stop at 800 seconds on Pro and Enterprise plans, and Netlify background functions stop at 15 minutes. Upsun Cloud workers run continuously, and Upsun task containers run on demand for up to 24 hours, so long imports, reports, and agent runs can work against the app's own database.

Which clouds, regions, and certifications does the team need?

Upsun Cloud runs in regions on AWS, Azure, Google Cloud, and OVHcloud, and IBM Cloud through its marketplace. Upsun holds ISO 27001 certification, a SOC 2 Type 2 report, and PCI DSS Level 1 compliance for its AWS, Azure, and Google Cloud regions; the OVHcloud region is excluded, and HIPAA workloads run only in the US-4 region. 

Vercel holds a SOC 2 Type 2 report, ISO 27001:2022 certification, and PCI DSS v4.0 attestations, and offers a HIPAA BAA to eligible Pro and Enterprise teams. 

How does the full bill add up?

Vercel bills per seat plus usage, and Marketplace databases add their own charges to the invoice. Upsun Cloud bills the CPU, memory, and storage allocated to each environment, including preview environments. 

How do you move a full-stack app from Vercel to Upsun Cloud?

  1. Generate a starting config. Run upsun project:init at the root of the repository. It detects Next.js and writes a .upsun/config.yaml file.
  2. Define each app. A Next.js frontend runs as a Node.js app with next start. Each backend in the repository becomes another app in the same file.
  3. Replace the Marketplace database. Add a service such as PostgreSQL and connect it to the app with a relationship. Connection details reach the app as environment variables.
  4. Move scheduled and background work. Cron jobs from vercel.json move to crons on the app, queue consumers move to workers, and long jobs move to task containers.
  5. Move environment variables. Set them with Upsun's secrets and environment configuration, for example upsun variable:create.
  6. Test on a branch, then switch the domain. Push a branch to get a full environment, check it, then merge and update DNS.

Frequently asked questions

Can Next.js run outside Vercel?

Yes. Next.js runs as a Node.js server with next start, so any platform that runs Node.js can host it, including Upsun Cloud, Render, Railway, and Fly.io. Netlify and Cloudflare run Next.js through adapters. Features that rely on Vercel's network, such as edge caching, can need extra setup elsewhere. 

Which cloud providers does Upsun Cloud run on?

Upsun Cloud has regions on AWS, Azure, Google Cloud, and OVHcloud, and is available on IBM Cloud through the IBM Cloud marketplace. Each project runs in the region chosen for it, and the same .upsun/config.yaml format works in every region, so teams with projects on different providers keep one workflow instead of a separate pipeline and runbook for each. 

Can Upsun Cloud run a frontend and a backend in different languages?

Yes. One .upsun/config.yaml can define several apps, for example, a Next.js frontend and a Python API, each with its own runtime. They build and deploy together, and routes send each path or domain to the right app. 
 

Stay updated

Subscribe to our monthly newsletter for the latest updates and news.

Deploy possibility.
Try Upsun for free.

Build with DispatchDeploy on Cloud