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.
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 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. The hub runs on three or five servers with failover and makes scheduled backups 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.
Each area has its product page, its docs, its videos, a view in the live demo and an example in the GitHub repository.
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 and other systems, with retries and dead letters.
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 one-line 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.
Every integration, API, channel and deployment is a YAML document you can keep in Git. A pull request runs weikio diff and posts the plan, and the merge applies the change to devtest. Promoting a tested version to production is a one-line pull request. Changes made in the admin UI are versions too, and the audit log records who changed what.
$ 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 (context), 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 (context), 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 three or five for high availability, and it publishes port 443. Three sites connect to it: a factory site inside a customer network, a site in the customer's Azure account and cloud agents in Weik.io Cloud. Each site has a leaf node and an agent that starts one Java process per running integration, and it opens two outbound connections to the hub on port 443, wss for the leaf node and https for telemetry. No site accepts an inbound connection.
Integrations run wherever an agent is enrolled: on your servers, in your cloud account, inside a factory network or on cloud agents in Weik.io Cloud. A site connects to the hub with two outbound connections on port 443 and opens no inbound port, and the hub runs on one server, or on three or five for high availability. The CLI runs on Linux and Windows today, and Windows sites arrive with Weik.io 2026.2.2.
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 with the commands to follow along, and every video links the docs pages it teaches.
Free
Every feature under the Apache License 2.0, on your servers or in your cloud, with support subscriptions available.
From €2,990 a month
Run by the Weik.io team in your cloud account or data centre.
From €49 a month
Managed Weik.io, SFTP servers, MQTT brokers, object storage and AI models in Helsinki, operated by Adafy Oy. You create a workspace yourself in the console.
weikio CLI, and the post goes through each part.Testing 2026.2.0 for 24 hours on three servers The release candidate handled 250 deployments and 34 events a second for 24 hours through three failure drills, and the stores received every telemetry record the sites sent.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.The dev container runs the whole platform on your laptop, and the live demo needs nothing installed.