Skip to content
Weik.io
Book a demoTry Weik.io

Open source GitOps integration platform

Weik.io manages your integrations, APIs, file transfers and events

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.

/integrations/finance/erp-invoice-export
The page of finance/erp-invoice-export with version 1.2.0 running in devtest on the agent dev and in production on fi-01, where 1.1.0 ran before. The last hour of production has no failed messages. The log lines of production follow.The page of finance/erp-invoice-export with version 1.2.0 in devtest and 1.1.0 in production, where 8 of 88 messages failed in 15 minutes. The last hour of production has its messages, failures, memory and the counter invoices_processed.

Some of the companies that run their integrations on Weik.ioFirst production installation in January 2018

For developers and for enterprises

For developers

Try it on your machine

Run the 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. weikio run hello builds it and deploys it to devtest, then follows its log.

Terminal
$ weikio init hello
$ weikio run hello

For enterprises

Run it in production

The first Weik.io installation went into production in January 2018. Today Cross Wrap, Dinolift, Jouka, Junttan, Oscar Software, Steerprop and Tana run their integrations on Weik.io. It 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. The audit log keeps every change for 400 days. Adafy Oy makes Weik.io in Finland and runs Weik.io Cloud in Helsinki.

What Weik.io manages

Camel integrations

Your integrations are Apache Camel routes in YAML or XML files, or in Java classes. Each has versions, environments, logs, metrics and traces.

routes/fetch-invoices.camel.yaml
- route:
    from:
      uri: timer:tick?period=60000
      steps:
        - setHeader:
            name: Authorization
            simple: "Bearer {{erp-api-key}}"
        - to: "{{erp-url}}/api/invoices/pending"
        - to: direct:transform

Managed file transfer

Transfers move files on a schedule between SFTP servers, FTP servers, cloud storage and local folders. Weik.io keeps a record of every file.

finance/transfers/supplier-invoices.yaml
kind: mft
spec:
  schedule: "0 0 5 * * ?"
  operation: move
  source:
    remote: supplier-ftp
    path: /outgoing
  destination:
    remote: invoice-archive
    path: invoices/incoming

API management

API management puts a gateway in front of any HTTP API. The gateway checks keys and rate limits and records every call.

finance/apis/invoices/v1.yaml
kind: api-version
spec:
  type: proxy
  rateLimit:
    permitLimit: 600
    window: 1m
  clusters:
    - ClusterId: erp
      Destinations:
        erp: { Address: "{{erp-url}}" }

The admin UI

/
The Home page with devtest and production. The production list has the versions of erp-invoice-export, invoice-archiver, the invoices API and supplier-invoices, and whether devtest runs the same ones.The Home page with devtest and production. The production list has the versions of erp-invoice-export, invoice-archiver, the invoices API and supplier-invoices, and whether devtest runs the same ones.The Home page with the deployments running in test and in devtest. Production and its deployments are on the page too.The Home page with the deployments running in test and in devtest. Production and its deployments are on the page too.
On Home, you see each environment with its deployments. In production, you also see the version of each integration and API and whether devtest runs the same one.

From Git to production

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. Merging it 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. The audit log records who made it.

GitOps and the CLI

Terminal
$ 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 s

Where it runs

The 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. It publishes port 443. Agents connect to it from a factory inside a customer network and from the customer's Azure account. Cloud agents in Weik.io Cloud connect to it too. Each agent has a small message server beside it and starts one Java process per running integration. Each agent's two outbound connections to the hub on port 443 are wss for the message server and https for telemetry. No agent accepts an inbound connection.

A Weik.io installation: the hub at the top, and the agents that connect out to it on port 443. The leaf node beside each agent is a small message server that carries its messages.

An agent runs your integrations on your on-premise servers, in your cloud account, inside a factory network or as a cloud agent in Weik.io Cloud. It 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. Agents run on Linux hosts and on Windows Server 2022 and 2025.

How Weik.io is put together

Open source and open standards

Weik.io is open source under the Apache License 2.0. It uses open standards where your integrations meet other systems:

  • Apache Camel for integrations
  • CloudEvents 1.0 for stored and delivered events
  • OpenAPI for the platform's HTTP API and for calling other APIs from integrations
  • OpenTelemetry for logs, metrics and traces
  • OpenID Connect for sign-in and API subscriptions

Open source and open standards

Ways to run Weik.io

Self-hosted

Free

Every feature on your servers or in your cloud, and support from the Weik.io team by agreement.

Weik.io Dedicated

From €2,990 a month

Run by the Weik.io team in your cloud account or data centre.

Weik.io Cloud

From €590 a month

Managed Weik.io that Adafy Oy operates on servers in Helsinki.

Compare the prices

Try Weik.io

Run Weik.io on your laptop, or book a demo. An engineer from the Weik.io team shows it with integrations like yours.

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