THE AGENT CONTROL Customer portal
CONTROL FOR THE POST-AGI ERA

When agents outthink us,
what keeps them in bounds?

As agents become more capable than the people overseeing them, one unchecked action can move from intent to impact at machine speed. The Agent Control puts enforceable rules between agents and the tools they can use.

See how control works Keep operations in your hands
⌘Rules enforced at the tool boundaryOperator controlled
SCROLL TO EXPLORE
More capable agentsBounded authorityHuman review when requiredCustomer controlled infrastructure
INTELLIGENCE WILL SCALE. AUTHORITY MUST STAY BOUNDED.

Don't let greater capability
mean unchecked authority.

Post-AGI agents may reason beyond human speed. Their access to tools still needs limits people define and systems enforce. The Agent Control makes connected tools visible and checks policy before a call is dispatched.

01 / DISCOVER

Know what an agent can reach

Bring compatible MCP servers behind one gateway. Review the tool catalog before exposing capabilities an agent could use to affect your systems.

Explore the flow
02 / GOVERN

Make every allowed action deliberate

Allow only the clients and tools you configure. Denials take precedence, and new or changed tool definitions stay blocked until authorized.

Explore the flow
03 / REVIEW

Keep a human accountable for the boundary

Use the local console to inspect policy, review approval requests where required, and follow recorded activity in your installation.

Explore deployment
THE AGENT CAN REASON. THE GATEWAY ENFORCES THE RULES.

Thinking is powerful.
Tool access is authority.

Connect the tools your agents use, identify each client, and define what it may call. The gateway checks those rules before requests reach connected tools.

See deployment model
i

A control layer only governs calls routed through it. Restrict direct access to upstream tools in your environment too.

DESIGNED FOR YOUR ENVIRONMENT

Put the control point
inside your boundary.

Keep the gateway and operator console with your workloads, where your team can set policy, review activity, and retain operational data.

01
PRIVATE INSTALLATION

Don't hand a distant service the keys to your tools.

Run the control layer in infrastructure you manage. Keep tool credentials, policies, approval decisions, and audit records inside your environment.

Customer operated
02
OPEN INTEGRATION

Keep your agent stack. Govern its reach.

Route MCP clients through a configured gateway and apply policy at the point where agents reach tools.

MCP gateway
03
PRODUCT PORTAL

A separate place for account services.

The customer portal will handle organization access, licensing, releases, and support. It does not control private agent operations.

Visit the portal
BUILT FOR A POST-AGI WORLD

Capability can grow.
Authority stays bounded.

01

No permission by assumption

Access requires an explicit matching rule. Denials take precedence.

02

Changed tools are a new risk

New or changed tool definitions need operator authorization before use.

03

Keep the control point yours

Run the gateway and retain operational authority in infrastructure you manage.

INSTALLATION & CONFIGURATION

Get your installation
ready, step by step.

Follow the local setup, create your administrator, connect agents, and review your first tool definitions with real console screenshots.

Open installation guide
QUESTIONS, ANSWERED

What happens when
agents get more capable?

More capable agents make clear authority boundaries and accountable operation essential.

Does this replace my agent framework?

No. The Agent Control is a governance layer for tool access. Your agents, models, and frameworks remain yours.

Where does the operational console run?

The operator console belongs to the private installation and runs with the gateway in infrastructure you manage. It is separate from the customer portal.

Can it stop every action an agent takes?

It governs tool calls routed through The Agent Control. It cannot govern actions that bypass the gateway, so your environment should also restrict direct access to upstream tools.

Which tools can I connect?

The current gateway supports MCP servers over stdio and Streamable HTTP. Each installation should verify client compatibility and restrict direct access to upstream tools.

Does the portal receive prompts or tool data?

No. Operational prompts, tool inputs, credentials, and audit records stay in the customer managed installation by default. Support diagnostics should be shared explicitly and redacted.

Can I see pricing or create an account today?

Not yet. Licensing and portal onboarding are still being defined. Contact your product representative for current project information.

BE READY FOR MORE CAPABLE AGENTS

Decide what an agent
can do before it acts.

Make tool access visible, enforce explicit policy, and keep the control point in your environment.

See how control works