Deployment

The steps

Build -> Package -> Publish -> Install -> (Upgrade)

Publish does all of them for you (Check, build and publish); the CLI does the same (erp plugin op, spark package).

Deployment modes

Mode	What runs where	Choose it for
Plugin (embedded)	artifacts and any code run inside the platform	most plugins
Service	the plugin's backend is its own container, registered at the gateway, sized and controlled from Studio	heavy or independent logic, independent scaling
Regional	one stack per region, each with the same PLUGIN_REGION; each region routes to its own copy	data residency, latency

Builds run in isolated, disposable environments; each service plugin runs on its own private network. Details: Backend services.

Configuration

Environment variables and secrets are set per service in Manage backend service (variables restart it). Secrets belong there or in connectors, never in plugin metadata. Database changes are made by entity definitions, which apply their own schema changes on install; there is no hand-written migration in a metadata plugin.

Planned (placeholders)

Blue/green and canary rollout, automatic promotion pipelines between environments, per-region rollout status in Studio. Planned. (Environment promotion and manual export/import exist.)

Verify

Header shows Installed; the service dialog shows Running; the route answers.

Troubleshooting

See Troubleshooting: install failures, "temporarily unavailable", missing library in the worker image.