Glossary
Weik.io 2026.2The words of Weik.io in one or two plain sentences each, the same words the admin UI, the CLI and Weik.io University use.
| Term | What it means |
|---|---|
| Admin UI | The web application the hub serves on its own address, where you see and change everything you’re allowed to. It has the same rights model as the CLI. |
| Agent | The program at a site that runs integrations. It starts one Java process for each running integration and reports what runs to the hub. |
| API | A name and a path prefix that callers know, such as /. Its versions hold the definitions. |
| API deployment | One API version served in one environment on one or more gateways. |
| API gateway | The part of the platform that serves APIs to their callers, also called APIM. Each running copy of it is an APIM instance. |
| API key | The credential of the CLI and of pipelines, shown once when it’s created. A key carries grants, which can’t exceed what its owner was given. |
| Apache Camel | The integration framework whose routes Weik.io runs. An integration’s files are Camel files, written as you would write them for Camel JBang. |
| Audit log | The record of every change, every secret reveal and every sign-in to break-glass accounts, kept for 400 days and forwardable to your SIEM. |
| Break-glass account | An emergency account that can sign in only while an operator has opened a break-glass window on a hub server. |
| Camel line | A Camel version the platform can build integrations on, such as 4.22.1. Two lines can run side by side. |
| Capability | A label of an agent, such as os: linux, region: fi or environment: production. An integration’s requirements are matched against capabilities. |
| Change tracking | An integration that publishes the changes of database tables as events, with Debezium. |
| Channel | A named stream of events in a project. Integrations publish events to it and read events from it, and each environment stores the events for 30 days by default. |
| CI and pipeline | A CI system, such as GitHub Actions, runs a pipeline on each change to a repository. A Weik.io pipeline runs the weikio CLI to apply the change. |
| CLI | The weikio command-line tool, one program file that you copy into a folder on your PATH. |
| Context | A server address with an API key and a default project and environment, saved on your machine by weikio login. |
| Dead letter | An event an integration couldn’t handle after its last retry, kept with the integration it failed in and the reason. |
| Deployment | One version of one integration in one environment. It runs on every agent that matches it. |
| Devtest | The development and test environment that a new installation’s trial setup creates. |
| Document | One record the hub stores, such as an integration, a deployment or a project, with a kind. Each can be written as a YAML file and applied with weikio apply. |
| Draining | An agent that gets no new deployments while it keeps running what it has. |
| Entity store | A store of the latest value of each entity, such as an invoice by its ID, kept per type, project and environment. |
| Environment | A stage shared by the whole installation, such as devtest or production. |
| Event source | An integration that brings events in from another system, such as files arriving in an S3 bucket. |
| Event subscription | An integration that sends the events of an event source to a channel, filtered and changed on the way. |
| File transfer | An integration that moves or copies files on a schedule between two places rclone can reach, such as an SFTP server and an Azure storage account. |
| Gateway | An entrance of one environment for API callers: its hostnames, the networks that may call it, its client certificate rules and its rate limits. |
| Grant | A role in one project for some or all environments, and optionally for named integrations and APIs only. People, API keys and claim mappings hold grants. |
| Health | The admin UI page that shows every part of the platform, the backend nodes, the APIM instances, the stores and the agents, with their status. |
| Hub | The central server, or three or five servers for high availability. It runs the admin UI, the API, the message server, the API gateway and the stores for logs, metrics and traces. |
| Integration | A folder of Camel files, or a generated kind such as a file transfer. Its full name is project/, such as sandbox/. |
| Kamelet | A reusable Camel route snippet with parameters, from Camel’s catalog, the platform or a project. |
| Leaf node | The site’s small relay of the message server. It has the site’s one outbound link to the hub, so a site needs no inbound port. |
| Master key and operator seed | The two keys the owner of a hub keeps outside the hub server. The master key seals every stored secret, and the operator seed is the root key the message server’s credentials are signed with. You need both to restore the hub from a backup. |
| Message server | NATS, which carries what the hub and the agents say to each other and stores the hub’s records and events. |
| Pinned | A deployment that names one exact version, so a new publish doesn’t change what runs. Production deployments are pinned. |
| Platform administrator | A user or API key with the right to change the installation itself: projects, environments, agents, users and settings. |
| Problem | Something that needs attention now, such as a failing integration or an agent that is offline. Each kind has its page under Problems. |
| Project | A group of integrations and APIs and the people allowed to work on them. |
| Promote | Copying the version that runs in one environment to the next, for example from devtest to production, without building it again. |
| Reader | An integration’s read of a channel, with how far it has come with the channel’s events. |
| Role | A set of verbs, such as viewer, editor, deployer or admin. |
| Schedule | An integration that runs a command on an agent at set times. |
| Secret | A value such as a password, stored encrypted, set per environment and never listed with its value. |
| Site | A place where integrations run, a server with an agent and a leaf node, in your network, in your cloud or beside the hub. |
| Site bundle | The files weikio agent enrol writes for a new agent, with its credentials and its setup script. It’s used once, on the site. |
| Standby hub | A second host, away from the main hub, that keeps the main hub’s newest backup restored and ready to take over. When it’s activated, DNS moves the hub’s names to it and the sites link to it. |
| Subscription | A caller’s access to APIs on one gateway, with an API key, a token, a client certificate or another credential type, and an optional rate limit. |
| Telemetry | Logs, metrics and traces together. A trace is the path one message took through a route’s steps. |
| Telemetry forwarding | Sending the installation’s logs, metrics, traces and audit records to your own systems, such as Splunk, Azure Monitor or any OpenTelemetry receiver. |
| Variable | A configuration value that routes read as a Camel property, such as {{erp-, with a default and an override per environment. |
| Version | One publish of an integration’s folder. A version never changes, and each publish with changed files adds a new one. |
| Weik.io Cloud | The managed service where you create a workspace, a Weik.io installation run by the Weik.io team, along with services such as SFTP servers and MQTT brokers. |