Weik.io 2026.2.0
Weik.io 2026.2.0 has a hub on one, three or five servers, sites with agents that connect out on port 443, Camel integrations as versioned folders, the gateway, events, logs, metrics and traces, and the weikio CLI for GitOps.
Highlights
Camel integrations
An integration is a folder of Apache Camel routes in YAML, XML or Java, with beans, kamelets and properties beside them. weikio apply publishes it as an immutable version. The hub resolves its jars once, so every agent runs the same files. Each integration picks Camel 4.18.5 or 4.22.1, runs as its own Java process, and can run as several copies or as one copy at a time with the lock kept by the hub.
Managed file transfer
A transfer of kind: mft moves files on a schedule between any two rclone remotes, SFTP, FTP, S3, Azure Blob and local folders among them, with copy, move, sync and filters. Each file leaves a log line, each run publishes a summary event, and a run with errors raises a problem.
API management
The gateway fronts any HTTP API, and its routes and clusters use the configuration of YARP, Microsoft's open source reverse proxy. Subscriptions use API keys, query parameters, basic authentication, OpenID Connect tokens or client certificates, with rate limits and expiry. Each environment answers on its own hostnames with certificates the platform obtains and renews, webhooks land in event channels, and every reply carries a traceresponse header.
Events
Channels, event sources and subscriptions connect integrations through the environment's event stream. Failed events go to the dead letters and can be sent again, change tracking captures database changes with Debezium, and the entity store keeps what integrations have processed.
Observability
Logs, metrics and traces arrive through OpenTelemetry with the integration, version, environment and agent on every record. The platform checks for problems every 15 seconds, Health shows every part of the platform, and telemetry and the audit trail can be forwarded to Azure Monitor, Splunk or an OTLP receiver.
Delivery, security and operations
The weikio CLI applies a Git repository from any pipeline, with one key per environment and a plan before every change. Sign-in goes through Microsoft Entra ID or OpenID Connect, roles reach down to one integration, secrets are sealed with AES-256-GCM and the audit log keeps 400 days. The hub runs on one, three or five servers, with backups to S3, a standby hub, and upgrades that take a backup first and roll back with one command.
Images
The images are on Docker Hub with the exact version as their tag, and images.env pins each one by its digest. No image is tagged latest.
| Image | Digest |
|---|---|
weikio/ | sha256:f600659b34af… |
weikio/ | sha256:d793d9bbb912… |
weikio/ | sha256:c0d8d5244d48… |
weikio/ | sha256:06a3a95d4473… |
The table shows the start of each digest, and images.env has them in full, with the images of the stores and the message server.
CLI files
The checksums are from the release's SHA256SUMS, and the Windows CLI is signed by Adafy Oy. curl -fsSL https://weik.io/install.sh | sh checks them before it places the CLI.
| File | SHA-256 |
|---|---|
| weikio-2026.2.0-linux-x64 | 56763447473b9af960e02868eb8eabd85413e63a34a03653f1c4b295292e503a |
| weikio-2026.2.0-win-x64.exe | 9e89838f4d95575fe3bd532ae31d78912d85dcfb43eb0ceaf9299a5a8d1e49b0 |
The open source projects inside the images, with their versions and licences, are listed in Third-party software. The release ships Apache Camel 4.22.1 and 4.18.5, OpenJDK 21.0.12, .NET 10, NATS 2.14.7 and rclone 1.75.1.
Upgrade notes
Weik.io 2026.2 is installed new, either next to a 2026.1 installation or in its place. Its images have new names, such as weikio/weikio-backend, so a 2026.1 installation never pulls a 2026.2 image by mistake. The 2026.1 docs stay at weik.io/docs/2026.1.
From 2026.2.0 on, an installation upgrades in place: upgrade.sh makes a backup first, keeps every record and every file of yours, and --rollback goes back to the previous release.
$ sudo sh ./upgrade.sh https://weik.io/downloads/releases/2026.2.0/images.env
$ sudo sh ./upgrade.sh --rollbackUpgrades and rollback in the docs has the check before an upgrade, the rollback and the rolling upgrade of a hub on several servers.
Security
Before 2026.2.0 was released, its release candidate ran for 24 hours on a three-server hub with 250 deployments and 34 events a second. During the run, drills paused one storage server for 30 seconds, stopped the telemetry stores for 15 minutes and cut a site off from the hub for 15 minutes. Of the 243,468 probe calls, the only failures came during the 30-second pause the test caused on purpose, and the stores received every telemetry record the sites sent.
Adafy's security team, which is separate from the development team, then tested the release candidate from the internet and found nothing rated critical or high.