Try Weik.io
Check the current release, its licence and its images, then call the live demo's API from your own terminal and find your call in the demo's admin UI. To run Weik.io yourself, start the whole platform on your machine in a dev container or install a hub on a Linux server.
Check it in a minute
Release
2026.2.1, published 28 October 2026, with SHA256SUMS for every file. The Windows CLI is signed by Adafy Oy. The files are also on the GitHub release.
Licence
Apache License 2.0. Every image contains /LICENSE, /NOTICE and /THIRD-PARTY-NOTICES.txt.
Images
weikio/weikio-backend, weikio/weikio-agent, weikio/weikio-apim and weikio/weikio-forwarder, tagged with the exact version, with no latest tag.
The call
Copy this call into a terminal on your own machine. It goes to the API echo on the live demo's gateway without a key. The gateway answers 401, and its answer carries a traceresponse header with the ID of the call's trace.
$ curl -i https://api-test.demo.weikiolab.com/echo/v1/HTTP/2 401
www-authenticate: ApiKey
content-length: 0
strict-transport-security: max-age=31536000
x-content-type-options: nosniff
referrer-policy: no-referrer
permissions-policy: camera=(), microphone=(), geolocation=(), payment=()
traceresponse: 00-25978b47a71d0bcdc2ace0d95319d1db-835efab335bfc965-01Find your call
In the live demo, go to APIs, open echo and open Requests. The newest row is your call, and its trace opens with one click.
Three ways to run it
The live demo is a Weik.io installation with the example project finance: a Camel integration that fails a share of its messages on purpose, a transfer that moves files every minute, an API with traffic, and a channel with events and dead letters. As the viewer you can open every screen of the projects demo and finance in every environment. The viewer can't change anything or reveal a secret, and the installation is restored to a clean state every night.
- Home
The environments, what runs in production and Needs attention, with the failing integration in it.
- Camel integrations
Open
finance/erp-invoice-exportand then Metrics for its six numbers and the messages chart with failure markers. - Traces
A failed trace of
finance/erp-invoice-exportshows the HTTP call to the ERP as three numbered attempts. - Transfers
Open
finance/supplier-invoicesand then Runs for the files each run moved. - APIs
Open
invoicesand then Requests for one row per call, with the subscription and the status of each. - Observability
What runs in production, the problems and the failed messages and traces of the last hour.
The Try Weik.io dev container runs the whole platform in one container: the message server, the log, metric and trace stores, the backend with the admin UI, the gateway and an agent called dev. The weikio CLI inside it is signed in as the platform admin, in project sandbox and environment devtest.
What you need:
- Docker with 8 GB of memory (6 GB at least), 4 CPUs and 20 GB of free disk
- Visual Studio Code with the Dev Containers extension, or the
devcontainercommand line - Internet access for the first build of the container
The images are built for Intel and AMD processors, and on a Mac with Apple silicon Docker runs them emulated.
Open the container
Clone the repository, open the folder in Visual Studio Code and run Dev Containers: Reopen in Container. The first build takes a few minutes, and the platform then sets itself up in less than a minute and prints its welcome in the terminal.
Terminal$ git clone https://github.com/weikio/try-weikioYou seeAdmin UI: http://localhost:8580 (Chrome, Edge or Firefox) Admin: admin@local, who signs in with a password CLI: signed in as the platform admin, in project sandbox and environment devtestCreate an integration and run it
weikio init hellowrites a new integration into the folderhello, and the integration logs a line every 5 seconds.weikio run hellopublishes it as version 0.1.0, deploys it to devtest and follows its log until you press Ctrl-C.Terminal$ weikio init hello $ weikio run helloYou seeCreated hello/ hello.camel.yaml timer -> log, runs every 5 s application.properties message=hello from weikio integration.yaml name hello, other fields as commented examples Next, to run it in environment devtest: weikio run ./hello Target: http://localhost:8580, project sandbox (context), environment devtest (context) integration sandbox/hello created (version 0.1.0, built in 16.2 s) deployment devtest/sandbox/hello created (follows latest) Following the log lines of sandbox/hello. Ctrl-C stops following, and the integration keeps running. 09:14:07.113 UTC INFO hello dev Exchange[ExchangePattern: InOnly, BodyType: String, Body: hello from weikio] 09:14:12.114 UTC INFO hello dev Exchange[ExchangePattern: InOnly, BodyType: String, Body: hello from weikio]Open the admin UI
weikio-dev ui-linkprints a one-time link. Open it in Chrome, Edge or Firefox, choose a password, sign in athttp://localhost:8580asadmin@localand open Integrations, thensandbox/hello.Terminal$ weikio-dev ui-linkChange it
Edit
hello/hello.camel.yaml, for example the message or the period, and publish the change as a new version. The deployment follows the latest version, so devtest runs 0.1.1 a few seconds later.Terminal$ weikio run hello --bump patchYou seeintegration sandbox/hello updated (version 0.1.1, built in 15.9 s) deployment devtest/sandbox/hello updated (follows latest)
weikio run hello, the admin UI shows sandbox/hello running in devtest on the agent dev, with its messages and log lines.These steps install a hub on one Linux server with the dev agent, the project sandbox and the environment devtest, so you can run an integration right after the install. Point two DNS names at the server first, hub.example.com and nats.example.com in the commands, and open TCP port 443 to it.
Download the release files and check them
images.envlists the release's images with their digests, andSHA256SUMSfrom the same folder checks it.Terminal$ curl -fsSLO https://weik.io/downloads/releases/2026.2.1/images.env $ curl -fsSLO https://weik.io/downloads/releases/2026.2.1/SHA256SUMS $ sha256sum -c --ignore-missing SHA256SUMSYou seeimages.env: OKWrite the stack
Create the installation's home and its master key, then run
initin the backend image. It prints the installation's operator seed once, which you keep outside the server with a copy ofmaster.key.Terminal$ install -d -o 1654 -g 1654 -m 0700 /opt/weikio $ head -c 32 /dev/urandom > /opt/weikio/master.key && chown 1654:1654 /opt/weikio/master.key && chmod 0400 /opt/weikio/master.key $ IMG=$(grep '^WEIKIO_IMAGE_BACKEND=' images.env | cut -d = -f 2-) $ docker run --rm -u 1654:1654 -v /opt/weikio:/opt/weikio -e WEIKIO_HOME=/opt/weikio -e Weikio__Keys__Dir=/opt/weikio/keys \ -e WEIKIO_MASTER_KEY_FILE=/opt/weikio/master.key -e Weikio__Nats__Urls__0=nats://nats:4222 -e WEIKIO_BACKEND_IMAGE=$IMG \ $IMG weikio-backend init --dev --public-base-url https://hub.example.com --public-leaf-url wss://nats.example.com:443 --disk-budget 15GiBStart it
The stack starts the hub, the stores and the
devagent. The log ofinitshows the first platform-admin API key and a link to set the admin's password, once. Save the key into a file calledfirst-api-keythat only you can read.Terminal$ cd /opt/weikio/deploy/compose/dev $ docker compose up -d $ docker compose logs initCheck it
doctorprints one line per check. A line whose result iswarnorfailends withfix:and the command that fixes it.Terminal$ docker compose run --rm infra weikio-backend doctorInstall the CLI and sign in
The install script checks the release's
SHA256SUMSbefore it places~/.local/bin/weikio. On Windows,irm https://weik.io/install.ps1 | iexinstalls it without administrator rights.Terminal$ curl -fsSL https://weik.io/install.sh | sh $ weikio login https://hub.example.com --project sandbox --env devtest < first-api-keyRun your first integration
The agent is online about 40 seconds after the start. When
weikio get agentslistsdevasonline, create the integration and run it.Terminal$ weikio get agents --env devtest $ weikio init hello $ weikio run ./hello --env devtestYou seeintegration sandbox/hello created (version 0.1.0, built in 16.2 s) deployment devtest/sandbox/hello created (follows latest)
Tested on Ubuntu 24.04 LTS on x86-64 with 4 vCPUs and 8 GB of memory.
Questions
Does the CLI run on macOS?
The CLI is published for Linux and Windows, and on a Mac the dev container has it ready and signed in.
How much does the dev container need?
Docker with 8 GB of memory, 4 CPUs and 20 GB of free disk. With 6 GB of memory it still runs.
Can I keep what I build in the container?
weikio init writes into your folder, which keeps the files on your machine and in your editor. weikio export writes everything else as YAML that you can apply to any installation.
Is the live demo shared with other people?
Yes, it's one installation that anyone can open as a viewer, and it's restored to a clean state every night.
Which call shows up in the live demo?
Every call through the demo's gateway is a row on the API's Requests page, with its status, its subscription and a link to its trace. The traceresponse header of your answer has the same trace ID.
Bring it to your team
When the integration runs, two pages help the next people: Weik.io for enterprises is written for your manager and your buyer, and How Weik.io is put together is written for your architect.