Heroku exit · £995 after sign-off
Move your small Heroku app to Render, with its database.
We move one eligible Rails or Node web app and its Heroku Postgres database to a Render account you own. The result is a working production app, not a recipe for you to follow.
Tell us the app language, database size, add-ons and who controls the accounts and code. No passwords, code, database records or invites in your first email.
Scope and limits
One bounded move, to Render only.
Included: one existing Rails or Node web app, one Heroku Postgres database and up to two portable, non-data add-ons (such as an independently held email or error-reporting service that can continue on Render). We inventory settings, prepare the Render build and a separate test deployment, back up and move the database during an agreed pause to writes, compare agreed table counts, test key flows, support DNS cutover and hand over the check record and instructions. A second reviewer checks the plan and changes. Heroku stays available until sign-off.
Not included: Salesforce Connect/Data Bridge, Private Spaces, Shield or regulated/compliance workloads; multiple apps or databases, large or continuously written databases, Redis/queues, workers, schedulers or background runners (including those inside a web dyno), dyno-tied storage, custom networking, complex add-on replacements, major Rails/Node upgrades or new features. We check eligibility first; if your app does not fit, we say so without charging for this package.
We only offer Render at this price, not Fly.io, a self-managed server or Kamal. Render's migration guide describes web services, Postgres and DNS, including brief downtime at cutover. We have not yet completed a production migration off Heroku or an end-to-end rehearsal of this package. This is a proposed route, not a past result. A qualifying rehearsal must pass before we accept a job.
How we work
You keep the accounts and approve the switch.
Agree eligibility and handoff.
We inventory your app, database, add-ons and who holds the source, Heroku, Render and DNS. You keep ownership of the hosting accounts and domain. We do not have a company GitHub identity for client repositories outside our organisation, so we cannot promise a repo invite or pull request. We agree a client-approved secure archive or patch exchange before accepting work; without a safe handoff, we do not take the job.
Test without sharing passwords.
Your authorised account holder creates the Render account, enters secrets privately, runs the Heroku database export and grants only documented temporary access if needed. Before any production cutover, we check the actual build, database connection and agreed key flows in your own staging environment. We never request passwords. We do not accept a job until a safe handoff and client-held steps are workable; if they are not, the fixed-price job cannot go ahead.
Pause, move and check.
We agree the backup, pause to writes, table-count checks, key flows, DNS switch and last safe point to turn back before new writes begin. Your account holder approves cutover. We check the live app with you, hand over what was checked and you remove any temporary access after sign-off and payment.
Before you decide
The risks and the choice to stay.
Is Heroku shutting down?
No shutdown date has been announced. Heroku says it is in sustaining engineering: existing apps and card-paying customers remain supported, but it plans no new features. Staying on Heroku is a valid choice. Our free Heroku-22 owner guide explains the separate stack deadline.
Can you guarantee no downtime or data loss?
No. Backups and cutover need a maintenance window; we cannot promise zero downtime or certify every record or integration from table counts. After the new database accepts writes, returning to Heroku needs another data move, not a one-click rollback. We agree the risk and reversal point before touching production.
Can my email service stay?
Possibly, if your own account and credentials work outside Heroku. We will not silently replace a data-holding add-on.
Start with an email, not access.
Tell us your app language, any Heroku-22 notice, database size, add-ons and who holds the accounts and source. Send no credentials.