Approve the exact change.
Review the proposed policy and its alternatives. A different authorized person approves it. A separate apply checks the approved plan, writes it once and records the readback.
THE ARC1 PLATFORM
From approved policy
to observed configuration.
Your gateways carry the requests. ARC1 connects the change your team approved to the configuration each supported gateway reports back, with a record you can verify offline.
Current standingVerified live on Kong in a lab;
Azure API Management contract-tested.
Azure API Management contract-tested.
01 / THE ARCHITECTURE
Policy above the path.
Traffic on your infrastructure.
ARC1 uses gateway management APIs within its registered ownership scope. Your gateway’s own control plane remains in place.
ARC1 · POLICY & DECISION RECORDS
A reviewed change, with its evidence.
- 01Propose
- 02Second-person approval
- 03Apply
- 04Read back
Signed audit receipts accompany recorded transitions and can be verified offline.
Approved configurationSeparate apply to a registered target
Configuration readbackPublication, timestamp and drift status
YOUR REQUEST PATH · SCHEMATIC
Your applicationsRequests originate here
Kong GatewayLab-verified publication and readback
Azure API ManagementContract-tested · live acceptance outstanding
Model endpointsSelected by your gateway configuration
Requests travel from your applications through your gateways to model endpoints. They do not pass through ARC1’s hub. The separate management exchange publishes approved configuration and reads it back. This diagram shows topology, not live traffic.
Kong OSS 3.9.3: policy publication, readback and drift recovery exercised on a local lab node. Azure API Management: adapter contract tests. Configuration readback does not establish model inference or production savings.
02 / THE OPERATING RECORD
Know what changed.
Keep what supports it.
See what the target holds.
Scheduled checks distinguish matching, drifted, unreachable and stale configurations. A correction starts with a fresh plan and a new approved apply; the reading keeps its configured polling interval.
Keep the financial basis.
Provider bills, gateway measurements and reported usage estimates retain their sources and periods. Compare a proposed change with its baseline and follow the decision’s recorded evidence.
03 / EVIDENCE THAT TRAVELS
A matching configuration
is one part of the story.
Approval records the intended policy. Readback records observed configuration. Request execution and financial results require their own evidence. ARC1 keeps those distinctions visible so a review can move forward with the right next step.
Follow a decision in the product tour- Intended
- The exact policy and separate approval
- Observed
- The target’s configuration, version and readback time
- Retained
- Signed audit receipts checked against a trusted public verification key
START WITH ONE CHANGE
Bring a gateway policy
your team needs to review.
See the proposed change, the approval and the target readback together.