Weik.io 2026.2.1 updates 2026.2 with the fixes from the release test of 2026.2.0 and with stricter security on the gateway and at the sites. An installation of 2026.2.0 upgrades to it in place.

Release notes: https://weik.io/releases/2026.2.1

Highlights

• The gateway adds Referrer-Policy, X-Content-Type-Options and Permissions-Policy to every reply and passes the caller's cookies on only when the API's route asks for them
• A site stops what it runs once it has been cut off from the hub for longer than its environment's offline limit, 24 hours unless you set another
• The backend's memory stays level on hub servers that run for weeks, which was the one finding of the 24-hour release test of 2026.2.0
• The live tail shows the log lines that arrive late, such as the lines a site kept while it couldn't reach the hub
• weikio deploy and weikio promote into production have the platform check the change before they ask, and the plan of weikio apply --dry-run shows the warnings of the upload
• Builds work on both Camel versions behind a Maven mirror with no internet access, and a build that is missing a jar fails and shows which one
• The texts of the admin UI and the CLI say what happened and what to do next

Images

Each image is tagged with the exact version, and images.env below lists each one with its digest:

• weikio/weikio-backend:2026.2.1
• weikio/weikio-agent:2026.2.1
• weikio/weikio-apim:2026.2.1
• weikio/weikio-forwarder:2026.2.1

Upgrading from 2026.2.0

Before you upgrade, set the offline limit of every environment whose sites may stay cut off from the hub for more than 24 hours, and set the Metadata key weikio-forward-cookies to "true" on the route of each API whose service needs the caller's cookies. Upgrade the hub before you use a 2026.2.1 CLI for weikio delete environment, or for weikio deploy and weikio promote into production. The release notes have the details and the known issues, and the upgrade guide is https://weik.io/docs/operate/upgrades-and-rollback.

Links

• Weik.io: https://weik.io
• Docs: https://weik.io/docs
• University: https://weik.io/university
• Weik.io Cloud: https://weikio.cloud
• Live demo: https://demo.weik.io
• GitHub: https://github.com/weikio/weikio

Weik.io 2026.2.0 manages your integrations, APIs, file transfers and events. The hub keeps your integrations, APIs and their versions and serves the admin UI and the HTTP API, agents run the integrations at your sites, and the gateway publishes your APIs. You manage all of it with the weikio CLI from your Git pipelines or in the admin UI.

Release notes: https://weik.io/releases/2026.2.0

Highlights

• Camel integrations in YAML, XML or Java on Apache Camel 4.22.1 and 4.18.5, each with immutable versions that you deploy, promote from devtest to production and roll back
• Managed file transfers on a schedule between SFTP, FTP, S3, Azure Blob and local folders, with a log line for every transferred file
• API management with API keys, OpenID Connect tokens, client certificates, rate limits and webhooks, and a trace for every call
• Event channels with retries, dead letters, resend and database change tracking
• Logs, metrics and traces of every integration through OpenTelemetry, with Health and Problems in the admin UI and forwarding to Azure Monitor, Splunk or any OTLP receiver
• A hub on one, three or five servers, sites that connect out on port 443 and open no inbound port, backups every 24 or 6 hours and a standby hub

Images

Each image is tagged with the exact version, and images.env below lists each one with its digest:

• weikio/weikio-backend:2026.2.0
• weikio/weikio-agent:2026.2.0
• weikio/weikio-apim:2026.2.0
• weikio/weikio-forwarder:2026.2.0

How it was tested

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.

Installing and upgrading

Weik.io 2026.2 is installed new, either next to a 2026.1 installation or in its place. Its images have new names, so a 2026.1 installation never pulls a 2026.2 image by mistake. The 2026.1 docs stay at https://weik.io/docs/2026.1, and the guide to installing a hub is https://weik.io/docs/operate/install-single-server.

Links

• Weik.io: https://weik.io
• Docs: https://weik.io/docs
• University: https://weik.io/university
• Weik.io Cloud: https://weikio.cloud
• Live demo: https://demo.weik.io
• GitHub: https://github.com/weikio/weikio