The admin UI
Weik.io 2026.2Sign in to the admin UI at your Weik.io installation's address and work with the same records the CLI does. Product page · Video
Watch: Creating integrations in the admin UI, 4:04
The video creates an integration in the admin UI's New integration dialog and deploys the saved version to devtest.
This part of the video couldn't be loaded.
On this page
The admin UI is at the same address as the API, such as https://hub.example. Sign in with the button of one of the installation’s identity providers, such as Microsoft Entra ID, or with an e-mail address and a password.
After you sign in, you see only the records your grants cover.
The navigation#
Open an area of the main navigation, or Settings beside it:
| Area | What you go there for |
|---|---|
| Home | See what runs in one environment and what needs attention there |
| Integrations | Find an integration of any kind, or a file your transfers moved |
| APIs | Work with your APIs and their subscriptions. The docs call this area API management. |
| Events | Read an environment’s stored events and dead letters |
| Entity store | Look up the records your integrations store |
| Observability | Search the logs, metrics and traces of what runs |
| Settings | Administer the platform and its access, and check its health |




Create an integration#
To create an integration, click New integration on the Integrations page or in a project’s page header. Enter the integration’s name and project in the dialog, and pick one of the kinds that 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 | Contains events that integrations publish and read |
| Event subscription | Sends events from an event source to a channel |
| Change tracking | Publishes database changes as events |
Click Continue to open the editor with the new integration’s files. To make the next one from a terminal instead, run the weikio init command the dialog shows, such as weikio init supplier-invoices --kind mft --project finance, which writes the same files.
Save a version in the editor#
The editor stores nothing until you save. Saving builds a new version with the same checks as weikio apply. When Camel finds an error in a route, the save fails with Camel’s message. Deploy the version from the Environments section or with weikio deploy.
An integration made in the browser is the same as one applied from Git. 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.
A notice on every page#
A platform administrator can show a one-line notice, such as a planned service break, at the top of every page of the admin UI. The sign-in page and the other signed-out pages show it too, so anyone who reaches the installation from its allowed networks can read it.
To set the notice, click Set notice in the Notice panel on Settings › Platform › Installation, or run weikio notice set:
$ weikio notice set "Planned service break on 20 November, 08:00 to 10:00 UTC" --level warn --until 2026-11-20T10:00ZTarget: https://hub.example
notice created (revision 270)The notice is one line of at most 300 characters, in blue for Info and in yellow for Warning. Set the From and Until times to choose when it shows. Without them, it shows from now until you remove it. To remove it, pick Remove notice in the panel or run weikio notice delete. Platform administration lists the command’s flags.
Pages outside your grants#
When your grants don’t cover a page, the admin UI shows which access to ask for and whom to ask.