On your servers
Free
Self-hosted under the Apache License 2.0, with every feature, on Linux servers with Docker in your data centre or cloud account.
- Your team installs and runs it
- Support subscriptions from €490 a month
Weik.io for enterprises
The first Weik.io installation went into production in January 2018, and today Cross Wrap, Dinolift, Jouka, Junttan, Oscar Software, Steerprop and Tana run their integrations on Weik.io. It's made by Adafy Oy, a software company founded in Jyväskylä, Finland in 2012, and the whole platform is open source under the Apache License 2.0.
- January 2018
- First production installationThe company
- 2012
- Adafy Oy founded, Business ID 2480016-8Finnish trade register
- 2026.2.1
- Current release, published 28 October 2026Release notes
- 243,468
- Probe calls in the 24-hour release test, run through three failure drillsThe test
- Apache 2.0
- The licence of the whole platformOpen source
Companies that run their integrations on Weik.io
What your IT department checks
Each requirement in the terms your IT department uses, with Weik.io's answer and the docs page that shows how it works.
| Requirement | Weik.io's answer | Docs |
|---|---|---|
| High availability | Hub on three or five servers with failover, any backend answering any request, gateways on every server | Install a hub on three or five servers |
| Backup and restore | Sealed archives every 24 hours on one server or 6 hours on several, copies to your S3 storage or any rclone remote, restore onto new servers | Backups and restore |
| Disaster recovery | A standby hub that keeps the newest archive restored and ready | Standby hub |
| Upgrades | One command that makes a backup first, keeps every record and rolls back with --rollback | Upgrades and rollback |
| Single sign-on | Microsoft Entra ID and any OpenID Connect provider, with group claims mapped to grants | Sign-in and providers |
| Multi-factor sign-in | Two-factor sign-in with an authenticator app for local accounts, required of platform administrators | Two-factor sign-in |
| Roles and access | Viewer, editor, deployer and admin plus custom roles, granted per project and environment and down to one integration or API | Roles and grants |
| Audit log | Every change with its diff, actor, reason and commit, kept 400 days, forwardable to a SIEM | Audit log |
| Secrets | AES-256-GCM, revealing a secret is its own audited permission, Azure Key Vault and HashiCorp Vault through Dapr | Secrets |
| Network | Sites connect out on port 443, with no inbound port at a site | Network |
| Air-gapped installation | Images from your own registry and Maven through one mirror | Air-gapped installations |
| Monitoring integration | OpenTelemetry forwarding with examples for Azure Monitor, Splunk and OTLP SIEMs, Prometheus pages on every process | Telemetry forwarding |
| Data residency | Self-hosted wherever you run it, Weik.io Cloud in Helsinki, Finland | Sovereignty |
| Licence | Apache License 2.0 | Open source and open standards |
Three data servers in three zones sit behind a TCP load balancer that checks /readyz/node on each of them. Every server runs a TLS terminator, the backend, a gateway and a message server. Each data server keeps a copy of the stored data, and any backend answers any request. Backup copies go to S3 storage with Object Lock, where no key can delete a copy early, and a standby hub keeps the newest backup restored and ready.
How releases are 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.
Before the release candidate was built, a dependency check found no vulnerable package among the 56 NuGet packages of the platform's 10 projects. The end-to-end suite runs over the release images, and each release checks the licence of everything its images contain.
The product
Home shows what runs in each environment, and Settings shows the gateways with their hostnames, the health of every part of the platform and the audit log of every change.
weikio audit query line above the filters runs the same search.Where it runs
Weik.io Dedicated
From €2,990 a month
Run by the Weik.io team in your cloud account or data centre.
- Your account keeps the data and the backups
- Every action of the team is in your audit log
Weik.io Cloud
From €49 a month
A workspace in Helsinki, operated by Adafy Oy under Finnish law.
- Created in the console in a few minutes
- SFTP servers, MQTT brokers and object storage beside it
Sites run wherever an agent can connect out to the hub, whichever way you run Weik.io. weikio export and weikio apply move every integration and setting between the three.
Support and services
Support cases are handled by the team that develops Weik.io. A subscription covers one installation you run yourself, and Weik.io Dedicated and Weik.io Cloud include support.
| Subscription | What it covers | Price |
|---|---|---|
| Business hours | Monday to Friday 8 to 16 Finnish time, first response the next business day, upgrade help, security advisories before publication | €490 a month |
| Production | Business hours plus critical incidents around the clock with a first response within two hours, a named engineer and a yearly architecture review | €1,490 a month |
The Weik.io team also helps with:
- Onboarding, from the installation design to your first integrations in production
- Migration of separate Camel applications or an older integration platform
- Training with the Weik.io University videos and workshops for your team
If you leave
- Weik.io is open source under the Apache License 2.0, and your installation keeps running under it whatever you buy or stop buying.
- Your integrations are Camel files and YAML documents in your own Git repository.
weikio exportwrites every other document as YAML that applies unchanged to any Weik.io installation.
For the next reader
- How Weik.io is put together
For your architect: the hub and the sites, the network flows, where data lives, high availability and sizing.
- Security
For your security reviewer: the trust model, the controls with their docs pages, the release tests and how to report a vulnerability.
Both pages print cleanly from "Print or save as PDF" in their header.
Where Weik.io is going
The direction page lists what the next releases bring and where the product goes after them, from Windows sites and more Camel versions to the services of Weik.io Cloud.
Questions
Does Weik.io need Kubernetes?
No, the hub and the sites run with Docker Compose on Linux servers.
Can integrations run inside a company network?
Yes, an agent at your site runs them and connects out to the hub on port 443, with no inbound port opened at the site.
How is Weik.io priced?
There's no fee per integration, agent or user. Support subscriptions, Weik.io Dedicated and Weik.io Cloud have monthly prices on the pricing page.
Does Weik.io run on Windows?
The CLI runs on Windows today, and Windows sites arrive with Weik.io 2026.2.2, with an MSI installer for Windows Server 2022 and 2025.
What happens if you stop paying for support?
Your installation keeps running under the Apache License 2.0, with every feature.
Who makes Weik.io?
Adafy Oy, a Finnish software company, Business ID 2480016-8, at Lutakonaukio 1, 40100 Jyväskylä, Finland. The company page has the facts and the contacts.
Book a demo
In an hour, an engineer from the Weik.io team shows the product with integrations like yours and goes through how your team would run it.