Status

What this deployment can and cannot do right now, stated plainly.

Database Designer’s own Postgres — sessions, canvas state, MCP activity. ready

GitLab Compliance scanning, and publishing a session as a merge request. ready

Workspaces Per-session preview pods (driver: kubernetes). ready

Preview content Published collections render the site's real content, through a read-only token scoped to this site and revoked when the workspace stops. Unpublished ones fall back to sample content. ready

How Designer is driven

There is no model key here Designer is driven from your own AI client over MCP, so inference is billed to your subscription and no model credential of yours ever reaches this deployment. The canvas is where you point at elements and approve publishing — the two things a chat client cannot do. Set the connection up under Settings.

Where preview content comes from Each workspace serves the Roving content API itself, from the collections defined in that workspace, with generated sample content — so a page can be designed before its schema is published. Sample content is held in memory, never committed, and dies with the workspace. The token that reads them is read-only and scoped to this site alone.

Designer never writes to the CMS It reads published content so a preview looks real, through a read-only token scoped to one site. It has no tool that creates or edits content, and its Roving client can do exactly two things: mint that read token and revoke it. Content and schema sync belong to the Roving MCP server.

What the preview will not do It will not invent a page so that a broken link resolves. A link with no route and no content row 404s in the canvas exactly as it would in production, and the canvas reports it — a preview that disagrees with the live site is worse than no preview.

Known limitation: who can actually sign in

Local-auth accounts cannot sign in yet Roving CMS is the OIDC provider, but its login interaction handler redirects unconditionally to the upstream SSO — there is no branch for auth_type: 'local'. Every customer and editor account authenticates by email one-time code, so sign-in completes today only for accounts on the Roving SSO domains. The fix belongs in roving-cms, in routes/oidc-interactions.ts, and it fixes this for every sibling app at once.

Deployment

Public URL: https://designer.roving.studio
Version: 4725453f
Workspace driver: kubernetes
Health: /healthz