Studio overview

Studio is an independent agent factory and hosted runtime. It helps teams build, preview, obtain bounded artifact certification, deploy, operate, and support tenant-owned hosted agents through a guided product workflow, and it remains usable without Meridian.

What this covers

Studio evaluates membership, roles, entitlements, credits, capacity, and runtime state at its server boundary. The initial catalog is tenant private. Studio does not expose a supported public customer API in version 1.0.

The build experience allows creators to start from a supported template or natural-language assistance, iterate on proposed changes, preview agents within the tenant boundary, and proceed through certification and deployment. Connector accounts are bound within Studio's authorization and metering boundaries so the agent can be evaluated in its tenant context.

How it works

Deployment requires the applicable certification, entitlement, capacity, and tenant checks. Completing a build stage or preview does not bypass those gates. A governance-ready manifest is source evidence for later reconciliation; it is not a Meridian Agent Passport or coverage certificate.

Limits

Where certification is claimed, preserve the separately bounded Anchor artifact-certification envelope for the exact artifact and bill of materials. Artifact certification does not authorize deployment, prove action-path enforcement, or expand to the hosted runtime. Meridian independently owns workforce passports, authority, and coverage reconciliation.

Use Studio when you need a structured path from an agent idea to a tenant-owned hosted deployment. Begin with the quickstart, then follow the complete build and deployment workflow.

Next steps

Start with the quickstart, then follow the complete build and deployment workflow after reviewing the tenant and certification boundaries.