Build Your Own Apps
Build custom surfaces on top of the platform APIs.
Every Runline ships with its own web app, but that shipped UI is not the only way in. When the default view is the wrong lens for how a team actually works, they can build their own surface on the same platform primitives, and it is a first-class citizen, not a workaround.
Build on the same primitives
A custom app talks to the same API the Runline's own app uses: the Items, the Workstreams, the Runner actions. An API a model cannot tool is unfinished, so everything a Runner can do, your app can do too, under the same permissions. The surface is not the value; the Fabric and the composition are. The surface just has to match how the team wants to work.
Any surface, one identity
The Console is the surface, not a specific technology: a purpose-built screen, a Slack app, an email flow, whatever fits. Whatever the surface, it authenticates through Identity (org-scoped OIDC), so a custom app inherits the same scoped access, the same gates, and the same audit as everything else. There is no ungoverned back door.
For example
- A review screen that shows only the 5% a Runner parked for a human, tuned to one team's queue.
- A Slack app that lets a manager approve an Ask gate without leaving chat.
- An email flow that routes a Runner's draft to the right person for sign-off.