Running deployments
Weik.io 2026.2Deploy a published integration with the weikio CLI and change its deployment by hand. Video
Watch: Your first integration, 3:15
The video creates sandbox/hello with weikio init and publishes it with weikio apply. Then it deploys the integration to devtest and follows its log lines.
This part of the video couldn't be loaded.
When you deploy an integration to an environment, one of its versions runs there. Every agent that matches the deployment runs that version. Where an integration runs explains which agents match a deployment.
If you keep your deployments in Git, your pipeline deploys them. A change you make by hand lasts until the next apply puts back what the repository describes. When you can’t wait for the pipeline, for example to stop a failing integration, use the commands on this page. Then make the same change in the repository.
Deploy a version#
Use weikio deploy to run a published version of an integration in an environment. If you leave out --version, the deployment follows latest. It runs the newest stable version and moves to each new one you publish.
$ weikio deploy finance/erp-invoice-exportTarget: https://hub.example, project finance (argument), environment devtest (context)
Deploying finance/erp-invoice-export 1.1.0 (latest) to devtest...
deployment devtest/finance/erp-invoice-export updated (version 1.0.0 -> latest)
Agents: 1 of 1 running after 3.0 sIn a terminal, weikio deploy returns when every online agent runs the deployment. If the deployment fails to start on an agent, the command exits with an error. To see why, run the weikio status command in the error message. In a pipeline, the command returns as soon as the deployment is written.
The deployments reference lists every flag of weikio deploy. These are the flags that change what a deploy does:
| Flag | What it does |
|---|---|
-- |
Runs that version and stays on it |
-- |
Writes the deployment without starting it |
--set erp- |
Sets a variable for this deployment only and overrides every other value of that name |
-f ./ |
Deploys every integration in the folder |
-- |
Deploys even when no online agent matches yet |
The CLI never selects a production environment from your context. To deploy there you need --env production, or WEIKIO_ENV in a pipeline. You also need --version unless the environment allows latest. Environments and promotion shows how weikio promote copies the version that ran in devtest into production.
In production, every command on this page that changes a deployment shows a confirmation prompt first. In a pipeline, confirm with -y.
If a version uses a secret that has no value in the environment, deploying it fails with an error. Starting or restarting the deployment fails for the same reason. To set the secret, run the weikio secret set command in the error message.
Check where it runs#
To see where an integration runs, use weikio status. For each environment, it shows the integration’s deployment and the agents that run it:
$ weikio status finance/erp-invoice-exportENVIRONMENT VERSION STATE AGENT SINCE DETAIL
devtest 1.1.0 (latest) running dev 2026-11-17 14:45 UTC -
production 1.1.0 running dev 2026-11-17 14:49 UTC -
Last hour in devtest: 51 messages, 0 failed (0 %), memory 110 MB.
Last hour in production: 45 messages, 0 failed (0 %), memory 107 MB.When a deployment isn’t running on an agent, the DETAIL column shows the reason. One reason is an agent that hasn’t reported since the deploy. Add --watch to refresh the view every two seconds until you stop it.
You can list every deployment in one environment with weikio get deployments:
$ weikio get deployments --env productionPROJECT INTEGRATION VERSION DESIRED ACTUAL AGENTS SINCE
finance erp-invoice-export 1.1.0 started running 1/1 running 2026-11-17 14:49 UTCThe AGENTS column shows how many of the agents that match the deployment are running it.
To see one deployment in full, run weikio describe deployment finance/erp-invoice-export --env production. The output includes who deployed it and the process that runs it on each agent. For each deployment you can see, weikio get fleet prints a line for every agent that runs it.
In the admin UI, Home lists the integrations and APIs deployed in an environment. It also shows who deployed each one and when.




Stop and start#
Pause an integration with weikio stop when, for example, a system it calls is down. The command stops the integration on every agent but keeps its deployment:
$ weikio stop finance/erp-invoice-export --env productionTarget: https://hub.example, project finance (argument), environment production (--env)
This will stop 'finance/erp-invoice-export' in production environment 'production'.
Continue? [y/N] y
deployment production/finance/erp-invoice-export stopped (version 1.1.0)To run the same version again, use weikio start:
$ weikio start finance/erp-invoice-export --env productionTarget: https://hub.example, project finance (argument), environment production (--env)
This will start 'finance/erp-invoice-export' in production environment 'production'.
Continue? [y/N] y
deployment production/finance/erp-invoice-export started (version 1.1.0)Restart#
A running deployment picks up a changed variable or secret at its next start. If you need the changed values now, run weikio restart. It stops and starts the deployment on every agent:
$ weikio restart finance/erp-invoice-export --env productionTarget: https://hub.example, project finance (argument), environment production (--env)
This will restart 'finance/erp-invoice-export' in production environment 'production'.
Continue? [y/N] y
deployment production/finance/erp-invoice-export restarted (version 1.1.0)When you change a value with weikio apply or weikio secret set, the command lists the deployments that use it. With --restart, weikio secret set also restarts them.
Roll back#
When a new version misbehaves, roll back with weikio rollback. It moves the deployment back to the version it ran before:
$ weikio rollback finance/erp-invoice-export --env productionTarget: https://hub.example, project finance (argument), environment production (--env)
This will roll 'finance/erp-invoice-export' back to 1.0.0 in production environment 'production'.
Continue? [y/N] y
deployment production/finance/erp-invoice-export updated (version 1.1.0 -> 1.0.0, previous 1.1.0)
Agents: 1 of 1 running after 3.0 sThe version you rolled back from becomes the previous one, so a second rollback returns to it. To go back further, deploy the older version with --version. In Git, you make the same change by reverting the promotion. Delete and undo shows how.
Remove a deployment#
You remove integrations from an environment with weikio undeploy. The integrations’ versions stay published, so a later deploy starts them again without a build. Name the integrations, or remove every deployment of one project with --all and --project:
$ weikio undeploy --env devtest --all --project sandboxTarget: https://hub.example, project sandbox (--project), environment devtest (--env)
3 deployments will be removed from environment 'devtest': sandbox/csv-import, sandbox/erp-ping, sandbox/hello.
Continue? [y/N] y
deployment devtest/sandbox/csv-import deleted
deployment devtest/sandbox/erp-ping deleted
deployment devtest/sandbox/hello deletedweikio undeploy shows a confirmation prompt in every environment. If a deployment is running, Weik.io stops it first and removes it once its agents report the stop.