Deployments

A deployment is a running instance of a service. You can deploy, redeploy, stop, list historical deployments, and stream live logs.

The deploy command can be shortened to d:

edge d up api

All deployment commands require a workspace, project, and environment.

up

Deploy a service. If the service has never been deployed, a new deployment is created. If it has been deployed before, the same command re-deploys it.

edge deploy up <svc-slug>

If the service has pending changeset changes (staged image, resource, or variable updates), the command prints a summary of those changes before proceeding:

• Interactive — prompts Deploy with these changes? [y/N]. Answering y deploys; anything else cancels.
• --yes / -y — skips the prompt and deploys immediately. Useful in CI/CD pipelines.
• Non-interactive without --yes — exits with an error so the pipeline fails visibly rather than silently skipping staged changes.

If there are no pending changes, the command deploys straight away without any prompt.

Deployment strategy

For Docker services, deployment behaviour depends on whether a readiness check is configured:

Simplifyd Cloud does not create a default readiness check. Configure one under Health Probes before deploying if the service requires a rolling update. See Healthchecks.

This behaviour is the same for a plain redeploy and a deployment that applies pending changes.

Flags

Examples

# Interactive deploy — prompts if there are pending changes
edge deploy up api

# Auto-approve pending changes and deploy (CI-friendly)
edge deploy up api --yes
edge deploy up api -y

Example output (pending changeset)

Pending changes for service api:

TYPE          ACTION  NAME          FROM               TO
docker_image  update  docker_image  my-org/api:v2.1.0  my-org/api:v3.0.0
memory        update  memory        512                1024

Deploy with these changes? [y/N]: y
✓ Deployment started: dep-01j2k3... (status: pending)

Example output (no pending changes)

✓ Deployment started: dep-01j2k3... (status: pending)

JSON output

edge deploy up api --json

{
  "id": "dep-01j2k3...",
  "slug": "dep-01j2k3...",
  "status": "pending",
  "service_id": "svc-01j2k3...",
  "created_at": "2025-06-01T12:00:00Z",
  "updated_at": "2025-06-01T12:00:00Z"
}

down

Stop a running service (undeploy).

edge deploy down <svc-slug>

edge deploy down api

The service's resources are freed but its configuration is preserved. Run edge deploy up to start it again.

list

List all deployments for a service, ordered from newest to oldest.

edge deploy list <svc-slug>
edge deploy list api --json

Example output

SLUG              STATUS     CREATED AT
dep-01j2k3...     running    2025-06-01T12:00:00Z
dep-01j2k2...     stopped    2025-05-28T09:15:00Z
dep-01j2k1...     failed     2025-05-20T17:30:00Z

logs

Stream live logs from a deployment.

edge deploy logs <svc-slug>
edge deploy logs <svc-slug> --deployment <dep-slug>

By default, logs are streamed from the latest deployment. Pass --deployment to target a specific one.

Press Ctrl+C to stop streaming.

Flags

Example

# Stream latest deployment logs
edge deploy logs api

# Stream a specific deployment
edge deploy logs api --deployment dep-01j2k3...

→ Streaming logs for deployment dep-01j2k3...
2025-06-01T12:00:05Z Starting server on :8080
2025-06-01T12:00:05Z Connected to database
2025-06-01T12:00:06Z Listening for requests