Before you start
- Your code is on GitHub. HudHud builds from a GitHub repository and branch. Private repositories need a GitHub token, added in the console when you create the app.
- The app listens on
$PORTand on0.0.0.0. Most apps already do this because the other platforms ask for the same thing. - Settings come from environment variables. Export them from your current platform (each section below shows how) and keep the file somewhere safe; it contains secrets.
- Plan a short write freeze for the database copy: stop writes (maintenance mode), dump, import, then switch DNS. For small apps this is a few minutes.
The quickest path is the HudHud CLI: npm i -g hudhud-cloud, then hudhud login. Everything below can also be done in Console → Apps.
DATABASE_URL, the same name these platforms use, so most code needs no change. If your code reads a different name (for example POSTGRES_URL), set that variable to the same value.From Heroku
| Heroku | HudHud Apps |
|---|---|
Procfile web: line | Read automatically as the start command (worker: for worker apps) |
| Buildpacks | Stack detection (Node, Python, PHP, Go) or your Dockerfile |
| Config vars | Environment variables |
| Heroku Postgres | PostgreSQL 16 add-on (DATABASE_URL) |
| Heroku Key-Value Store / Redis | Redis 7 add-on (REDIS_URL) |
| Release phase | Put migrations at the start of the start command |
heroku logs --tail | hudhud logs <app> -f |
heroku rollback | hudhud rollback <app> |
1. Export settings
heroku config -a my-heroku-app --shell > heroku.env # remove DATABASE_URL and REDIS_URL from heroku.env: HudHud sets its own
2. Create the app on HudHud
hudhud apps create shop --repo acme/shop --plan starter --db postgres --redis --no-wait hudhud env set shop $(grep -v -E '^(DATABASE_URL|REDIS_URL)=' heroku.env | tr '\n' ' ')
Values with spaces are easier to paste into the Environment tab in the console.
3. Copy the database
heroku maintenance:on -a my-heroku-app heroku pg:backups:capture -a my-heroku-app heroku pg:backups:download -a my-heroku-app # writes latest.dump hudhud db import shop latest.dump --confirm shop
latest.dump is in pg_dump's custom format, which HudHud restores directly (owners and grants are skipped). Imports up to 100 MB go through the CLI or the Database tab; for bigger databases, contact support and we will load it for you.
4. Deploy and check
hudhud deploy --app shop hudhud logs shop -f
Open https://shop.run.hudhudexpress.com, check the app, then switch your domain.
From Vercel
Next.js apps run on HudHud as a Node server (next build, then next start), not as serverless functions. In practice that means:
- API routes, server components, server actions and middleware all work as they do with
next start. - Vercel-only services such as Vercel Blob, Edge Config, Vercel KV and Vercel Cron need replacing: use HudHud object storage (S3-compatible) for files, the Redis add-on for key-value data, and a worker app or a scheduled job library for cron.
- Image optimisation (
next/image) runs inside your app. On small plans, considerimages: { unoptimized: true }or a bigger plan if you serve many large images. - A fully static Next.js export (
output: "export") or a plain React/Vue/Svelte site fits HudHud Sites better: cheaper, with a preview for every pull request.
Steps
vercel env pull .env.production --environment=production hudhud apps create web --repo acme/web --plan pro --no-wait hudhud env set web $(grep -v '^#' .env.production | grep -v '^VERCEL' | tr '\n' ' ') hudhud deploy --app web
If you used a hosted Postgres (Vercel Postgres, Neon, Supabase), copy it with pg_dump and import it as described for Railway below, or keep using it: outside databases work as long as your app can reach them.
From Railway
| Railway | HudHud Apps |
|---|---|
| Service from a GitHub repo | An app (web or worker) |
| Nixpacks / Railpack build | Stack detection, or your Dockerfile |
| Postgres / MySQL / Redis service | Database and Redis add-ons on the app |
Variables and references like ${{Postgres.DATABASE_URL}} | Environment variables; DATABASE_URL / REDIS_URL are set for you |
Steps
railway variables --kv > railway.env # in the linked project; remove database URLs pg_dump -Fc --no-owner --no-acl "$RAILWAY_DATABASE_PUBLIC_URL" -f railway.dump hudhud apps create api --repo acme/api --plan starter --db postgres --no-wait hudhud env set api $(grep -v -E '^(DATABASE_URL|REDIS_URL|RAILWAY_)' railway.env | tr '\n' ' ') hudhud db import api railway.dump --confirm api hudhud deploy --app api
For a MySQL service use mysqldump --single-transaction and import the .sql file the same way. Each Railway service from the same repository becomes its own HudHud app (for example one web and one worker).
From Render
| Render | HudHud Apps |
|---|---|
| Web Service | Web app |
| Background Worker | Worker app |
| Build command / Start command | Same fields in the app's Settings tab (Procfile is also read) |
| Render Postgres | PostgreSQL 16 add-on |
| Render Key Value | Redis 7 add-on |
| Free instances that spin down | Free plan: sleeps after 30 idle minutes, wakes on the next visit |
Steps
- In the Render dashboard, open the service → Environment and copy the variables (skip
DATABASE_URL). - Copy the database with its External Database URL:
pg_dump -Fc --no-owner --no-acl "$RENDER_EXTERNAL_URL" -f render.dump - Create the app with the same build and start commands:
hudhud apps create site --repo acme/site --db postgres --no-wait, then set them in Settings if detection doesn't match. hudhud db import site render.dump --confirm site, thenhudhud deploy --app site.
Switch your domain
- Lower the TTL of your domain's DNS record to a few minutes a day before.
- In the app's Domains tab, add your domain (for example
www.mybusiness.et). - Change the record to a
CNAMEpointing at<app>.run.hudhudexpress.com. For a bare domain without CNAME support, use theArecord shown in the tab. - Press Check DNS. HTTPS is issued automatically once the record resolves.
- Keep the old platform running (read-only) for a day in case you need to compare, then shut it down.
Domain managed in Cloudflare? Set the record to DNS only (grey cloud) until HTTPS is active, or connect Cloudflare in Console → Cloudflare DNS and edit it from there.
What is different today
- No pull-request preview environments for apps yet (static Sites have them).
- One instance per app; no autoscaling. Choose a bigger plan for more memory and CPU.
- No one-off command runner yet. Run migrations at start-up, or use the SQL editor in the Database tab.
- Persistent disk is not attached to the app container. Store uploads in object storage, not on the local filesystem.
Missing something you rely on? Tell us at support; it shapes what we build next.