Operate
Weik.io 2026.2Install a hub on one server or several, run sites on Linux 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. The hub runs on one Linux server with Docker Compose, or on three or five servers with failover for high availability. Agents run your integrations at your sites and connect out to the hub on port 443, with no inbound port open at the site. A site’s host runs Linux. After the installation, 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 a hub, Try Weik.io on your machine runs the whole platform in one dev container.
Pages#
weikio-backend init and Docker Compose, then sign in with two-factor and connect the weikio CLI.Install a hub on three or five servers The hub runs on three or five data servers that each keep a copy of its storage, and a TCP load balancer sends callers and sites to the servers that are ready.Sites and agents An agent runs your integrations at a site and connects out to the hub on port 443, with no inbound port open at the site.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 the hub 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 the platform'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 The platform 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 log, metric and trace stores keep their records within caps and days of their own.Behind a CDN The hub's names can sit behind Cloudflare's proxy, and the audit trail still records each caller's own address.Air-gapped installations An air-gapped hub pulls its images from your own registry and resolves every Camel dependency through one Maven mirror.Encryption at rest The platform 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 a hub and its sites need to run them.