CGP Gateway
Software developed and owned by IOAI Gateway, Inc., built on HyperCycle technology.
Core productProduct · CGP Gateway
One high-speed, governed path into the Internet of AI.
CGP Gateway implements the Connectivity Gateway Protocol (CGP) as a private-beta B2B connectivity SaaS and API. The protocol converts connection-heavy TCP traffic into encrypted UDP datagrams, so cross-system work runs at machine speed. AI infrastructure teams register endpoints, apply policies and spend limits, route work between applications and agentic systems, and review each transaction’s receipt and metadata.
Product identity
What it is, who buys it, what stage it’s at, and how it’s delivered.
One product, sold as a multitenant SaaS and API, now in private beta.
AI infrastructure teams
Enterprise organizations connecting applications, APIs, agents, models, and tools.
BuyerPrivate beta
Invite-only availability with two active workspaces and a focused design-partner program.
CurrentMultitenant SaaS + API
Azure-hosted control plane, HTTPS API, browser dashboard, and SDK.
Delivery modelJob to be done
Replace one-off integrations with a repeatable connection workflow.
CGP Gateway speeds up, governs, and observes the traffic that moves between systems.
It does not replace application logic, AI models, or downstream services.
Submit a request
An engineer registers the calling system and its allowed destination, then submits the request synchronously or as a durable asynchronous job. The gateway compiles it into a signed transaction record that binds principal, authority, spend limit, and task.
Identity, policy, and route
The gateway authenticates the caller and resolves the tenant, then checks authority and budget before evaluating the connection policy and selecting an authorized path.
Result plus receipt
The caller receives the downstream result with a verifiable receipt, while operators see timing, route, policy decisions, and evidence pointers in one workspace.
The transaction record
One signed record holds the whole transaction.
CGP Gateway keeps every cross-system transaction in one sealed, signed record, rather than scattering the pieces across logs, invoices, and dashboards.
The record references the protocols a team already uses. It does not replace MCP messages, A2A tasks, or payment payloads; it ties them into one verifiable record that can be reconciled and handed off.
Principal and authority
The accountable principal, the requesting agent, the scope it was granted, and whether the action was delegated by a person or taken autonomously.
Task and budget
The objective, input references, completion conditions, and the spend ceiling the transaction must stay within.
Evidence and result
Execution timestamps, output hashes, evidence pointers, and acceptance state, minimized by default so proof travels without raw data.
Settlement and lineage
The settlement reference, parent and downstream task links, and disclosure rules that govern how the evidence may be used.
Capability boundary
What’s live, what’s planned, and what we don’t offer.
The protocol gives the gateway five jobs: Connect, Translate, Control, Monetize, and Migrate. The private beta delivers the first three; Monetize and Migrate are on the roadmap.
Endpoint registration
Register HTTPS endpoints, classify each system, assign a tenant, and verify a health check.
CurrentProtocol adapters
Normalize REST, gRPC, MCP, and A2A requests into one shared request format. Each new protocol needs one new adapter.
CurrentConnection rules and budgets
Configure allowed routes, authentication, spend limits, timeout behavior, payload size limits, and the evidence level each transaction must carry.
CurrentSync and async routing
Use a direct path for immediate responses or a durable queue for jobs and event fan-out.
CurrentTransaction observability
Inspect transactions, routes, policy decisions, timing, and failures, review tenant-scoped audit events, and export receipts on demand.
CurrentSupply-side gateway
A supply-side configuration of the same gateway that turns a team’s own services into agent-payable destinations, with service fees settled peer to peer.
PlannedNative-path execution
Move recurring, high-frequency work toward native execution on the destination network where measured economics justify it.
PlannedPremium account isolation
A dedicated data account and runtime boundary for customers requiring stronger workload isolation.
PlannedSecondary-region recovery
Warm recovery components, rehearsed failover, and a documented regional recovery target.
PlannedSelf-hosted runtime
Customer-operated CGP runtime packages are not part of the private beta.
Not offeredHolding customer funds
Value stays in accounts the customer controls. The gateway enforces budget policy and records settlement references, but never takes custody of customer funds.
Not offeredAutonomous business approval
The gateway does not make legal, financial, safety-critical, or policy decisions for customers.
Not offeredBusiness model
The software is the product. Services remain ancillary.
Customers subscribe to the control plane and API. Pricing scales with workspaces, registered endpoints, and routed transaction volume. Access is sold as software, not as an asset.
A standard onboarding package helps teams configure their first routes. Custom development is not required.
Platform subscription
Tenant workspace, dashboard, API, policies, transaction metadata and receipts, sandbox, and support entitlement.
Metered usage
Usage pricing follows routed transaction volume and data-processing bands with visible cost controls.
Standard onboarding
Architecture review, initial endpoint configuration, policy workshop, and operational handoff.
Open-ended consulting
IOAI Gateway, Inc. is a software product company, not an agency, development shop, or staff-augmentation provider.
Product results
See benchmarks, releases, and design-partner outcomes.
The Results page includes performance methodology, release history, a design-partner workflow study, and an API quickstart.
Open results