zograph.Request a walkthrough

Every agent action, governed. Every decision, on the record.

Zograph is an agent platform with governance in the execution path. Build and operate specialist agents while keeping your options for models and deployment, with a clear record of consequential actions and the rules behind them.

Not ready to talk? Join the waitlist.

Builder Layer

Conversational and background agents from configuration: a prompt, a model allowlist, and plugins. Versioned draft to publish.

Read more →

Compose

Bring your knowledge, tools and skills together.

Govern

Control, observe and prove every action.

Run

Keep your options for models and deployment.

Built for trust

Agent capability with organizational control.

Build

Compose the agent your work needs.

Define its instructions. Attach your knowledge, MCP servers, plugins and skills. Choose its capabilities and the model that powers it.

Request a walkthrough

Attach your resources

Knowledge

Give the agent access to your content.

Inventory procedures245 pages · Updated 2 days agoMore

MCP Servers

Connect to your systems through MCP.

  • Inventory SystemStock levels, orders, locationsconnected
  • ERPProducts, suppliers, purchase ordersconnected
  • Service DeskIncidents, changes, approvalsconnected

Plugins & Skills

Add reusable skills and tool packages.

  • Data AnalysisTables, charts, insightsconnected
  • Document GenerationWord, PDF, structured outputconnected
  • Custom SkillsYour organization’s packagesAdd

Your chosen model

Use the model that fits your needs.

  • Claude
  • OpenAI
  • Mistral
  • More models

Agent

Inventory planning agent

Helps planners resolve stock exceptions.

Instructions

You work with our inventory data to identify and investigate stock exceptions, propose actions, and prepare a briefing for the planning team.

  • Knowledge
  • MCP Servers
  • Plugins & Skills
  • Add

Conversational and background agents.

Enable its capabilities

Task Planning

Let the agent plan and manage complex work.

  1. 1Analyze stock exceptions
  2. 2Investigate root causes
  3. 3Propose resolution options
  4. 4Prepare briefing

Artifacts

Let the agent create and iteratively refine documents.

Stock exception memo

DOC

A structured briefing including key findings, impacted SKUs, root causes and recommended actions.

Builder / 01

02 / Evaluation

Test behavior.
Before release.

Run the scenarios that matter to your business. Inspect the response and evaluation results.

Example evaluation

Scenario

Test scenario

Stock exception briefing

Investigate the exception and prepare a briefing using the connected inventory data.

Agent response

Stock exception memo

The stock position, supporting evidence and questions for the planning team.

Evaluation checks

  • passRequired sections
  • passSources included
  • failUncertainty flagged

Refine the agent. Run the scenarios again.

03 / Extensibility

Your logic.
In the lifecycle.

Extend Zograph with synchronous HTTP hooks. Connect your systems through event subscriptions.

Synchronous hooks

Call your service and use its response.

Zograph lifecycle
HTTP requestResponse
Your service

Event subscriptions

Let your systems react to platform events.

Zograph
Platform event
Your system

Your services, connected to the platform lifecycle.

Evaluate + Extend / 02

Govern

See the work behind the result.

Inspect conversations and background runs, from individual tool calls to their sources and artifacts. Understand execution, model usage and time spent waiting.

Inventory Planning Assistant

Stock exception SR-3184 · Example conversation

ConversationBackground run

Recorded actions

Execution

Approval wait

Continue

  1. Read the exceptionget_exception
  2. Read stock levelsget_stock_by_dc
  3. Read the forecastget_forecast
  4. Read open purchase ordersget_open_purchase_orders
  5. Create purchase ordercreate_purchase_order
    Waiting for approval
  6. Edit exception memoartifacts_str_replace

Illustrative execution · not a time scale

Associated context

Task planInventory proceduresException memo

Selected action

Create purchase order

Completed

Recorded result

Purchase order created.

Inventory System · MCP tool

Approval wait35.3 s
Tool execution154 ms
Inspect recorded input and result

Permission and execution are separate facts.

Execution

Outcomes, duration and approval waits.

Usage

Models, tokens and estimated cost.

Context

Plans, sources and created artifacts.

Observability / 04

Set the rules. Control the action.

Set defaults across your agent’s tools, refine permissions by source or action, and choose when approval is required.

Configure the boundaries

Agent defaults
Source rules
Individual tools

Broad defaults. Inherited settings. Deliberate exceptions.

  1. Read inventoryInventory System
    Allowed
    Administrator rule
  2. Update task planTask Planning
    Allowed
    Plugin default
  3. Edit exception memoArtifacts
    Allowed
    User standing grant
  4. Create purchase orderInventory System
    Ask administrator
    Explicit tool rule
  5. Change safety stockInventory System
    Denied
    Administrator rule

Governed action

Create purchase order

Waiting for administrator approval

Effective permission

Ask an administrator each time.

Initiated by

Requesting user

Execution

Held pending approval.
ApproveDeny

The requested call has not run.

Rules establish permission.

Across plugins, provider tools and MCP servers.

Grants carry user authority.

Automatic allows still have a deciding source.

Your logic can participate.

Connect decision logic through an extension.

Access & Governance / 05

Every decision, with its reasons.

Keep the history of changes, tool permissions, attempted actions and approvals. Trace an action back to the rule, authority and turn behind it.

Connected records

  1. Changes

    History

    Who changed or published what.

  2. Tool permissions

    Admissions

    What was allowed, denied or required approval.

  3. Invocations

    What was attempted and how it ended.

  4. Approvals

    Who decided, and how the request was resolved.

Selected record · Invocation

Related turn

Create purchase order

Allowed following administrator approval.

Permission · AllowedExecution · Completed

Authority

Administrator approval required each time.

Explicit rule for this tool.

Approval

Approved by an administrator.

Decision recorded before tool execution.

Execution

35.3sapproval wait154msexecution

Tool outcome recorded separately from permission.

Related context

Inventory Planning Assistant

Initiated by the requesting user.

Inspect the associated turn

Automatic decisions, too

Edit exception memo

User standing grantAllowed

Not only the exceptions. The automatic allows, too.

Records that support review and accountability.

Audit & Compliance / 06

Run

Choose your models. Keep your options.

Use Zograph’s model access, or bring your own provider credentials. Choose from supported models and compatible endpoints, with control over the connections behind your agents.

Zograph-managed access

Recommended

Use model access supplied by Zograph.
No provider API key required from you.

Your own provider credentials

Connect your own provider account.
Use your existing API keys and credentials.

One platform

zograph.

Your agents, in control.

Inventory Planning Assistant

  • Agent configuration
  • Governance
  • Execution records

Your platform stays the starting point.

Evaluate behavior when changing models.

Configured model connections

Direct provider

Selected

Configured model · Provider connection

Access: Zograph-managed

Cloud AI connection

Configured model · Compatible endpoint

Access: Your provider credentials

Alternative

Your inference endpoint

Self-hosted or private inference

Access: Your provider credentials

Alternative

Configured choices, not a failover sequence.

Model choice

Choose from the models your connections support.

Zograph access or your own keys

Start with Zograph-managed access, or connect your own provider account.

Compatible endpoints

Connect beyond a fixed catalog through supported interfaces.

Redundancy / 07

Your platform. Your environment.

Choose where Zograph runs and how it connects to your models and systems. Keep deployment, regional choices and external dependencies explicit.

Platform deployment

Zograph-managed

Region

Your selected region

Illustrative deployment

Platform environment

Selected region
zograph.

Platform

Your governed agent platform.

  • Agents
  • Governance
  • Execution records

Connected services

Inference endpoint

Your configured model connection.
Placement depends on configuration.

Business systems

Inventory, knowledge and tools.

In this example, the model and business services sit outside the deployment.

Deployment choice

Where the platform is operated.

Regional choice

Where the selected deployment is located.

Explicit connections

Which models and systems the platform depends on.

Sovereignty / 08

Walk us through
your case.

Forty minutes with the people who built Zograph. Start with the workflow you want to govern first.

Not ready to talk? Join the waitlist.