Skip to content
Weik.ioUniversity
Try Weik.io

What runs where

Concept 2 · 3:41

Each part of Weik.io has its place, from the weikio CLI and the admin UI on your machine to the agents at each site. The hub places a deployment on every agent that matches its requirements.

Download the mp4Recorded on 2026.2

What it covers

  • The weikio CLI on your machine, the admin UI in a browser, and a hub that runs no integrations
  • Sites with an agent and a leaf node that connects outward to the hub
  • Agent capabilities and allowed projects, set in the admin UI under Settings › Agents
  • Placement of sandbox/hello by the requirements in integration.yaml
  • One copy per matching agent, one at each site
  • A refused deployment when no online agent meets a requirement

Commands in this video

This video explains with drawings and types no commands.

Transcript
  1. 0:01This video shows where every part of Weik.io runs.
  2. 0:09The Weik.io CLI on your machine talks to your Weik.io installation.
  3. 0:14You open the admin UI in a browser on that machine.
  4. 0:17The hub decides where each deployment runs, but runs no integrations itself.
  5. 0:23The hub's machine also runs agent dev, marked environment devtest.
  6. 0:32Integrations run on these sites, on their agents.
  7. 0:39Site fi-01 is one host with an agent and a leaf node.
  8. 0:44The leaf node opens a link outward to the published address, the hub's public name.
  9. 0:49Nothing connects into the site.
  10. 0:52The agent here is agent fi-01, online.
  11. 0:57The agent starts one Java process for every integration it runs.
  12. 1:04An administrator writes capabilities on an agent as key and value pairs.
  13. 1:09Agent fi-01 carries os linux, region fi and environment production.
  14. 1:16When an agent connects, it reports its operating system and architecture,
  15. 1:22but those reports never become capabilities.
  16. 1:25The environment is a capability like the others.
  17. 1:28It sets which environment's deployments this agent takes.
  18. 1:34The administrator also writes which projects the agent may run.
  19. 1:39Agent fi-01 may run the projects sandbox and finance.
  20. 1:44You set capabilities and projects in the admin UI, under Settings, Agents.
  21. 1:50A deployment from any other project never runs on this agent.
  22. 1:59The integration sandbox/hello requires os linux in integration.yaml.
  23. 2:06A deployment adds its environment, so environment production joins that list.
  24. 2:12Checking every online agent against that list is placement.
  25. 2:15Agent dev carries environment devtest, so production deployments never land on it.
  26. 2:23Agent fi-01 matches, so sandbox/hello runs there as a Java process.
  27. 2:35Agent fi-02 at site fi-02 carries the same capabilities and the same projects.
  28. 2:42It matches the list too, so sandbox/hello now runs in two copies, one per site.
  29. 2:53Now integration.yaml also requires region se.
  30. 2:58No online agent carries region se, so the hub turns the deployment down.
  31. 3:03The deployment isn't stored, so no copy starts.
  32. 3:07The refusal names the requirements no online agent meets.
  33. 3:11An administrator writes those capabilities on an agent.
  34. 3:19Every site adds an agent and a leaf node to the installation.
  35. 3:23Capabilities and project lists decide which deployments an agent takes.
  36. 3:28The hub checks a deployment's requirements with placement,
  37. 3:31so every agent that matches runs a copy.

Next in this track

Concept 3 · 3:05 Which part do I need? Watched