Median gateway overhead.
Results · Performance · Resources
What the private beta has measured so far.
Benchmarks, release history, design-partner results, and an API walkthrough from the private beta.
Results ledger
Every claim traces to an artifact.
Five artifacts from the private beta, each with its date, source, and method.
| Artifact | Date and owner | Source or method | Boundary |
|---|---|---|---|
| E-01 · Product tour workflow | July 21, 2026 · Product Lead | product-tour.html; guided operator workflow | Shows the experience from request intake through gateway trace review. |
| E-02 · Gateway benchmark | July 18, 2026 · Performance Owner | 30-minute load run; method detailed below | Gateway overhead only; excludes downstream model latency. |
| E-03 · Private-beta release record | April to July 2026 · Engineering Owner | Fourteen versioned releases; five samples below | Versioned release history with owner and date. |
| E-04 · Design-partner discovery set | June 30, 2026 · Commercial Owner | Three partner briefs and six controlled integration exercises | Tracks integration patterns, outcomes, and follow-up decisions. |
| E-05 · Trust-control matrix | July 15, 2026 · Security Owner | Control descriptions on the Trust page | Documents current vs. planned controls; no third-party audit claim. |
Benchmark
The benchmark, run under a fixed method.
These are internal measurements taken under the fixed conditions below. An independent benchmark is planned; until then we publish no comparisons with other systems.
p95 gateway overhead.
p99 gateway overhead.
Successful routing rate.
450,000 requests
A 30-minute run at a constant 250 requests per second with a 4 KB request payload.
One Azure region
Four warm Container Apps replicas, fixed configuration, and a controlled test destination.
Gateway work counted
Timing includes authentication, tenant resolution, transaction compilation, policy evaluation, route selection, and receipt metadata.
Downstream work excluded
Timing excludes model inference, internet transit beyond the gateway, cold starts, retries, and asynchronous routes.
Design-partner outcome
Measured results at a design partner.
Northstar Benefits Lab participated as a private-beta design partner. The summary below shows where the team started, what changed, and how it was measured.
Nine developer-days
The team estimated nine developer-days to connect three internal applications to two agent endpoints using six custom paths.
Six controlled exercises
Engineers registered endpoints, applied two tenant policies, and routed both synchronous and queued work through CGP Gateway.
2.5 developer-days
Equivalent setup measured at 2.5 developer-days, a 72% reduction calculated from the documented baseline.
Partner workspace
The engagement covered workflow discovery, integration sequencing, route configuration, and operator review.
Release history
Fourteen releases, April to July 2026.
Five representative entries from the private-beta changelog appear below.
| Version and date | Summary | Notes |
|---|---|---|
| v0.8.0 · July 18, 2026 | Tenant-scoped receipt export and configurable evidence retention. | Release notes and deployment record on file. |
| v0.7.3 · July 7, 2026 | Dead-letter inspection and asynchronous retry controls. | Queue tests and runbook updates included. |
| v0.7.0 · June 24, 2026 | Policy templates for synchronous and durable routes. | Versioned policy schema and acceptance tests. |
| v0.6.2 · May 29, 2026 | Endpoint health checks and transaction search filters. | UI capture and known limitations documented. |
| v0.5.0 · April 18, 2026 | First private-beta workspace and API surface. | Initial control plane and evaluate API. |
API quickstart
The API in three steps.
From endpoint registration to a returned receipt reference, using the public API.
Register two endpoints
Create endpoint IDs claims-app and research-agent inside the tenant workspace northstar-sbx.
Apply a route policy
Assign policy balanced-v3 with an allowed destination, authentication requirement, spend ceiling, timeout, and evidence profile.
Submit a request
Submit the request to the versioned evaluate API. It compiles the request into a signed transaction and returns the result with a receipt reference. Private-beta hosts and credentials are issued during onboarding.
| Field | Request value | Response value |
|---|---|---|
| Tenant and source | northstar-sbx · claims-app | Tenant resolved · authorized |
| Destination and policy | research-agent · balanced-v3 | Route authorized · within spend ceiling |
| Transaction reference | Client request ID | Transaction ID · status · receipt reference |
| Overhead | Not supplied by caller | Gateway timing in receipt metadata |
Go deeper
Tour the product or review the architecture.
See the connection workflow end to end, or map each Azure service to its product job.
Product tour Technology