Running deployments

A deployment is one integration in one environment: the version it runs, whether it should be started, and its own overrides. It runs on every agent that matches it. Every command on this page changes the deployment record, and the agents that run it act on the change within a second or two.

Deploy#

$ weikio deploy finance/erp-invoice-export

Target: 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 -> 1.1.0)
Agents: 1 of 1 running after 3.4 s

--version picks a version and defaults to latest, and the CLI always prints the version it resolved. -f ./finance/events deploys every integration a folder has, --stopped writes the deployment without starting it, and --set erp-page-size=50 gives this deployment an override of its own. In a production environment --env is always needed.

Stop and restart#

$ weikio stop    finance/erp-invoice-export --env production   # the process stops, the deployment stays
$ weikio start   finance/erp-invoice-export --env production
$ weikio restart finance/erp-invoice-export --env production   # stops and starts with freshly resolved values

restart is how a deployment gets a changed variable or secret right away. A restart or a start is refused while a secret the version uses has no value in the environment, because the process would fail at its start.

Roll back#

$ weikio rollback finance/erp-invoice-export --env production

Target: 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.7 s

A rollback moves the deployment to its previous version, which is already built, and the version it replaced becomes the new previous one. In a repository, follow it with a git revert of the promotion, so the next apply from Git doesn’t move it forward again.

Undeploy#

weikio undeploy deletes the deployment. The version and its files stay, so a later deploy starts it again with no build:

$ weikio undeploy --env devtest --all --project sandbox

Target: https://hub.example, project sandbox (--project), environment devtest (--env)
3 deployments will be removed from environment 'devtest': sandbox/hello, sandbox/csv-import, sandbox/erp-ping.
Continue? [y/N] y
deployment devtest/sandbox/hello deleted
deployment devtest/sandbox/csv-import deleted
deployment devtest/sandbox/erp-ping deleted

A running deployment is stopped first, and the lines it writes while it stops are kept.

See what runs#

weikio status shows one integration in every environment:

$ weikio status finance/erp-invoice-export

ENVIRONMENT   VERSION   STATE     AGENT         SINCE                  DETAIL
devtest       1.0.0     running   agent-fi-01   2026-09-15 09:14 UTC   -
production    1.0.0     running   agent-fi-02   2026-09-15 16:02 UTC   -

The DETAIL column explains a deployment that isn’t running yet, such as one waiting for its agent’s next report, or one no agent matches, with the reason. --watch keeps the view open and updates it.

weikio get deployments shows every deployment of an environment:

$ weikio get deployments --env production

PROJECT   INTEGRATION          VERSION   DESIRED   ACTUAL    AGENTS                   SINCE
finance   erp-invoice-export   1.0.0     started   failed    2/3 running, 1 failed    2026-09-16 14:40 UTC
finance   invoice-archive      1.4.2     started   running   3/3 running              2026-09-15 09:12 UTC
finance   ledger-sync          0.8.0     started   pending   0/1 running, 1 offline   2026-09-12 11:30 UTC
finance   nightly-payroll      2.3.1     stopped   stopped   0/2 running, 2 stopped   2026-09-10 02:05 UTC

The AGENTS column counts the copies: a deployment runs on every matching agent, so 2/3 running, 1 failed means one of its three agents has a problem. weikio get fleet lists every deployment and agent pair across environments and projects. weikio describe deployment finance/erp-invoice-export --env production shows one deployment with its previous version, its overrides, who deployed it and when, and each agent’s process with its PID, restarts and last exit.

In the admin UI, Home lists the integrations and APIs deployed in one environment, with who deployed them and when, and offers undeploy and promote on each integration’s row. An integration’s Environments section shows each copy with its agent, its state and its memory.