Migrate from Render

Render bills by the service.
Varity bills by the app.

One fixed monthly price per app, based on the hardware reserved. Postgres, Redis, and Mongo auto-wired as separate reserved Managed Cloud deployments, each with its own preset price shown before you deploy.

Get a migration estimateSee Varity pricing

Your bill today. Your bill on Varity.

A single production web service with Postgres. Two very different billing structures.

Your Render bill today

  • +Workspace fee
  • +Per-service Web Service compute
  • +Managed Postgres billed separately
  • +Bandwidth above included GB
  • +Build pipeline minutes above included
  • +Persistent disk metered per GB

Result

Unpredictable

More services, more meters, more line items.

Your Varity bill

One priceshown before you deploy
  • All-in. No workspace fee.
  • No per-service compute.
  • Postgres attaches as a managed service.
  • No bandwidth meter.
  • No build-minute meter.

Result

Predictable.

Side by side, line by line.

Structural differences, side by side. For current Render dollar figures, see the official source below.

Feature
Render
Varity
Pricing model
Workspace subscription plus per-service compute, bandwidth, and build pipeline minutes[1]
One fixed monthly price for the resources you reserve, shown before you deploy
Workspace base subscription
Paid workspace tiers layered on top of per-service compute[1]
No separate workspace fee on top of the app price
Web service compute
Fixed instance tiers per service, with usage meters layered on top[1]
Fixed resource presets, with no usage metering layered on top
Bandwidth
Included allotment per plan, then metered per GB[1]
No ingress or egress fees. No bandwidth meter, no overage
Build pipeline
Included minutes per plan, then metered per 1,000 minutes[1]
No build-minute meter
Managed Postgres
Separate paid tiers, billed per database[1]
Postgres + pgvector attaches as a managed service, with its own preset price shown before you deploy
Auto-sleep on Free tier
Yes. Free instance type sleeps after inactivity[1]
Reserved resources do not sleep. Free static tier: 3 active sites, 1 GB pinned assets, verified account, no card required
Vendor lock-in
Render-specific config and dashboard wiring
Open-source varitykit CLI, standard containers
Migration path
Self-serve
Redeploy your services on Varity, same stack, same env vars. Scripted Render migration coming soon.
Stacks supported
Node, Python, Ruby, Go, Rust, Elixir, PHP, plus Docker
Node (Next.js, React, Vue, Astro, Qwik, Vite, Express, Fastify, Nest, Koa, Hono), Python (FastAPI, Django, Flask), static HTML
Bill when traffic spikes
Instance upgrades plus bandwidth and build meters scale the bill with traffic.[1]
For an unchanged resource profile, the price doesn't move with traffic.

A governed numeric cost comparison with matched assumptions and dated evidence is coming. Until then, see current Render pricing at the official source and Varity pricing at varity.so/pricing.

Sources

  1. [1]Current Render pricing: render.com/pricing
Redeploy on Varity

Same Dockerfile. Same env vars. Same stack.

Varity does not have a one-command Render migrator yet. The path is a clean redeploy.

terminal
$ pipx install varitykit
$ cd your-render-app
$ varitykit app deploy
✓ Detected Dockerfile
✓ Loaded env vars from .env
✓ Auto-wired Postgres + Redis sidecars

Live at varity.app/your-app

Your repo

Same Dockerfile. Same start command.

Your databases

pg_dump to a Varity Postgres service (its own reserved deployment with its own preset price).

Your env vars

Copy from Render dashboard. No code changes.

Common migration questions

The five things builders ask before they migrate.

How long does migration take?+

Most apps move in under an hour. Varity does not have a one-command Render migrator yet (the varitykit migrate command is Vercel-specific today). The path is: redeploy your repo on Varity, same Dockerfile, same env vars, same stack. A scripted Render migration is on the roadmap.

What if I need to roll back?+

Keep your Render services running until your varity.app URL is verified end-to-end. Migration does not touch your Render deployment. Point your DNS over only after you have confirmed the Varity URL works. Rollback is a DNS change away.

Will my Render Postgres data migrate?+

Yes, via a standard pg_dump from your Render Postgres into your Varity Postgres service. Same Postgres on both sides, so schema and data move cleanly. Varity attaches Postgres (with pgvector), Redis, MongoDB, and MySQL as managed services in the same cloud, each with its own preset price shown before you deploy.

What happens at 10x traffic?+

For an unchanged resource profile, your Varity price doesn't move with traffic. Render meters compute on every Web Service, bandwidth above included GB, and build pipeline minutes above included minutes. Three growth axes mean three ways traffic growth becomes bill growth. On Varity, those meters do not exist.

What about Render background workers and cron jobs?+

Honest gap: Varity does not yet offer Background Workers or Cron Jobs as first-class primitives. If your app already runs a worker process inside its container, you can deploy that container on Varity. A dedicated worker service type and managed cron are on the roadmap. Worker-heavy apps should wait.

Stop paying per service.

One app. One fixed monthly price per reserved deployment, prorated by running time.

Get a migration estimateSee Varity pricing