Open source GitOps integration platform
Integrations in Weik.io are Apache Camel routes in YAML, XML or Java, and they can use Camel's components and kamelets. You keep them in Git and promote each version from devtest to production with the weikio CLI or the admin UI. Every integration has its own logs, metrics and traces. Weik.io is open source under the Apache License 2.0 and runs on your own servers, in your cloud or in Weik.io Cloud.
Some of the companies that run their integrations on Weik.ioFirst production installation in January 2018
For developers
Run the whole platform on your machine in the Try Weik.io dev container, or call the live demo's API from your terminal and find your own call in its admin UI. weikio init hello creates an integration, and weikio run hello builds it, deploys it to devtest and follows its log.
$ weikio init hello
$ weikio run helloFor enterprises
Cross Wrap, Dinolift, Jouka, Junttan, Oscar Software, Steerprop and Tana run their integrations on Weik.io, and the first installation went into production in January 2018. Weik.io runs on as many servers as you need across your data centres with failover, and backs up on a schedule to your own storage. People sign in through Microsoft Entra ID or any OpenID Connect provider, and the audit log keeps every change for 400 days. Weik.io is made in Finland by Adafy Oy, and Weik.io Cloud runs in Helsinki.
Apache Camel integrations in YAML, XML or Java, each with versions, environments, logs, metrics and traces.
- route:
from:
uri: timer:tick?period=60000
steps:
- setHeader:
name: Authorization
simple: "Bearer {{erp-api-key}}"
- to: "{{erp-url}}/api/invoices/pending"
- to: direct:transformFiles between SFTP and FTP servers, cloud storage and local folders on a schedule, with a record of every file.
kind: mft
spec:
schedule: "0 0 5 * * ?"
operation: move
source:
remote: supplier-ftp
path: /outgoing
destination:
remote: invoice-archive
path: invoices/incomingA gateway in front of any HTTP API, with keys, rate limits and a record of every call.
kind: api-version
spec:
type: proxy
rateLimit:
permitLimit: 600
window: 1m
clusters:
- ClusterId: erp
Destinations:
erp: { Address: "{{erp-url}}" }Channels between integrations that react now or later, with CloudEvents attributes on every event and dead letters you can resend.
Logs, metrics, traces and problems for every integration and API.
A change starts in a folder in Git. A pull request runs weikio diff, and the pipeline posts the plan as a comment. The merge runs weikio apply and the change reaches devtest. Promoting a tested version to production is a pull request that changes the version, and production applies it after the repository's required reviewers approve. git revert rolls a change back through the same steps.
Integrations, APIs, channels and deployments are YAML documents you can keep in your repository. A pull request runs weikio diff and posts the plan, and the merge applies the change to devtest. Promotion to production is a pull request that changes the version. A change made in the admin UI becomes a version too, and the audit log records who made it.
$ weikio apply -f ./finance/erp-invoice-export --bump minor
Target: https://hub.example, project finance (from finance/project.yaml)
Uploading 2/9 files, building...
integration finance/erp-invoice-export updated (version 1.1.0, built in 17.3 s)
integration.yaml updated to 1.1.0
$ weikio promote finance/erp-invoice-export --from devtest --to production
Target: https://hub.example, project finance (argument), environment production (--to)
This will promote 'finance/erp-invoice-export' 1.1.0 to production environment 'production'.
Continue? [y/N] y
Promoting finance/erp-invoice-export 1.1.0 (latest) to production...
deployment production/finance/erp-invoice-export updated (version 1.0.0 -> 1.1.0, previous 1.0.0)
Agents: 1 of 1 running after 4.0 s
$ weikio rollback finance/erp-invoice-export --env production
Target: https://hub.example, project finance (argument), environment production (--env)
deployment production/finance/erp-invoice-export updated (version 1.1.0 -> 1.0.0, previous 1.1.0)
Agents: 1 of 1 running after 3.7 sThe hub runs a message server, the backend, the gateway and the log, metric and trace stores on one server, or on as many as you need for high availability, and it publishes port 443. Agents in three places connect to it: at a factory inside a customer network, in the customer's Azure account and as cloud agents in Weik.io Cloud. Each agent starts one Java process per running integration, with a small message server beside the agent, and it opens two outbound connections to the hub on port 443, wss for the message server and https for telemetry. No agent accepts an inbound connection.
Integrations run wherever you install an agent: on your on-premise servers, in your cloud account, inside a factory network or on cloud agents in Weik.io Cloud. An agent connects to Weik.io with two outbound connections on port 443 and opens no inbound port.
Weik.io runs on one server, or on as many as you need for high availability, in one data centre or across several. The CLI runs on Linux and Windows, and agents run on Linux hosts and on Windows Server 2022 and 2025.
Weik.io is open source under the Apache License 2.0, and it uses open standards where your integrations meet other systems:
Weik.io University has short videos, and every video page has its commands and links to the docs pages it teaches.
Free
Every feature, on your servers or in your cloud, with support from the Weik.io team by agreement.
From €2,990 a month
Run by the Weik.io team in your cloud account or data centre.
From €590 a month
Managed Weik.io on servers in Helsinki, operated by Adafy Oy.
integration.yaml or application.properties, and integrations on 4.18.5 and 4.22.1 run next to each other on the same agents.Moving separate Camel applications into Weik.io A Camel integration that runs as its own application becomes a folder of routes, beans, kamelets and properties, and gets versions, environments, logs, metrics and traces.Weik.io 2026.2.0 Weik.io is an open source GitOps integration platform. The release has Camel integrations as versioned folders, file transfers, API management, events, observability and the weikio CLI, and the post goes through each part.Run Weik.io on your laptop, or book a demo and an engineer from the Weik.io team shows it with integrations like yours.