Start
Weik.io 2026.2Learn what Weik.io is and the words it uses, then run your first integration, from the dev container to the admin UI.
On this page
Start here when Weik.io is new to you. The first two pages explain what Weik.io manages and the words the docs use for its parts. The rest take you through the dev container that runs the whole platform on your machine, your first integration from an empty folder to a running process, the weikio CLI, the admin UI and the YAML files you keep in Git.
If you already run an installation, go straight to Your first integration. If you want to install a hub of your own first, Install a hub on one server is in the Operate group.
Pages#
What is Weik.io Weik.io manages Apache Camel integrations, file transfers, APIs and events from Git and runs them wherever you install an agent.Concepts Projects, environments, integrations, versions, deployments, variables and secrets, and the hub, sites and agents they run on.Try Weik.io on your machine The Try Weik.io dev container runs the whole platform on your machine, with the
weikio CLI signed in to project sandbox and environment devtest.Your first integration Three commands take an integration from an empty folder to a running process on devtest, weikio login, weikio init and weikio run.Install the CLI The weikio CLI is one native binary for Linux and Windows on x64, and every command it has is a call on the platform's API.The admin UI The admin UI is served by the backend at the installation's own address, and it creates, edits, deploys and watches the same records the CLI does.How the YAML files look Every record you write is a YAML document with apiVersion, kind, metadata and spec, kept in a project folder in Git.