Operate
Weik.io 2026.2Install Weik.io on one server or several, run agents on Linux and Windows hosts, watch the platform and keep it backed up, upgraded and sized.
On this page
These pages are for the person who runs a Weik.io installation. 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 hosts of your own and connect out to Weik.io on port 443, with no inbound port open on the host. An agent’s host runs Linux or Windows Server. After you install, the pages cover the daily work: the Health page and the problem list, logs, metrics and traces, forwarding telemetry to your own monitoring, backups and restore, upgrades with rollback, a standby hub for disaster recovery, certificates, storage and sizing.
Every command on these pages runs in the stack folder that weikio-backend init writes, or with the weikio CLI from your own machine. The stack folder also has its own README.md, which init writes for the release you installed.
If you want to try Weik.io before you install it, Try Weik.io on your machine runs the whole platform in a dev container.
Pages#
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, and a TCP load balancer 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 and connects out to Weik.io on port 443, with no inbound port open on its host.Agents on Windows An agent runs on Windows Server 2022 and 2025, installed from one MSI that brings its own .NET and Java runtimes.Health and problems Settings › Health shows every part of the platform with its state, and the problem list says what needs attention now.Logs, metrics and traces Every integration sends its log lines, metrics and traces to Weik.io through OpenTelemetry, and you read them with the weikio CLI or on the admin UI's Observability pages.Telemetry forwarding One telemetry-forwarding document sends Weik.io's logs, metrics, traces and audit records to Azure Monitor, Splunk or any system that accepts OTLP.Backups and restore The hub takes 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 any rclone remote.Upgrades and rollback upgrade.sh takes a backup and moves the hub to a new release, and upgrade.sh --rollback returns 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 it 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, your own certificate authority or the platform's own authority.Storage and its budget The disk budget caps the hub's message storage, and the installation settings say how many days the log, metric and trace stores keep their records.Behind a CDN The names of your Weik.io installation can be behind Cloudflare's proxy, and the audit trail still records each caller's own address.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 seals every secret, password hash and key with AES-256-GCM under the installation's master key, and the hub's disks are encrypted by your provider or with LUKS2.Sizing The measured image size and memory of every part of Weik.io, and what the hub and the agents need to run them.