Enterprise

Every team's agents. One harness to run them.

Roll coding agents out across the company without a hundred ways of building the same thing. gyve gives every team the same paths and patterns, and gives you the metrics, controls and audit trail to scale it.

Talk to salesRead about security
NNorthwind (sample organization)Enterprise · SSO on · 4 teams
Agent calls, last 30 days
5,916
Steps completed
23
Projects
6
Members · unlimited seats
140
Agent calls per dayagent:call · last 30 days
5002500
Oct 6Nov 4
Projects
  • Invoicer · Payments6/8saas-starter · last step by Claude Code
  • Payouts API · Payments3/4mcp-server · last step by Cursor
  • Support bot · Support5/5rag-assistant · last step by Claude API
  • Partner API · Platform2/4mcp-server · last step by Claude Code
  • Admin console · Platform4/8saas-starter · last step by Cursor
  • Docs search · Data3/5rag-assistant · last step by Claude Code

Why enterprises use gyve

Scale agents without losing the plot

One standard, every team

Every team's agents follow the same paths and the same patterns, so a project in Payments is built the way one in Platform is. No more twelve CLAUDE.md files drifting apart.

Metrics you can manage by

Agent calls a day against your plan, every project's progress step by step, and who (person or agent) finished each one.

Governed by default

Single sign-on, roles checked permission by permission, keys limited to a project, and an audit log of every agent call.

On the record

Know what every agent did, and who sent it

Each tool call lands in the audit log with the key that made it, and every finished step keeps the note its agent left. When someone asks what changed, the answer is already written down.

agent:callcomplete_step billing
agent:callsearch_catalog payments
agent:callcomplete_step first-page
agent_key:createci-agent, Invoicer only
agent:callget_kit stripe
project:step_reopenfirst-page

In the Enterprise plan

Everything in Business, and the rest

SAML single sign-onPeople sign in through your identity provider.
Custom rolesPick permissions one by one, beside the built-in roles.
Project-scoped keysAn agent's key reaches one project and nothing else.
Audit logEvery action by people and agents, as it happens.
Unlimited seats and callsBring every team and every agent they use.
Invoiced agreementsA price agreed with you, invoiced on net terms to your billing contact.
A named contactPriority support from someone who knows your rollout.
Every kit and pathThe whole catalog, reviewed against each kit's own docs.

Rolling it out

From one team to all of them

  1. 1Week 1Pilot one team

    Start a project on a path and connect the agents that team already uses.

  2. 2Week 2Turn on single sign-on

    Connect your identity provider and shape roles around how you work.

  3. 3Week 3+Bring every team

    Each new team starts on the same paths, and you watch it all from one dashboard.

Plan your rollout with usCompare plans

Your next agent session starts briefed.

Start a project on a path, connect your agent with one command, and watch it build on patterns that hold up.

claude mcp add --transport http gyve https://api.gyve.dev/v1/mcp
Start free, no cardhello@gyve.dev