Designer Canvas

The Designer canvas

Your whole environment as a live diagram: what runs where, what talks to what, and what is about to change.

Every project environment has two views: Apps, the card view of each service, and the Designer, one canvas where the whole environment is a diagram. Apps sit in bands with their own add-ons, shared add-ons get their own band, AI models appear as endpoint cards, and the lines between them are the real wiring.

Switch views with the Apps / Designer toggle above the canvas. The search bar above it searches the environment: services, add-ons and their settings.

Bands

A band is the rounded frame that groups a service with its own add-ons — its database, cache, anything attached just to it. Move the band and everything inside moves with it; open a card from the band by clicking it. Shared add-ons, used by several services, sit in their own band.

Where you drag a band is remembered. New resources drop onto the grid near what they connect to, and cards snap to the dot grid when you drop them.

Connections are real wiring

Nothing on the canvas is drawn for looks. A line exists only when the underlying wiring exists:

ConnectionDrawn when
Add-on attachmentAn app has a database or other add-on attached to it.
Service to serviceAn app's variables reference another service's host — for example https://api or api-kuberoapp.
App to AI modelAn app is connected to an AI model, so its variables carry the model's inference URL.

Hover a card to spotlight its connections. A band you collapse keeps its lines: they retarget to the band and a count shows how many connections it has.

Staged changes

The canvas is also where changes are made. Adding a service or an add-on from + Service drops a ghost card on the canvas: a preview, not a deploy. Configure it, review everything in the commit sidebar, then commit to apply or remove to discard.

  1. 1

    Stage it

    Click + Service and pick a template, repository, Docker image, database, AI model or one of the add-ons. A ghost card appears on the canvas.
  2. 2

    Review it

    Click the ghost card to open its settings. The commit sidebar lists every staged change across the environment.
  3. 3

    Commit it

    Commit applies the staged changes and deploys. Remove discards them. Settings edits on existing services stage and commit the same way.

Note

Pull-request previews get their own pr-<n> phase with its own canvas. See PR previews.

Tidy Up

The Tidy up button (the sparkles, bottom left) re-runs the automatic layout for the whole canvas. It arranges the environment into role columns, reading the wiring — never names:

ColumnWhat lands there
Apps (left)Services that only call others, and standalone services.
Gateway (middle)Services other apps call: APIs, proxies such as LiteLLM, backing services.
Inference (right)AI models and the servers that serve them, each model beside the GPU machine that runs it — AI models cards with the endpoint look.

Everything flows left to right: apps call services, services front inference. A column that grows too tall wraps into a second column, so a wide canvas is used instead of one tall strip. Tidy Up is the only thing that rearranges everything — what you drag stays put until you press it again.

Reading the cards

On the cardWhat it tells you
Status lineRunning, Rolling out, Sleeping, and what a starting service is doing (downloading, loading).
Domain lineThe service's public URL; AI model cards show their endpoint URL.
Right-click menuOpen management, restart, scale, rename, delete — the actions for that resource.

AI model cards

AI models are not apps: they run on rented GPUs outside the cluster. Their cards carry an endpoint pill and their model, machine and region — and their lines to the apps that call them. See AI models.