Render bills you per service and per instance, so a web service, a background worker, a cron job, and a Postgres database quickly become four separate line items. Miget works differently: you buy one fixed-price resource plan and run unlimited services inside it. They share CPU fairly through the Fair Scheduler, so consolidating everything you run on Render onto a single Miget plan is the core win of migrating.

​
What maps to Miget

On RenderOn Miget
Web ServiceApp (public, traffic routed to PORT)
Background WorkerApp kept private (no public port)
Cron JobCron job
Render PostgresMiget managed PostgreSQL
Render Key Value / RedisMiget Valkey
Env GroupEnvironment variables (secrets)
Static SiteApp
There is no render.yaml importer. You recreate your services on Miget, either as individual apps or as a single Compose Stack built from one compose.yaml.

​
The PORT question

On Render, web services bind to $PORT. On Miget, PORT is set to an immutable 5000, and Miget routes public traffic there automatically. As long as your app reads the PORT environment variable (which Render apps already do), no code change is needed.

​
Migration steps

1

Recreate your services on Miget

List each service you run on Render - web service, worker, cron job, database - and recreate them on your Miget plan. Web-facing services become public apps; background workers become apps with no public port so they stay private. Prefer one file? Describe the whole set in a single Compose Stack.
2

Push your code

Connect your repository and push to the builder. Miget auto-detects your language from marker files (like package.json, requirements.txt, or go.mod), or you can bring your own Dockerfile for full control over the build.
3

Move your data

Provision Miget PostgreSQL and restore your Render database with pg_dump / pg_restore. Miget injects DATABASE_URL automatically. If you used Render Key Value, provision Valkey - Miget injects REDIS_URL.
4

Set environment variables

Recreate your Render Env Group values as Miget secrets. DATABASE_URL and REDIS_URL are injected for you, so you only carry over your own configuration.
5

Point your domain

Add your custom domain and let Miget provision TLS automatically. Once traffic looks healthy, cut DNS over from Render.
Migrate a copy first: run your Miget apps against a restored database and verify behavior before you move DNS. Nothing on Render changes until you flip the domain.

​
Next steps

Git push to builder

Connect your repo and deploy on every push.

Compose Stacks

Recreate multi-service setups from one compose.yaml.

Managed PostgreSQL

Provision a database with DATABASE_URL injected.

Valkey

Redis-compatible cache with REDIS_URL injected.

Secrets

Move your Env Group values across.

Custom domains

Add a domain with automatic TLS.

Fair Scheduler

How unlimited services share CPU fairly.

Resource plans

One fixed price for everything you run.