Migrate Remix from Heroku to EasyHost

Move your Remix app in four steps, and keep Heroku running until the new deployment works.

Last updated November 9, 2026

Export your variables

heroku config -s > .env

Then import them into EasyHost.

npx ezhst env import .env

Change the Remix setup

Replace platform packages such as @vercel/remix with @remix-run/node, and start with remix-serve.

Procfile is not read by EasyHost, so its build and routing rules need moving into your app or into build settings.

Use the default @remix-run/serve server. It reads PORT and HOST.

Deploy and test

npx ezhst projects create my-project --link
npx ezhst apps create my-app
npx ezhst link --project <project-slug> --app <app-slug>
npx ezhst env import .env
npx ezhst deploy

Test your easyhost.fun URL before changing DNS. Heroku runs your app on dynos, so check anything that depends on it, such as platform functions or cron configuration. Schedules move to EasyHost schedules.

Switch your domain

npx ezhst domains add www.example.com
npx ezhst domains list
npx ezhst domains verify www.example.com

Follow the custom domain guides for your DNS provider. Keep Heroku running until traffic has moved. Also read why Remix may be unreachable and the Heroku overview.

Start for free

Install the skill, choose Global or Local, then tell your agent to deploy. No credit card, no config files.

npx ezhst skill install