Settings & Configuration

Settings exist at three scopes. More specific scope wins.

Workspace settings

• Profile: name, slug, logo
• Members & invitations: see Team Management
• Billing: plan, credits, invoices (see Billing & Usage)
• Notifications: in-app preferences; transactional email is always on for security events

Project settings

• General: name, slug, visibility of members
• Environments: create custom branch environments; production and preview are built-in kinds
• Shared variables: project-wide values referenced by services
• Danger zone: delete project (disable → 14-day undo → purge)

Service settings

Organized by concern:

Source

Git connection (repo + deploy branch) or image reference. Changing the source affects the next build only — running deployments keep serving their frozen release until you redeploy.

Build

Commands, working directory, output handling. Per-service, shared across all its environments.

Deploy

• Deploy branch per environment
• Auto-deploy on push (per environment)
• Rollback: repoint the alias to any retained historical deployment — instant, no rebuild

Networking

• Ports: which container port the platform endpoint exposes over HTTP
• Public TCP: opt-in exposure for non-HTTP protocols (binds once on the endpoint)
• Health checks: HTTP/TCP probes that decide replica readiness

Variables

Instance variables and references — see Variables & Configuration.

Where changes take effect

The pattern to remember: anything frozen into a deployment (artifact, runtime spec, env snapshot) needs a new deploy; anything held as intent (placement, aliases, domains) applies through reconciliation without one.