Weik.io 2026.2.0

Weik.io 2026.2.0 was published on 24 October 2026. This post describes how an integration is built and versioned in it, how it reaches production, where it runs and how you see what it's doing.

An integration in Weik.io is a folder of Apache Camel routes in YAML, XML or Java. weikio apply publishes the folder as an immutable version, weikio deploy runs a version in an environment, and weikio promote copies a tested deployment from devtest to production without building it again. The hub runs on one server, or on three or five for high availability, and agents at your sites connect out to it on port 443.

Camel integrations

Routes in YAML, XML and Java, beans in beans/*.java, kamelets, route templates and REST DSL files are loaded as Camel loads them. Each integration picks its Camel line, 4.18.5 or 4.22.1 in this release. The hub resolves the jars once per version, so every agent runs the same files. Every running integration is its own Java process, and an integration that must run one copy at a time uses Camel's master: component or singleton: true, with the lock kept by the hub. Camel integrations

Managed file transfer

A transfer is a short YAML document with a schedule, a source, a destination and an operation such as copy, move or sync. Both ends are rclone remotes, so SFTP, FTP, S3, Azure Blob and local folders work. Devtest and production can point at different systems. Every file leaves a log line, every run publishes a summary event, and a failed run raises a problem. Managed file transfer

API management

The gateway fronts any HTTP API, from your own integrations to an ERP's REST interface. Consumers get subscriptions with API keys, OpenID Connect tokens, client certificates or the other types, with rate limits and expiry dates. Devtest and production answer on their own hostnames with their own keys, the platform obtains and renews the certificates, and every reply carries a traceresponse header that finds the trace of the call. Webhooks land in event channels. API management

Events

Channels carry events between integrations, event sources bring them in from queues, buckets, webhooks and folders, and a channel with a type delivers to Slack, S3, SFTP, Kafka, JMS or HTTP. A reader that keeps failing an event sends it to the dead letters, from where weikio deadletters resend sends it again. Change tracking captures database changes with Debezium, and the entity store keeps what an integration has already processed. Events

Observability

Every integration sends its logs, metrics and traces through OpenTelemetry, labelled with the integration, version, environment and agent. The backend checks them every 15 seconds and raises problems for failing integrations, restart loops, growing memory and integrations that stopped. Health shows the state of the whole platform, and the hub forwards everything to Azure Monitor, Splunk or any OTLP receiver. Observability

Delivery and security

Your Git repository has the integrations, variables, channels, APIs and deployments. Your pipeline applies them with the CLI, so the platform needs no Git credentials. People sign in through Microsoft Entra ID or any OpenID Connect provider, roles reach down to one integration or API, secrets are sealed with AES-256-GCM, and the audit log keeps every change for 400 days. GitOps and the CLI and Security have the details.

Running it

A hub installs with Docker Compose on one Linux server or on three or five behind a load balancer. Upgrades take a backup first and roll back with one command, backups go to your S3 storage every 6 or 24 hours, and a standby hub keeps the newest backup restored. An air-gapped hub pulls its images from your registry and its Maven jars from one mirror.

How it was tested

The release candidate ran for 24 hours on a three-server hub with 250 deployments, 34 events a second and three failure drills, and the stores received every telemetry record the sites sent. Adafy's security team, which is separate from the development team, then tested it from the internet and found nothing rated critical or high. Testing 2026.2.0 for 24 hours on three servers has the numbers.

Try it

The Try Weik.io dev container runs the whole platform on your machine. Open the repository in Visual Studio Code with the Dev Containers extension, and the CLI in the container is already signed in:

$ git clone https://github.com/weikio/try-weikio
$ weikio init hello
$ weikio run hello

To install the CLI on Linux, or with irm https://weik.io/install.ps1 | iex on Windows:

$ curl -fsSL https://weik.io/install.sh | sh

The release notes list the files, the images and their checksums, the docs cover every part of 2026.2, and Weik.io University has 41 short videos with the commands to follow along.