Docs

Ways to deploy

Each way with a short video and a hello-world sample you can copy. All of them run in the Kingdom.

01Import a repository (GitHub App)

wadiup-hello-app ↗
  1. Settings → GitHub → Manage repositories on GitHub; pick the repository and save.
  2. New → Import a repository → Deploy.
  3. Name the project and press Apply. The wadiup.yaml (or render.yaml) in the repo says what to create.
Import a repository (GitHub App)

02Push to deploy

wadiup-hello-app ↗
  1. Commit to the deployed branch (main).
  2. GitHub tells Wadiup; the exact commit is built and released with no clicks.
  3. Deployments shows the new release as Live and the old one as Superseded.
Push to deploy

03Paste a blueprint

  1. Open a project and scroll to Blueprint.
  2. Paste a wadiup.yaml or an unchanged render.yaml, then Apply. Existing items are skipped.
services:
  - type: web
    name: hello
    image: nginxdemos/hello:plain-text
    port: 80
Paste a blueprint

04Public Git address

wadiup-hello-node ↗
  1. Project → Add new → Web service.
  2. Open “Or build from Git” and paste the public repository address. No Dockerfile needed: Node.js is detected.
Public Git address

05Private Git with a personal token

wadiup-hello-private ↗
  1. Create the service from the private repository address.
  2. On the service page, GitHub token for private repositories: paste a fine-grained token with Contents: read, Save, then Deploy now.

Test environments only. Production deploys require the GitHub App.

Private Git with a personal token

06Ready-made image

  1. Project → Add new → Web service.
  2. Enter the image (for example nginxdemos/hello) and its port, pick a plan, Create.
Ready-made image

07Image from a private registry

wadiup-hello-image ↗
  1. Create a web service from the private image (for example ghcr.io/<owner>/<image>:1) and its port.
  2. On the service page, Private registry credentials: user and a token with read access (GHCR: read:packages), Save, then Deploy now.
Image from a private registry

08Redeploy and roll back

wadiup-hello-app ↗
  1. Service → Redeploy builds the same branch again.
  2. Deployments → Roll back on any earlier release returns to that exact image.
Redeploy and roll back

09Access token for Claude and AI tools

  1. Settings → Security & access tokens → Read and deploy.
  2. The tool can list, deploy, roll back and apply blueprints through /v1/mcp; it can't delete, bill or manage members.
Access token for Claude and AI tools
  1. Project → Add new → Static site, from Git.
  2. An index.html is enough; nginx serves it with HTTPS.
Static site

11Background worker

wadiup-hello-worker ↗
  1. Project → Add new → Background worker, from Git.
  2. No port and no address: watch it under Logs.
Background worker
  1. Project → Add new → Cron job, from Git.
  2. Give a schedule in Riyadh time (for example */5 * * * *). Each run prints to Logs and exits.
Cron job

13PostgreSQL

  1. Project → Add new → PostgreSQL; pick version and plan.
  2. Link it to a service to give it DATABASE_URL. Backups run inside the Kingdom.
PostgreSQL

14MongoDB

  1. Project → Add new → MongoDB; high availability is optional.
  2. Link it to a service to give it its connection string.
MongoDB

15File storage (S3-compatible)

  1. Project → Add new → File storage; private by default.
  2. Link it to a service to give it the S3_* variables.
File storage (S3-compatible)

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.jsonnpm ci → npm run build (if present) → npm start. PORT is set for you.wadiup-hello-node ↗
Next.jspackage.json with nextBuilt and served with next start; choose a Web service.
Static sites (Vite, React, Astro, plain HTML)index.html or package.jsonChoose Static site; output from dist, build, out or public is served by nginx with SPA fallback.
Python (Django, Flask, FastAPI)requirements.txt or pyproject.tomlpip install; the Procfile web: line is the start command, else main.py, app.py, or gunicorn for Django.wadiup-hello-python ↗
Gogo.modgo build; the binary must listen on $PORT.wadiup-hello-go ↗
Java (Maven, Gradle, Spring Boot)pom.xml or build.gradleMaven or Gradle build; the jar is started with -Dserver.port=$PORT.wadiup-hello-java ↗
.NET*.csprojdotnet publish; ASPNETCORE_URLS set from $PORT.wadiup-hello-dotnet ↗
PHP (Laravel, WordPress)composer.json or index.phpApache with Composer install, listening on $PORT.wadiup-hello-php ↗
Ruby (Rack, Sinatra, Rails)Gemfilebundle install → bundle exec rackup on $PORT.wadiup-hello-ruby ↗

Moving from Render

  1. Create a project on a KSA data plane.
  2. Paste your render.yaml as a blueprint, or add each service from the same repo and branch.
  3. Create PostgreSQL, restore your pg_dump, link it (DATABASE_URL).
  4. Add your custom domain, verify the TXT record, switch DNS.

Moving from Vercel

  1. Next.js apps: Web service, build and start detected.
  2. Pure static exports: Static site, publish directory out.
  3. Serverless functions run inside the Next.js server.
  4. Connect the GitHub App for push to deploy.

Moving from Heroku

  1. Your Procfile web: line is used as-is.
  2. Worker dynos: Background worker with a start command.
  3. Scheduler jobs: Cron job (Riyadh time).
  4. heroku pg:backups → restore into managed PostgreSQL.