Docs
Quickstarts by stack (no Dockerfile needed)
A Dockerfile in the repository always wins. Otherwise the platform detects the project type and builds it in-Kingdom.
| Node.js (Express, Nest) | package.json | npm ci → npm run build (if present) → npm start. PORT is set for you. |
| Next.js | package.json with next | Built and served with next start; choose a Web service. |
| Static sites (Vite, React, Astro, plain HTML) | index.html or package.json | Choose Static site; output from dist, build, out or public is served by nginx with SPA fallback. |
| Python (Django, Flask, FastAPI) | requirements.txt or pyproject.toml | pip install; the Procfile web: line is the start command, else gunicorn for Django. |
| Go | go.mod | go build; the binary must listen on $PORT. |
| Java (Spring Boot) | pom.xml or build.gradle | Maven or Gradle wrapper build; started with -Dserver.port=$PORT. |
| .NET | *.csproj | dotnet publish; ASPNETCORE_URLS set from $PORT. |
| PHP (Laravel, WordPress) | composer.json or index.php | Apache with Composer install, listening on $PORT. |
Moving from Render
- Create a project on a KSA data plane.
- Add each service from the same repo and branch; copy env vars.
- Create PostgreSQL, restore your pg_dump, link it (DATABASE_URL).
- Add your custom domain, verify the TXT record, switch DNS.
Moving from Vercel
- Next.js apps: Web service, build and start detected.
- Pure static exports: Static site, publish directory out.
- Serverless functions run inside the Next.js server.
- Enable push-to-deploy with the GitHub webhook.
Moving from Heroku
- Your Procfile web: line is used as-is.
- Worker dynos: Background worker with a start command.
- Scheduler jobs: Cron job (Riyadh time).
- heroku pg:backups → restore into managed PostgreSQL.