The admin UI
Weik.io 2026.2The 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. Product page · Video
Watch: Creating integrations in the admin UI, 4:02
The video creates an integration in the admin UI's New integration dialog, saves it as a version and deploys it to devtest.
On this page
The admin UI is a web application served by the backend on the same address as the API, such as https://hub.example. You sign in with a button for each identity provider the installation has, such as Microsoft Entra ID, or with an e-mail address and a password. A person sees the projects, environments, integrations and APIs their grants cover, and nothing else.
The navigation#
The main navigation has six areas, with Settings beside them:
| Area | What it has |
|---|---|
| Home | One environment at a time: the integrations and APIs deployed there, who deployed them and when, what needs attention and the recent changes |
| Integrations | Every integration in tabs: All, Camel, Transfers, Schedules, Event integrations and Change tracking, each with its count and a red bubble for those that need attention, then Transferred files |
| APIs | APIs and Subscriptions |
| Events | The stored events of an environment, with the dead letters and the stream usage |
| Entity store | The record types integrations store and their records |
| Observability | Overview, Metrics, Traces and Logs |
| Settings | Platform (Projects, Environments, Agents, Gateways, Certificates, Installation), Access (Users, Roles, Project access, API keys, Providers, Claim mappings) and Operations (Health, Audit log, Telemetry forwarding) |
Every page has its own address, so a link to a page deep in the admin UI works when you paste it into a new tab. The browser’s Back button returns to the section you came from.
A record’s page#
An integration, an API, a project, an agent and an entity type each have a page with its sections in a list on the left. An integration’s page groups them like this:
- Integration: Overview, the sections of its kind, such as Runs for a transfer or Events for a channel, and Activity.
- Observability: Metrics, Traces and Logs.
- Deployment: Versions and Environments.
- Configuration: Source for a Camel integration or Definition for the other kinds, and Variables and secrets.
The header shows the record’s ID beside its name, with a button that copies it.
Create an integration#
New integration, on the Integrations page and in a project’s page header, opens a dialog that asks for the integration’s name, its project and its kind. It offers the seven kinds weikio init writes:
| Kind | What it does |
|---|---|
| Camel integration | Runs Camel routes you write |
| File transfer | Copies files from one place to another on a schedule |
| Schedule | Runs a command at set times |
| Event source | Brings events in from another system |
| Event channel | Holds events that integrations publish and read |
| Event subscription | Sends events from an event source to a channel |
| Change tracking | Publishes database changes as events |
The dialog also shows the weikio init command that writes the same files, such as weikio init supplier-invoices --kind mft --project finance, so you can make the next one from a terminal. Continue opens the editor with those files.
Save a version in the editor#
Nothing is stored until you save. The save builds a new version the same way weikio apply does, with the same checks, so a route Camel refuses fails with Camel’s own message. Deploy it from the Environments section, or with weikio deploy.
An integration made in the browser and one applied from Git are the same kind of record. When an apply from Git replaces files that a person saved in the admin UI, its output says whose save it replaced and when. Keep integrations in Git explains how the two work together.
What a page says when it’s empty#
A page with nothing to show says what is missing and why, or how to create the first one, with the CLI command where the page has no button for it. A page outside your grants says which access to ask for and whom to ask.