Quick start

DeployON lets you provision apps, connect Git, build with Railpack/Nixpacks, and deploy to Kubernetes with HTTPS.

This guide covers three ways to get started:

  1. Deploy from GitHub/GitLab (portal)
  2. Deploy with the CLI
  3. Deploy from a Docker image / Dockerfile

Portal: https://console.deployon.pro/portal

Deploying your project — from Git

  1. Open the Portal → Projects → + New.
  2. Connect GitHub or GitLab (OAuth), or paste a repository URL.
  3. Choose the branch to build (usually main).
  4. Optionally enable deploy on push so every commit triggers a new build.
  5. Review build/start commands (auto-detected) or set them manually.
  6. Click Deploy.

When the deployment status becomes healthy, open the public URL from Domains (platform subdomain on *.apps.deployon.pro).

If the build fails, open Logs and scroll the full build output — the real error is often not on the last line.

Deploying your project — with the CLI

Node.js 20+ required. Install @deployon/cli.

npm install -g @deployon/cli
deployon --version
deployon login
deployon project ls
deployon project select
deployon deployment ls
deployon deployment select
deployon deploy --push --wait

In this CLI, a deployment is an application (platform Service). Link a local repo, then deploy:

cd /path/to/my-app
deployon init --connect --create
deployon deploy --push --wait
deployon logs --follow

Without Git:

deployon deploy --local --wait

Tarball limit: 100MB. Excluded: .git, node_modules, .next, dist, build.

Full command reference: CLI docs.

Deploying from a Dockerfile

  1. Create a project in the portal.
  2. In service configuration, set the Dockerfile path (or use auto-detection when a Dockerfile exists).
  3. Set the start command and port if needed.
  4. Deploy.

You can also point to a pre-built image from a registry when that option is configured on the service.

After the first deploy

You land on the project/service overview — your control plane for:

  • Deployments history and rollback
  • Live logs
  • Environment variables
  • Domains and TLS
  • Metrics (CPU / RAM / network)

Generate or copy the platform domain, or add a custom domain under Domains.

Optional next steps

  1. Provision a managed database (PostgreSQL / MySQL / Redis / MongoDB).
  2. Inject the connection string as an environment variable (e.g. DATABASE_URL).
  3. Redeploy.
  4. Attach a custom domain and verify DNS.
  5. Allocate CPU/RAM/storage on Usage.

What to explore next