Skip to content
Weik.ioBlog
Try Weik.io

Weik.io 2026.2.0

Weik.io 2026.2.0 was published on 24 October 2026. Weik.io is an open source GitOps integration platform for Apache Camel integrations, file transfers, APIs and events.

An integration in Weik.io is a folder of Apache Camel routes. The routes can be YAML or XML files, or Java classes. You publish the folder as an immutable version with weikio apply and run a version in an environment with weikio deploy. weikio promote then copies a tested deployment from devtest to production without building it again. Weik.io runs on one server, or on as many as you need for high availability. Your own agents connect out to it on port 443.

Camel integrations

Weik.io loads routes, beans in beans/*.java, kamelets, route templates and REST DSL files as Camel loads them. In this release, each integration sets its Camel line to 4.18.5 or 4.22.1. Because Weik.io resolves the jars once per version, every agent runs the same files. Every running integration is its own Java process. An integration that must run one copy at a time uses Camel's master: component or singleton: true with a lock that Weik.io keeps. 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. Each end is an rclone remote, such as SFTP, FTP, S3, Azure Blob or a local folder. Devtest and production can point at different systems. Weik.io writes a log line for every file and publishes a summary event for every run. 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 that use API keys, OpenID Connect tokens, client certificates or one of the other types. Subscriptions have rate limits and expiry dates. Devtest and production answer on their own hostnames with their own keys. Weik.io obtains and renews the certificates for those hostnames. Every reply carries a traceresponse header that you can use to find 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. A channel with a type delivers to Slack, S3, SFTP, Kafka, JMS or HTTP. Every stored event carries its CloudEvents 1.0 attributes. When a reader keeps failing an event, the event goes to the dead letters. weikio deadletters resend sends it again from there. Change tracking captures database changes with Debezium. The entity store keeps what an integration has already processed. Events

Observability

Every integration has its own logs, metrics and traces. It sends them through OpenTelemetry with the integration, version, environment and agent as labels. Weik.io checks them every 15 seconds and raises problems for failing integrations, restart loops, growing memory and integrations that stopped. In Health you see the state of the whole platform. You can forward everything to Azure Monitor or Splunk, or to 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 and get roles that reach down to one integration or API. Weik.io encrypts secrets with AES-256-GCM and keeps every change in the audit log for 400 days. Read GitOps and the CLI and Security for the details.

Running it

Weik.io installs with Docker Compose on one Linux server or on as many as you need behind a load balancer. Upgrades take a backup first and roll back with upgrade.sh --rollback. By default, the hub is backed up every 24 hours on one server and every 6 hours on several. Each backup is copied to an S3 bucket when you set one. A standby hub keeps the newest backup restored. An air-gapped installation pulls its images from your registry and its Maven jars from one mirror.

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. The CLI in the container is already signed in:

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

On Windows, install the CLI with irm https://weik.io/install.ps1 | iex. On Linux, run the install script:

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

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

Sign in to the live demo

Sign in with the shared viewer account. It can open every screen of the example projects but can't change anything.

E-mail
viewer@demo.weik.io
Password
try-weikio-live-demo
Open the live demo