Operate
Weik.io 2026.2Install Weik.io and its agents on your servers, and keep the installation running.
On this page
Weik.io runs on one Linux server with Docker Compose, or on as many servers as you need with failover for high availability, in one data centre or across several. Agents run your integrations on Linux or Windows Server hosts of your own. An agent opens no inbound port on its host, because it connects out to Weik.io on port 443.
You run the commands on these pages in the stack folder that weikio-backend init writes, or with the weikio CLI from your own machine. The stack folder also has a README.md that init writes for the release you installed.
To try Weik.io before you install it, run it in a dev container with Try Weik.io on your machine.
Pages#
Install Weik.io on one server Install Weik.io on one Linux server with
weikio-backend init and Docker Compose, then sign in with two-factor and connect the weikio CLI.Install Weik.io on several servers Weik.io runs on as many servers as you need, in one data centre or across several, behind a TCP load balancer that sends callers and agents to the servers that are ready.Install an agent An agent runs your integrations on an on-premise host or in your cloud account. Its host opens no inbound port, because the agent connects out to Weik.io on port 443.Agents on Windows Run an agent on Windows Server 2022 or 2025, installed from an MSI that brings its .NET and Java runtimes.Health and problems See the state of every part of the platform in Settings › Operations › Health, and what needs attention in the problem list.Logs, metrics and traces Every integration sends its telemetry to Weik.io through OpenTelemetry. You read it with the weikio CLI or on the admin UI's Observability pages.Telemetry forwarding Forward Weik.io's logs, metrics, traces and audit records to Azure Monitor, Splunk or any system that accepts OTLP.Backups and restore The hub writes a sealed backup archive every 24 hours on one server or every 6 hours on several, and copies each one to an S3 bucket with Object Lock or to any rclone remote.Upgrades and rollback upgrade.sh backs up the hub and moves it to a new release. upgrade.sh --rollback returns it to the release before and keeps every record stored since.Standby hub A standby hub on a second host restores and checks the primary's newest backup every six hours and takes over under the primary's names when you activate it.Certificates Weik.io obtains and renews the certificate of every hub name and gateway hostname from Let's Encrypt or another certificate authority, such as your own or the platform's.Storage and its budget Size the hub's message storage with the disk budget, and set how many days the log, metric and trace stores keep their records.Behind a CDN Put the names of your Weik.io installation behind Cloudflare's proxy and keep each caller's address in the audit trail.Air-gapped installations An air-gapped installation pulls its images from your own registry and resolves every Camel dependency through one Maven mirror.Encryption at rest Weik.io encrypts secrets and keys with AES-256-GCM under the installation's master key. You encrypt the hub's disks through your provider or with LUKS2.Sizing Size the hub and the agents from the measured image size and memory of each part of Weik.io.