Visual composition
Triggers, data reads, reasoning steps, tool calls, and approvals as blocks. Code where you want it, none where you do not.
Platform
Studio. Build your own agents on the same guardrails.
Studio is a low-code builder for agents on top of your data and Meridian's controls. Approval steps, evaluation sets, and Registry registration are built in, not bolted on.
app.meridian.example/studio/ap-duplicate-check
Draft v7
AP duplicate check
5 blocks · autosaved 14:02
Trigger01
Invoice posted
ERP event · AP subledger
Read02
Vendor, PO, history
Data Fabric · ap:read
Reason03
Duplicate and policy check
Workspace model
Approve04
Hold if over $10,000.00
AP manager role
Act05
Release or flag
ERP via Gateway
Run evaluationPublish
What is Studio?
Meridian ships twelve agents. Your organization has hundreds of workflows. Studio lets operations, HR, and finance teams build agents for the rest without inheriting the security work.
Agents are composed from blocks: a trigger, data reads through the Data Fabric, reasoning steps on your chosen model, tool calls through the Gateway, and approval steps that route to named people. Approval steps are a first-class block. So are evaluation sets, which let a builder define expected behavior on real examples and see pass rates before publishing.
Publishing registers the agent in the Registry with an owner, permissions, and a risk tier. Versions are promoted through environments. If an evaluation regresses or a policy changes, the agent can be paused from the Registry like any other.
- Design partners published their first custom agent within two weeks of Studio access
- Approval and logging cannot be bypassed by a builder; they are enforced below the builder
- Evaluation sets re-run automatically when the workspace's model changes
- Studio agents consume credits on the same meter as Meridian agents
Capabilities
What Studio does
6 capabilities, each enforced below the agent so they apply to Meridian, partner, and Studio-built agents alike.
Approval steps as blocks
Route consequential actions to named approvers or roles. Approvals are enforced at the Gateway, so a builder cannot skip them.
Evaluation sets
Define expected behavior on real examples. See pass rates and regressions before publishing and on every model change.
Versioning and promotion
Draft, test, and production environments with promotion gates and rollback.
Templates from Meridian agents
Start from the patterns Meridian's own agents use: intake and routing, reconciliation, document review, evidence packaging.
Registered on publish
Every published agent gets a Registry record with owner, scopes, and risk tier. Nothing runs unregistered.
Specification
Studio specification
Standards, protocols, and limits as of September 2026. Your account team can confirm coverage for a specific stack.
| Item | Specification |
|---|---|
| Blocks | Trigger, data read through the Data Fabric, reasoning step on your chosen model, tool call through the Gateway, approval step |
| Approvals | First-class block routed to named approvers or roles; enforced at the Gateway, so a builder cannot skip them |
| Evaluation | Evaluation sets on real examples with pass rates and regressions; re-run automatically when the workspace model changes |
| Environments | Draft, test, and production with promotion gates and rollback |
| Code | Blocks may contain code; whole agents can be defined in code and published through the same pipeline |
| Registration | Every published agent receives a Registry record with owner, scopes, and risk tier; nothing runs unregistered |
| Metering | Studio agents consume credits on the same meter as Meridian agents |
| Plan availability | Enterprise; early access for Growth on request |
How it fits
How Studio fits the platform
One identity model, one policy layer, one log. The other components and the trust model that binds them.
Questions
Questions about Studio
Operations, HR, and finance teams with a workflow Meridian's agents do not cover, and IT teams who want those agents built on governed infrastructure rather than in a spreadsheet macro or an unmanaged script.
Yes. Data access goes through the Data Fabric, tool calls go through the Gateway, approvals are enforced there, and every published agent has a Registry record. A builder can add controls; a builder cannot remove them.
Yes. Blocks can contain code, and whole agents can be defined in code and published through the same pipeline. Developers who prefer other frameworks can connect through the Gateway instead.
Studio is included in Enterprise. Growth customers can request early access for a specific use case.
Get started
Put the first agent to work this quarter.
Start with one workflow, one approver, and one number to move. Most design partners were live in five weeks.