Using the CLI

Deploying a service from a local folder

Create or update an always-on service without a Git connection.

Run deplomo deploy in the project root; no flags are required. If no target service is selected, the CLI creates one automatically using the folder name as its name and Default as its project, and asks for confirmation once in the terminal. Pass --yes or -y to skip confirmation, for example in CI.

Override defaults with --name <name> for the service name, --project <slug|id> for its project, --private for private access, --port N for the internal port, --framework <name> as a stack detection hint and repeatable --env K=V. Available resources follow the account’s fixed monthly package for its zone (EU, US or Asia). Package purchases and renewals use your EUR wallet balance; resources are not charged by the hour.

After the first deployment, .deplomo/service.json is saved in the project with the service ID. Subsequent deplomo deploy runs in that folder update the same service. To target a specific service explicitly, use deplomo deploy --service <slug-or-id>.

The CLI waits for a final state and prints build and deployment stages. If the status becomes running, it shows the service URL; if it becomes failed, it returns the recorded error.

Check before deployment


deplomo check            # Check for common first-deploy issues without uploading
deplomo deploy           # Runs the same checks before uploading

If the project root contains deplomo.json, its name, port, start command and other settings are used. See the command reference for details.

Managing services and Docker images

Create a service from a Docker image or deploy source to an always-on service.

List services with deplomo services or deplomo service list, and projects with deplomo projects. Available resources follow the account’s fixed monthly package for its zone (EU, US or Asia). Package purchases and renewals use the EUR wallet balance; there is no hourly resource billing.

If you have an image ready, deplomo service create --name <name> --image <image> creates the service. Use --private to avoid public exposure, --expose tcp for a raw TCP port for databases, and --port for the application’s internal port.

To turn a local folder into an always-on service, run deplomo service deploy --name <name>. Source is uploaded, built on the runtime and run as a service. Redeploy to the existing service with deplomo service deploy --service <slug-or-id>.

For builds and releases, use deplomo service builds <slug> and deplomo service releases <slug>. To see why a release failed, run deplomo service releases <slug> logs. To return to an earlier build without rebuilding it, run deplomo service rollback <slug> <build-id>. Use deplomo service domains <slug> for custom domains and deplomo service vars <slug> for build-time or secret variables.

Managing projects and environments

Create and manage projects (workspaces) and their environments from the command line.

A project groups a product’s services, environments and domains. List projects with deplomo projects, and inspect one with deplomo project get <slug|id>. Use deplomo project create --name <n>, deplomo project update <slug|id> and deplomo project delete <slug|id> to create, edit and delete projects.

Each project can have multiple environments: production, staging and preview. Manage them through deplomo project env <project> with list, create, get, update and delete. Identify an environment by name or ID; for example, deplomo project env my-app create --type staging --branch develop.

Manage environment variables with deplomo project env <project> vars <env>. With no additional argument it lists values; set KEY=VALUE adds or edits a value, with --build-time for build-time injection; rm KEY removes it.

List and read commands (projects, project get, env list/get/vars) accept --json to print the raw API response, which is useful for scripts and CI.

Environment variables, logs and status

Inspect service status and change settings without opening the dashboard.

All deplomo service subcommands take a service slug or ID as a positional argument. For example, deplomo service env <slug> shows variables, deplomo service env <slug> set KEY=VALUE adds or edits a value, and deplomo service env <slug> rm KEY removes it. The service is recreated to apply changes.

The same operations are available under service: deplomo service env <slug> [set KEY=VALUE | rm KEY] is equivalent to the shorthand. Alongside it, deplomo service vars <slug> is a separate typed variable store supporting --build-time for build-time injection and --secret for masked values. Both the simple env map and typed vars store are available.

deplomo logs <slug> --tail N shows the latest container log lines, defaulting to 200. Filter with --since, --grep and --level. deplomo service status <slug> prints status, URL and, when running, CPU and memory usage. deplomo service open <slug> opens the service URL in your browser.

Control lifecycle with deplomo service stop <slug>, deplomo service start <slug> for a stopped service, and deplomo service restart <slug> for an in-place restart. Manual stopping uses stopped status and differs from suspension due to insufficient balance. Use deplomo service delete <slug> for complete deletion.

Practical examples

Deploying from a local folder

The first deploy creates a new service and links the project. Subsequent deplomo deploy runs in the same folder update that service.


deplomo login
deplomo deploy            # Create and deploy; --yes skips confirmation
deplomo service status my-app
deplomo logs my-app --tail 200

Environment variables and CI

In CI, keep your token as a secret and pass it through DEPLOMO_TOKEN to avoid interactive login. The --yes flag skips confirmation when creating a new service.


deplomo service env my-app set NODE_ENV=production API_URL=https://api.example.com
deplomo deploy
 
# CI example
DEPLOMO_TOKEN="$DEPLOMO_TOKEN" deplomo deploy --service my-app --yes

Docker image services

Services run continuously, with available resources determined by the account’s fixed monthly package for its zone (EU, US or Asia). Package purchases and renewals use the EUR wallet balance. Use a prepared image or turn a local folder into a service with deplomo service deploy.


deplomo service create --name redis-cache --image redis:7 --private
deplomo service status redis-cache
deplomo service logs redis-cache --tail 100

Builds, releases and rollback

Each successful deployment records a new build and release. rollback runs the previous build without rebuilding and creates a new active release.


deplomo service builds my-app
deplomo service releases my-app
deplomo service rollback my-app <build-id>

Managing projects and environments

A project is a workspace for services. Each project can have several environments, each with its own variables. --json prints raw API output for scripting.


deplomo project create --name shop --description "Online store"
deplomo project env shop create --type staging --branch develop
deplomo project env shop vars staging set DATABASE_URL=postgres://… --build-time
deplomo projects --json

Variables, domains and the typed store

service vars is the typed variable store with --secret and --build-time support. service domains add shows the required DNS records, and verify verifies domain ownership after you create the TXT record.


deplomo service vars my-app set STRIPE_KEY=sk_live_… --secret
deplomo service domains my-app add app.example.com
deplomo service domains my-app verify app.example.com