For teams leaving Heroku
Switch from Heroku in 3 minutes.
Fieldwick gives you 1:1 PaaS parity with Heroku. Dynos map to Fieldwick services, your Heroku Postgres add-on is detected and mapped in the migration plan, and your Procfile is read directly. No rewrites, no Dockerfile changes - just one platform with a hard monthly spend cap replacing Heroku's per-dyno and per-add-on tiers.
$0 to try. Bring your project over when you are ready.
How it works
Three promises that make the migration feel safe.
Dyno-for-service mapping
Your web and worker dynos map 1:1 to Fieldwick web and worker service types. Procfile is parsed automatically - no Dockerfile needed unless you want one. Buildpack output works via Nixpacks (same upstream lineage). No rewrites, no Dockerfile changes required to move over.
Heroku Postgres in, Fieldwick Postgres out
Fieldwick detects your Heroku Postgres add-on and maps it to a Fieldwick managed Postgres in the migration plan. Your DATABASE_URL reference is preserved using the ${{Postgres.DATABASE_URL}} reference contract - the plan carries the correct reference across so nothing is hardcoded. You review and confirm before any data moves.
No surprise bills
Fieldwick gives your account one hard monthly spend cap. Heroku's per-dyno and per-add-on tier system added together can be hard to predict, especially after recent price-tier changes. Fieldwick rolls all usage into a single monthly ceiling for your whole account. You set the cap; we enforce it.
Ready when you are
Bring your project to Fieldwick.
The migration wizard is in your dashboard. We will not deploy until you approve the diff; we will not delete your Heroku app on the way out.
Open the migration wizard