10 Best Vercel Alternatives for Next.js in 2026

The best Vercel alternatives for Next.js in 2026 are Temps, Railway, Render, Netlify, Coolify, Fly.io, Cloudflare, DigitalOcean App Platform, AWS Amplify and Docker on a VPS. The right pick depends on whether you want managed simplicity or full ownership. For teams cutting costs, self-hosted Temps is free and includes built-in analytics, error tracking and session replay, so you pay only for the server. For managed hosting without per-seat pricing, Railway (Pro is $20/month per workspace with unlimited seats), Netlify (Pro is $20/month per team with unlimited members) and Render all qualify.

Disclosure: Temps publishes this blog, so treat our own entry as a vendor describing its product. Every other tool is described from its own documentation and pricing page (checked October 2026), and we say where another tool is the better fit. Corrections: github.com/gotempsh/temps/issues.

1. Temps: self-hosted, runs Next.js with next start on Node.js, bundles analytics + error tracking + session replay + uptime monitoring, free to self-host (MIT / Apache 2.0)
2. Railway: managed, usage-based pricing, no per-seat fee on any plan ($20/month per workspace on Pro), full SSR
3. Render: managed, free instances for side projects, full SSR, free services spin down when idle
4. Netlify: managed, static-first, Next.js runs through Netlify's adapter
5. Coolify: self-hosted, one of the larger template catalogues (360+; Easypanel and Dokploy list more), focused on deployment
6. Fly.io: managed VMs in 17 regions, full Docker/Node.js compatibility
7. Cloudflare: edge platform with free static bandwidth; server-rendered Next.js runs on Workers via vinext or OpenNext
8. DigitalOcean App Platform: managed, simple flat pricing, no built-in analytics
9. AWS Amplify: managed, pay-per-use, native AWS integration, complex pricing
10. Docker + VPS: self-hosted DIY, lowest possible cost, you maintain everything yourself

Netlify and Cloudflare come up most often in this search, and both run Next.js through an adapter layer that maps it onto their own runtime, which can mean gaps on newer Next.js features. Temps runs Next.js on a standard Node.js server, so there's no adapter to keep in sync with each Next.js release.

Vercel Pro is a $20/month platform fee that includes one deploying seat and $20 of usage credit; each extra deploying seat is $20/month, per Vercel's pricing page. A five-developer team pays $100/month before usage. Add CDN traffic past the included 1 TB and 1M requests on Flat Rate CDN (10M requests on on-demand pricing) (a Flat Rate CDN tier of $20 to $300 a month for Pro teams created since 8 September 2026, or from $0.15/GB on demand for older teams), function compute and image optimization, and bills climb. One developer was billed $46,485 after a traffic spike on a static site, an extreme case but a cautionary one. For Vercel's plans and worked bills, see Vercel pricing 2026.

Prices in this guide were checked on each vendor's pricing page in October 2026.

For the cheapest way to host a Next.js app, with worked costs, see the Next.js hosting cost breakdown.

Which Vercel Alternative Is Best for Next.js in 2026?

For most teams, Temps is the best Vercel alternative for Next.js in 2026. It runs full SSR and ISR, deploys via git push, and bundles analytics, session replay, error tracking and uptime monitoring in one self-hosted platform that's free under MIT / Apache 2.0. The only cost is the server, with no per-seat fees and no bandwidth bills.

If you need a fully managed platform with no ops work, Railway is a strong option for solo developers and teams alike, since no plan charges per seat, with full SSR support and built-in databases. Netlify is strong for static-first sites, though its Next.js support goes through an adapter.

Here's how the top three compare head-to-head:

Temps vs. Coolify vs. Dokploy: the self-hosted category

If you've already decided to self-host, the shortlist is usually Temps, Coolify and Dokploy. Coolify and Dokploy focus on deployment: they orchestrate Docker containers and give you a dashboard, but error tracking and session replay are separate tools you install and maintain. Temps is the only one of the three that bundles web analytics, session replay, error tracking and uptime monitoring into the same platform as deployment. Coolify has the bigger community (about 62,700 GitHub stars in October 2026) and a wider one-click template catalogue (360+), and added opt-in traffic analytics in v4.4; Temps trades that catalogue breadth for a bundled observability stack. See Temps vs Coolify.

Why Are Developers Looking for Vercel Alternatives?

Seat fees are the most common pain point. With $20 per deploying seat, a 10-developer team pays $200/month for platform access before any compute, bandwidth or add-ons. Vercel's September 2025 restructuring added a $20 usage credit and free viewer seats, but kept per-seat pricing for anyone who deploys.

Cost isn't the only reason

Vendor lock-in is the other concern. Vercel-specific services such as @vercel/analytics, Vercel Blob and Vercel's request headers tie code to the platform, and the longer a project runs there, the more of them it tends to use.

Data control matters too. Teams in regulated industries increasingly want infrastructure they control. Vercel Enterprise offers more control and compliance options, but Vendr reports a median contract of $52,825 a year, which is out of reach for most startups.

If the problem is Next.js itself rather than where it runs, that's a framework question: see Next.js alternatives in 2026 for React Router, Nuxt, Astro and SvelteKit.

Is self-hosting right for everyone? No. Here's the full spectrum.

Related: How to migrate from Vercel to self-hosted

Quick Comparison: All 10 Vercel Alternatives

The key difference: managed platforms charge per seat or per unit of usage, while self-hosted options charge only for infrastructure. Self-hosting moves the bill to a flat server price; a Hetzner CX23 (2 vCPU, 4 GB RAM, 20 TB of traffic) is €5.49/month excluding VAT (verified 2026-10-07).

1. Temps — Best All-in-One Self-Hosted Alternative

Temps is one self-hosted platform that replaces seven SaaS tools: Vercel (git-push deployments), PostHog (analytics and session replay), Sentry (error tracking), Pingdom (uptime monitoring), Datadog (OpenTelemetry traces, metrics and logs), Resend (transactional email) and E2B (AI agent sandboxes). It also runs managed databases. Temps is free to self-host under MIT / Apache 2.0; you pay only for the server, such as a Hetzner CX23 at €5.49/month excluding VAT.

Why Temps stands out

Every other alternative on this list handles deployment; none bundles the observability stack you'll eventually need. With them you still add Sentry Team ($26/month), Plausible ($9/month), a session replay tool such as LogRocket (from $176/month) and an uptime monitor (UptimeRobot Solo, about $10/month). Temps includes all of that.

The technical foundation matters too. Temps uses Pingora as its reverse proxy, the framework Cloudflare built to replace Nginx in its own network, which handles over a trillion requests a day.

The self-hosted version has no deployment caps, usage limits or seat restrictions. A Premium licence ($399/organisation/month) adds enterprise features such as SAML SSO and SCIM. See Temps vs Vercel for the full comparison.

Adding Temps analytics to a Next.js app

Temps ships @temps-sdk/react-analytics for Next.js. Add the provider to your root layout:

import { TempsAnalyticsProvider } from "@temps-sdk/react-analytics";

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return (
    <html>
      <body>
        <TempsAnalyticsProvider
          basePath="/api/_temps"
          enableSessionRecording={true}
        >
          {children}
        </TempsAnalyticsProvider>
      </body>
    </html>
  );
}

Track custom events with useTrackEvent:

"use client";
import { useTrackEvent } from "@temps-sdk/react-analytics";

export function SignupButton() {
  const trackEvent = useTrackEvent();
  return (
    <button onClick={() => trackEvent("signup_clicked", { plan: "free" })}>
      Get started
    </button>
  );
}

Pros

• One platform for deployment, analytics, error tracking, session replay and uptime monitoring
• Pingora reverse proxy with health-checked, zero-downtime deployments
• Multi-node clustering: worker nodes join over a private network you provide (temps join)
• Free to self-host (MIT / Apache 2.0); the only cost is the server
• No per-seat pricing, no bandwidth bills

Cons

• Smaller community than Coolify or Dokploy: Temps went public in October 2025, versus Dokku's 2013 debut. That gap is also why Temps ships a bundled observability stack the older, deployment-only tools were never built for.
• Fewer one-click templates than Coolify's 360+, because Temps focuses on deployment plus observability rather than a service catalogue.
• Enterprise features such as SAML SSO, SCIM and a tamper-evident audit log need the paid Premium licence, and Temps holds no SOC 2 or HIPAA certification.

Best for

Teams that want deployment and observability in one tool, especially startups that can't justify $200+/month in monitoring subscriptions.

To try Temps on your own server, follow the Temps quickstart (curl -fsSL https://temps.sh/deploy.sh | bash); Temps pricing explains what stays free and what Premium adds.

2. Coolify — Best Self-Hosted Template Catalogue

Coolify has the largest community of any self-hosted PaaS, with about 62,700 GitHub stars (October 2026) and 360+ one-click service templates. Dokploy (about 37,000 stars) is the other self-hosted name developers ask about: also deployment-focused, with an AI Docker Compose generator and basic CPU and memory monitoring, but no error tracking or session replay.

What you get

One-click installs for PostgreSQL, Redis, MinIO, Plausible and hundreds more services. Coolify wraps Docker Compose in a clean web dashboard with SSL, backups and multi-server support over SSH. Coolify Cloud starts at $5/month for two servers.

The trade-off: Coolify added opt-in traffic analytics in v4.4 (October 2026), but it has no error tracking, session replay or uptime checks. You add those yourself, either as more self-hosted services to maintain or as SaaS subscriptions.

Pros

• 360+ one-click services, one of the largest catalogues in self-hosted PaaS (Easypanel and Dokploy list more)
• Active community with frequent releases (v4.4.x in October 2026)
• Multi-server support via SSH
• Managed cloud option from $5/month

Cons

• No built-in error tracking, session replay or uptime checks
• v5 is in development with no release date, and Docker Swarm support is slated for removal in v5
• Running many one-click services on one server needs a larger server

Best for

Developers who want a wide template catalogue and don't mind assembling monitoring from separate tools.

3. Railway — Best Managed Alternative for Full-Stack Apps

Railway has no per-seat charge on any plan. Hobby is $5/month including $5 of usage; Pro, the plan a team needs, is $20/month per workspace with unlimited seats and $20 of usage included, per Railway's pricing page. There is also a Free plan with $1 of usage credit a month and a one-time $5 trial. For a team, Railway removes Vercel's per-seat multiplier and the variable becomes usage rather than headcount.

How Next.js runs on Railway

Push your code, Railway's builder detects Next.js, and it deploys a container with full SSR. You get custom domains, automatic SSL, and integrated PostgreSQL or Redis. The developer experience is close to Vercel's, without an edge network.

Where Railway gets expensive is always-on compute. A vCPU is about $20 a month and a GB of memory about $10, so a Next.js app using 1 vCPU and 1 GB around the clock costs about $30/month in compute; add a database and the bill reaches $40–60/month.

Pros

• No per-seat pricing on any plan
• Excellent developer experience with fast deploys
• Built-in PostgreSQL, MySQL, Redis and MongoDB
• Usage-based billing suits low-traffic apps

Cons

• Costs grow with production traffic (24/7 compute adds up)
• No built-in analytics or monitoring
• Egress billed at $0.05/GB
• No edge network

Best for

Solo developers and teams who want managed simplicity with usage-based billing and no seat fees. For worked bills, see Railway pricing 2026.

Head-to-head: Temps vs Railway.

4. Render — Best Free Tier for Getting Started

Render offers free web service instances for side projects, and paid instances from $7/month according to Render's pricing page. Its Pro workspace plan is $25/month plus compute, with unlimited seats. After Heroku ended its free tier in November 2022, Render absorbed a large share of that migration.

Next.js on Render

Render runs Next.js through Docker or native Node.js builds, with automatic SSL, custom domains and a straightforward dashboard. ISR and SSR work without custom configuration.

The catch: free web services spin down after 15 minutes without traffic, and the next request waits, up to about a minute, while the service starts again. Free Postgres databases expire after 30 days. For production you need paid instances, so a Next.js frontend plus an API backend plus a database adds up per service.

Pros

• Free instances for side projects
• Clean, simple dashboard
• Native PostgreSQL and Redis support
• Automatic HTTPS and custom domains

Cons

• Free services spin down when idle
• No built-in analytics or error tracking
• Free Postgres expires after 30 days
• Paid plans add up with multiple services

Best for

Solo developers and side projects that need a free starting point with an easy upgrade path.

Head-to-head: Temps vs Render.

5. Netlify — Best for Static-First Sites

Netlify's Free plan is 300 credits a month, roughly 15 GB of bandwidth or about 20 production deploys, according to Netlify's pricing page. Pro is $20/month per team with unlimited members and 3,000 credits. Synchronous functions time out after 60 seconds on every plan. Netlify was built for static-first architectures, and its CDN and Edge Functions are excellent for those sites; full Next.js SSR goes through its adapter.

The Next.js compatibility question

Netlify's Next.js support has improved a lot, but it isn't first-party: an adapter maps Next.js features onto Netlify's runtime. Most features work, including SSR, ISR, API routes and image optimization, but edge cases around middleware and advanced routing can cause friction in heavily dynamic apps.

Pros

• Excellent CDN for static assets
• Form handling and deploy previews built in
• No seat fees on Pro
• Large community and plugin ecosystem

Cons

• Next.js runs through an adapter, not natively
• Bandwidth is credit-metered at 20 credits per GB (about $0.13/GB in extra credits)
• No error tracking or session replay

Best for

Teams building static-first sites who don't need heavy server-side rendering.

Related: Netlify hidden costs and alternatives

Head-to-head: Temps vs Netlify.

6. Cloudflare — Best Edge Performance for Static Sites

Cloudflare serves static assets free and without limit on every plan. Pages' Free plan allows 500 builds a month with one build at a time (five concurrent builds on Cloudflare Pro), and Workers Paid at $5/month includes 10M dynamic requests. Cloudflare runs in 330+ cities, the largest edge network available to individual developers. The full list of limits is in Cloudflare Pages free tier limits.

How does Next.js run on Cloudflare?

Server-rendered Next.js on Cloudflare runs on Workers, not Pages. Cloudflare recommends vinext, a Vite plugin that reimplements the Next.js API surface, as the default; it is in beta. The OpenNext adapter (@opennextjs/cloudflare) remains supported for existing apps; it needs the nodejs_compat flag and doesn't support Node.js middleware yet. The older @cloudflare/next-on-pages adapter is deprecated. Both current paths run your app inside Workers' limits (10 ms of CPU per request on the free plan, 128 MB of memory on every plan), and new Next.js features can lag until the adapter catches up.

You don't need an adapter with Temps. Temps builds your app with your package manager's build script and runs it with next start as a Node.js process behind the Pingora proxy. There's no translation step and no adapter version to track. If your app is static or lightly dynamic and edge latency matters more than full Next.js compatibility, Cloudflare is a cheap, fast choice. For the alternatives that start from Cloudflare, see Cloudflare Pages alternatives.

Pros

• Free, unlimited static bandwidth on every plan
• 330+ edge locations
• Workers for server-side logic
• Generous free tier for static sites

Cons

• Server-rendered Next.js needs vinext (beta) or OpenNext on Workers
• Workers limits CPU time and memory per request
• 500 builds a month and one concurrent build on Free
• Platform services (KV, R2, D1, Durable Objects) are Cloudflare-specific

Best for

Static-heavy Next.js apps that prioritise global performance and want free bandwidth.

Head-to-head: Temps vs Cloudflare Pages.

7. Fly.io — Best for Multi-Region Containers

Fly.io runs Docker containers on its own hardware in 17 regions. There's no monthly platform fee: it's pay as you go, with the cheapest always-on machine (shared-cpu-1x, 256 MB) at about $2.19/month plus data transfer, according to Fly.io's pricing docs. New organisations get no free allowance, only a trial of $1 in credit that lasts up to 7 days.

Next.js on Fly.io

Fly.io runs Next.js as a Docker container with full SSR and multi-region deployment. fly launch detects Next.js and generates a Dockerfile.

The learning curve is steeper than Vercel or Railway: you manage containers, scaling and machine sizes. In return you can run your app in São Paulo, Tokyo and Amsterdam at once on pay-as-you-go pricing.

Pros

• Multi-region deployment at developer-friendly prices
• Per-second billing
• Full Docker support means full Node.js compatibility
• Managed Postgres available (from $38/month)

Cons

• Steeper learning curve than managed platforms
• No free allowance for new organisations
• Managed Postgres is a significant step up in cost from the app itself
• Networking complexity grows with multi-region setups

Best for

Teams that need multi-region deployments without enterprise pricing and are comfortable with containers.

Head-to-head: Temps vs Fly.io.

8. DigitalOcean App Platform — Best Simple Managed Hosting

DigitalOcean App Platform starts at $5/month for its smallest container (1 shared vCPU, 512 MiB RAM; $10/month for 1 GiB), according to DigitalOcean's pricing page, and hosts up to three static sites free. There's no per-seat pricing.

Next.js support

App Platform detects Next.js and deploys it via buildpacks. SSR works, custom domains are included, and managed databases are one click away. It is less flexible than Fly.io but much simpler to set up.

The limits show at scale: compute runs in one region, preview environments are limited, and monorepo setups are awkward. For a single Next.js app with moderate traffic, it's solid.

Pros

• Simple, predictable pricing with no per-seat charges
• Automatic Next.js detection and deploys
• Managed databases (PostgreSQL, MySQL, Redis) on the same platform
• Good documentation

Cons

• Single-region compute
• Limited preview environment support
• Insights metrics (CPU, memory, restarts, request rate, P95 latency; see DigitalOcean's docs); no error tracking or session replay
• Weak monorepo support

Best for

Small teams who want managed hosting without the complexity of AWS or Vercel's seat fees.

9. AWS Amplify — Best for Teams Already on AWS

AWS Amplify Hosting is pay per use: build minutes at $0.01 each, data transfer at $0.15/GB, CDN storage at $0.023/GB-month, and SSR at $0.30 per million requests plus $0.20 per GB-hour, according to AWS Amplify's pricing page. The free allowances (1,000 build minutes, 15 GB served, 5 GB stored and 500,000 SSR requests a month) come from the AWS Free Tier and last 12 months, not indefinitely; AWS also says new customers receive up to $200 in Free Tier credits instead. There are no seat fees; access is managed through AWS IAM.

Next.js on Amplify

Amplify supports Next.js with SSR, ISR, middleware and image optimization. Deployments trigger from Git pushes, and preview environments work out of the box.

The downside is AWS pricing complexity: build minutes, data transfer, request counts and storage all bill separately, and so does every other AWS service your app calls. The total is often lower than Vercel, but harder to predict.

Pros

• No per-seat pricing (IAM-based access)
• Native integration with Lambda, S3 and CloudFront
• Full Next.js SSR support, including ISR and middleware
• Preview environments for every pull request

Cons

• Complex pricing, hard to predict
• Dense AWS console
• Slower builds than Vercel's pipeline
• Debugging deployment failures needs AWS-specific knowledge

Best for

Teams with existing AWS infrastructure who want everything under one cloud provider.

10. Docker + VPS — Best for Maximum Control

A Hetzner CX23 (2 vCPU, 4 GB RAM, 20 TB of traffic) costs €5.49/month excluding VAT (verified 2026-10-07; Germany and Finland only), according to Hetzner's pricing page. Pair it with Docker, a reverse proxy like Caddy or Traefik, and a CI/CD script, and you have a fully self-managed Next.js deployment. No seat limits, no bandwidth charges, no vendor lock-in.

A small server can host several low-traffic Next.js projects behind Caddy. Setup takes an hour or two, but maintenance becomes the hidden cost: certificates, security patches, Docker updates and log management all fall on you.

What you need to set up

Docker, a reverse proxy (Caddy gives you automatic HTTPS most easily), a CI/CD pipeline (GitHub Actions works) and patience. There's no dashboard, no one-click deploys and no preview environments unless you build them.

The trade-off is total: complete control and the lowest cost, without any of the conveniences platforms provide.

Pros

• Cheapest possible option (server cost only)
• Complete control over the stack
• No vendor lock-in
• Unlimited projects and team access

Cons

• No dashboard, deploy previews or built-in CI/CD
• You maintain everything: TLS, updates, security, monitoring
• Setup takes a couple of hours at minimum (more for production-grade)
• No built-in analytics, error tracking or other observability

Best for

Experienced developers who enjoy infrastructure work and want the lowest cost with maximum control.

Related: How to deploy Next.js to a VPS manually

How Do These Alternatives Compare on Total Cost?

Total cost of ownership matters more than sticker price. Here's what a 5-developer team at about 100K monthly active users pays per month, with an observability stack of Plausible Starter ($9), Sentry Team ($26) and LogRocket (from $176), about $211/month, wherever the platform doesn't include it:

The observability stack is the hidden equaliser: for a small team it often costs more than the hosting. Without it, a self-hosted server beats every managed option on price; with it, only a platform that includes observability keeps the bill at the server cost. Cheaper replay options exist, so treat $211 as an entry-price example rather than a rule. For managed options without seat fees, see the cheapest Vercel Pro alternative.

What About Next.js Feature Compatibility?

Not every alternative supports every Next.js feature equally. Vercel builds Next.js, so it has first-party support for new features on day one. Next.js running as a Node.js server (next start) supports the full feature set, so any platform that runs it that way gets the same coverage.

Platforms that run Next.js as a Node.js server (Temps, Railway, Render, Fly.io, DIY) support the full feature set. Adapter-based platforms (Netlify, Cloudflare) map Next.js onto their runtimes, which can lag on newer features.

If you use basic SSR and API routes, every platform here works. If you push the edges of Next.js (Partial Prerendering, advanced middleware, streaming), test your specific features before committing.

Using @vercel/og Outside Vercel: Standalone Node.js

@vercel/og works in a standard Node.js API route; it doesn't require the Edge runtime. The package generates OG images with Satori and a WASM renderer. On every platform that runs standard Node.js (Temps, Railway, Render, Fly.io, DigitalOcean, Docker + VPS), it works as a regular API route.

Why developers hit this issue

@vercel/og was originally documented as Edge-only, and Vercel's examples include export const runtime = "edge". Deploy that file to a host without an Edge runtime and it can fail to build or error at runtime.

The fix is to leave out export const runtime = "edge":

// app/api/og/route.tsx — works on Temps, Railway, Render, Fly.io, Docker VPS
// Do NOT add: export const runtime = "edge"
import { ImageResponse } from "@vercel/og";

export async function GET(request: Request) {
  const { searchParams } = new URL(request.url);
  const title = searchParams.get("title") ?? "My Page";

  return new ImageResponse(
    (
      <div
        style={{
          display: "flex",
          fontSize: 60,
          background: "black",
          color: "white",
          width: "100%",
          height: "100%",
          alignItems: "center",
          justifyContent: "center",
        }}
      >
        {title}
      </div>
    ),
    { width: 1200, height: 630 }
  );
}

Without the runtime = "edge" directive, Next.js runs this route on the standard Node.js runtime. @vercel/og loads its WASM renderer in both environments; the API is identical.

Using @vercel/og as a standalone script (no Next.js)

To generate OG images at build time or from a Node.js script:

bun add @vercel/og

// generate-og.tsx — run with: bun generate-og.tsx
import { ImageResponse } from "@vercel/og";
import { writeFileSync } from "fs";

const response = new ImageResponse(
  <div style={{ fontSize: 48, background: "white", padding: 40 }}>
    Hello from Node.js — no Vercel, no Edge runtime
  </div>,
  { width: 1200, height: 630 }
);

const buffer = Buffer.from(await response.arrayBuffer());
writeFileSync("og-output.png", buffer);

No Vercel deployment, no Edge runtime.

Platform compatibility for @vercel/og

The rule: remove export const runtime = "edge" and @vercel/og works on every Node.js-capable platform. Cloudflare Workers needs extra configuration because it exposes only part of the Node.js API.

Which Alternative Should You Pick?

Choose Temps if...

You want deployment and observability in one tool, without separate Sentry, analytics and session replay subscriptions, and you're comfortable self-hosting (Temps is free; you need a server). It gives the lowest total cost when you count observability.

Choose Coolify if...

You want the widest template catalogue and community, you're comfortable with Docker, and you don't mind assembling monitoring from separate tools.

Choose Railway if...

You want managed hosting with no per-seat fees, your app needs databases alongside the frontend, and you prefer paying for what you use.

Choose Cloudflare if...

Your app is mostly static or uses light server-side logic, free bandwidth matters, and you want a global CDN without paying for it.

Choose Docker + VPS if...

You want maximum control and minimum cost, you enjoy infrastructure work, and you have time to maintain everything yourself.

Related: Deploy Next.js without Vercel

Frequently Asked Questions

What are the best alternatives to Vercel for Next.js hosting in 2026?

Temps, Coolify, Railway, Render, Netlify, Cloudflare, Fly.io, DigitalOcean App Platform, AWS Amplify and Docker on a VPS. For the lowest total cost, Temps is the strongest pick: it's self-hosted, runs Next.js on standard Node.js with no adapter, and bundles web analytics, session replay, error tracking and uptime monitoring, free under MIT / Apache 2.0 with no per-seat fees. Coolify and Dokploy are the other popular self-hosted names, but they focus on deployment, so monitoring is extra. For fully managed hosting, Railway and Render are the top usage-based picks. Netlify and Cloudflare suit static-heavy sites, but both run server-rendered Next.js through an adapter (Netlify's adapter, or vinext/OpenNext on Cloudflare Workers).

Which Vercel alternative can I self-host for production use?

Temps. It runs Next.js behind a Pingora reverse proxy with health-checked, zero-downtime deploys, and can add worker nodes over a private network you provide when one server isn't enough. Unlike Coolify, Dokploy, CapRover or Dokku, which focus on deployment, it bundles web analytics, session replay, a Sentry-compatible error-tracking DSN and uptime monitoring. It's free to self-host under MIT / Apache 2.0. Temps is newer (public since October 2025) than Dokku (2013) or Coolify, so its community and template catalogue are smaller, and SAML SSO and SCIM need the Premium licence. If you need a large catalogue of one-click templates, Coolify's 360+ win.

What's the cheapest Vercel alternative for Next.js?

Temps is the cheapest full-featured option: free to self-host, with git-push deploys, preview environments, analytics, error tracking, session replay and uptime monitoring included and no per-seat or usage fees. You pay for the server, for example a Hetzner CX23 at €5.49/month excluding VAT. For static sites, Cloudflare is free with unlimited static bandwidth. Docker on a bare server costs the same as Temps but leaves you to assemble monitoring yourself. The Next.js hosting cost breakdown has worked numbers.

Can I run Next.js SSR without Vercel?

Yes. Any platform that runs Node.js can serve Next.js SSR with next build and next start; if you build your own Docker image, standalone output mode (output: "standalone") makes it smaller. Every alternative on this list supports SSR. What doesn't move with you are Vercel's own services, such as @vercel/analytics, Vercel Blob and Vercel's edge network.

Is Netlify or Cloudflare better for Next.js?

Cloudflare offers free, unlimited static bandwidth and a larger edge network, which makes it better for traffic-heavy static sites. Netlify's Next.js adapter has a longer track record with server-rendered apps, while Cloudflare's recommended path, vinext, is still in beta. For purely static Next.js sites, Cloudflare wins on cost; for apps with significant server-side rendering, Netlify handles more edge cases. Neither matches running Next.js on a Node.js server.

How do I migrate from Vercel to a self-hosted platform?

Replace Vercel-specific services (such as @vercel/analytics or Vercel Blob), copy your environment variables, and connect the repository to your new platform's deploy pipeline. Most migrations take 15 minutes to 2 hours, depending on how tightly your code is coupled to Vercel. The migration guide covers managed and DIY paths, and the Temps migration docs cover the Temps steps.

Do self-hosted alternatives support preview environments?

Temps, Coolify and most managed platforms (Railway, Netlify, Cloudflare) support automatic preview environments for pull requests. With Docker on a VPS you build this yourself. Preview environments are one of Vercel's best features, but no longer exclusive to it.

The Bottom Line

Vercel is still excellent software, with unmatched zero-config Next.js deployment. But with $20 per deploying seat plus usage, it's not the only option, and for many teams not the most cost-effective one.

If you want managed simplicity without per-seat pricing, Railway, Render and Netlify are strong choices. If you want the fastest CDN with free static bandwidth, Cloudflare is hard to beat for static-heavy sites. If you want maximum control, Docker on a server gives you everything for the price of the server.

If you want deployment and observability in one tool, without adding $200+/month in SaaS subscriptions, that's where a self-hosted platform with built-in observability stands apart. Pick for your team's priorities: cost, control or convenience.

Related: Introducing Temps · Temps vs Vercel · Best deployment platforms for solo developers in 2026