Skip to main content
QGI Studio
Built for teams that get audited

One studio per vertical. One console for all of it.

QGI Studio is a platform, and Finance Studio is one vertical running on it. A vertical decides what its users can create, which templates they see, which tools and engines are enabled, what it costs, and the artwork it wears, all from an admin console, without a redeploy.

The admin overview showing app, tenant, UI mode, collections, tools, commands and MCP servers
Admin overview: app, tenant, UI mode, collections, tools, commands, MCP servers, and which enforcement the process is running under.
Auth · Tenants · Roles

Platform mode.

  • Supabase-backed auth, tenants and roles

    Off means single-operator local mode; on means every request resolves to a real member with a real role.

  • Login required

    Bearer auth on every API route.

  • Per-user OS isolation

    Every run executes as the requesting member's own Linux account on the fleet. Not a sandbox flag: a separate user.

  • Access list

    Signing in requires the person's email in the app's access list, in addition to their team role.

Team roles

Owner, Admin, Member.

Owner and Admin can edit every shared project. Member can edit what's shared with them. Invite by email, pick a role, done. Private tools ride only in your runs; team tools ride in everyone's.

The admin console

What you control.

Every change is recorded in the audit log. The manifest (apps/<name>/app.yaml) stays the source of truth; the console narrows what the running vertical offers.

Area What you control
Vertical File types users can create (inherit all 11 or choose), template availability and featured list, the icon/illustration art set.
Templates Curate the 34-template catalog per vertical.
Users · Subscriptions Members, tiers, invitations.
Pricing Per-tier overrides over global defaults; Stripe price ids checkout sells.
Engines Which runners are enabled and their live model catalogs.
Executors · Host toolchain · Environment Where runs execute and what is installed there.
Telemetry · Observability · Runs · Fleet Every run, every process, every host, in one place.
Project history with a run id on every version
Project history: a run id on every version.
Governance in the product, not beside it

Auditable by default.

  • Governed Agentic Workflows with approval gates and a per-run audit trail.
  • Project history with a run id on every version.
  • Per-project tool narrowing. The agent only sees what you allow.
  • Deterministic flows for anything that leaves the building.
Your own vertical

Finance Studio is the first. Tell us which domain you need next.

The same platform can wear a different toolset, template catalog, art set and price list for another domain.

One studio per vertical. One console for all of it.