Skip to content
Weik.ioUniversity
Try Weik.io

How Weik.io is put together

Overview · 4:19

An integration in Weik.io is a folder of Apache Camel files. You follow one from your machine through its versions and environments to your own agents and the Weik.io installation they link to. The overview is the first step of both paths and needs no earlier video.

Download the mp4Recorded on 2026.2

What it covers

  • Integrations as folders of Camel files that weikio apply publishes as versions
  • Deployments per environment that take values from variables and secrets
  • Promotion between environments without a rebuild
  • Projects and their member roles, and grants narrowed to environments or integrations
  • Your own agents and their capabilities, and the leaf node that links them to the hub
  • The hub with its backend, the API gateway, message storage and the telemetry stores
  • Reaching Weik.io through the admin UI and the weikio CLI

Commands in this video

Terminal
$ weikio get agents
$ weikio init hello
$ weikio apply -f ./finance/erp-invoice-export --bump minor
$ weikio deploy finance/erp-invoice-export
$ weikio promote finance/erp-invoice-export --from devtest --to production
$ weikio status finance/erp-invoice-export

The commands after weikio init hello work on finance/erp-invoice-export, the example integration in the drawing. On your own installation, use the folder that weikio init wrote and its integration name in their place.

Transcript
  1. 0:02This video shows how your Weik.io installation is put together.
  2. 0:09Each integration is a folder of Apache Camel files you write.
  3. 0:13Where a value changes between environments, the route uses a placeholder.
  4. 0:18The installation fills in the ERP's address and its API key from the environment.
  5. 0:28Weik.io builds each version once into a bundle:
  6. 0:31every file of the folder and every jar it needs.
  7. 0:38weikio apply publishes the folder as a new version.
  8. 0:43Nothing runs yet, because publishing and running are separate.
  9. 0:51The agent runs devtest and production copies of its integrations.
  10. 0:55Every write to production names the environment.
  11. 0:58Deploying points devtest at the new version.
  12. 1:01Admins set variables and secrets per environment,
  13. 1:04so devtest reaches a test ERP and production reaches the real one.
  14. 1:10Promote copies the deployment to production, so nothing is built again.
  15. 1:18A project groups related integrations, which share variables, secrets and kamelets.
  16. 1:28Access is granted on a project: a role,
  17. 1:31narrowed to certain environments or integrations when needed.
  18. 1:36The command under the dialog does the same grant from a terminal.
  19. 1:43Agents run integrations, one Java process per running integration.
  20. 1:49Admins give agents capabilities like os and region, plus allowed projects.
  21. 1:54weikio get agents lists each agent with its status, capabilities and projects.
  22. 2:01Every agent that matches the environment and project runs a copy.
  23. 2:10Beside each agent runs a NATS leaf node, the site's link to Weik.io.
  24. 2:15Two flows leave the site, both outbound on port 443: the leaf node's wss link,
  25. 2:22and https carrying the logs, metrics and traces of the Camel processes and the agent.
  26. 2:29The agent and the leaf node open no inbound port at the site.
  27. 2:38Every site links to one hub, at Weik.io or in your cloud.
  28. 2:42A cloud agent in the hub's network links directly.
  29. 2:46weikio-backend serves the API and the admin UI.
  30. 2:50weikio-apim is the API gateway in front of any HTTP service.
  31. 2:57NATS, the store of record, contains every document and bundle.
  32. 3:04Every process writes logs, metrics and traces into three stores.
  33. 3:13You reach Weik.io from the Weik.io CLI or the admin UI.
  34. 3:19Home shows every environment and the integrations and APIs in production.
  35. 3:26weikio init scaffolds a new integration folder.
  36. 3:29weikio apply publishes erp-invoice-export as a version.
  37. 3:35weikio deploy runs a version on the agents.
  38. 3:39weikio promote copies that deployment to production.
  39. 3:46weikio status shows each environment's version, state and agent.
  40. 3:55Agents live at sites,
  41. 3:57on an on-premise server or as a cloud agent in the hub's network.
  42. 4:01Integrations pass messages through the installation's events.
  43. 4:05A pipeline runs the same weikio apply from Git.

Next in this track

Concept 1 · 3:07 Projects and environments Watched

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