Bespoke connection work
Every new agent, model, tool, or application introduces its own authentication, routing, and observability path. Identity, authority, budget, and evidence end up scattered across systems that don’t share a record.
CGP · Connectivity Gateway Protocol
Today’s internet was built for web pages and email, at human pace. CGP Gateway is the bridge into the Internet of AI: a multitenant SaaS and API that converts slow, connection-heavy TCP traffic into encrypted UDP datagrams moving at machine speed. Your team still sets who may call what, under which policy, and at what spend limit, and every request comes back with its result and a verifiable receipt.
Customer and outcome
CTOs, VPs of Platform Engineering, and Heads of AI Infrastructure bring it in. Platform engineers and integration architects use it every day.
They use CGP Gateway to replace one-off integration paths with a repeatable connection workflow: register endpoints, define tenant-scoped policies and spend limits, route synchronous or asynchronous work, and inspect transaction records and metadata from one control plane.
Every new agent, model, tool, or application introduces its own authentication, routing, and observability path. Identity, authority, budget, and evidence end up scattered across systems that don’t share a record.
Each transaction is signed and carries its principal, authority, spend limit, task, and policy. The result comes back with evidence your auditors can check.
Teams access a web control plane, HTTPS API, sandbox workspace, and SDK. Implementation support is available but never required.
The private beta is invite-only and single-region, run through a focused design-partner program. Single-tenant deployment and secondary-region recovery are on the roadmap.
Product visual
The CGP control plane shows endpoints, policies, routes, and live transaction activity in one workspace.
Operators can trace a routing decision back to its receipt or check current latency without leaving the dashboard.
Northstar workspace · West US 2 · Last 24 hours
| Transaction | Route | Policy | Overhead | Status |
|---|---|---|---|---|
| cgp_82f0 | claims → research | balanced-v3 | 21 ms | Receipted |
| cgp_82ef | ops → planner | strict-v2 | 26 ms | Receipted |
| cgp_82ee | support → analyst | balanced-v3 | 19 ms | Receipted |
End-to-end workflow
Three steps take a new endpoint from registration to its first receipt.
An engineer registers an application, agent, model endpoint, or tool and assigns it to a tenant workspace. From there, protocol adapters for REST, gRPC, MCP, and A2A normalize each request into one envelope.
The team sets allowed routes, authentication requirements, and spend limits. Payload handling, timeouts, and the evidence level each transaction must carry round out the policy.
The gateway selects the authorized path, records the policy decision, and returns the result with evidence operators can inspect and export.
Results at a glance
All figures are internal measurements; the method is documented on the Results page.
Active design-partner programs.
Releases in the product changelog.
Continuous operation on the Azure stack.
2.16 million messages through the gateway path.
Azure architecture
Every Azure service here does a specific job. The gateway runtime itself is built on HyperCycle technology. Beyond the gateway, authorized requests reach agents and services across the Internet of AI. The Vision page tells that story.
Front Door · API Management · Container Apps
Private beta
IOAI Gateway, Inc. is building CGP Gateway for platform teams that refuse to trade governance for speed.
Request private-beta access