Get Started
Keep the existing connection, create the Forge project, describe the environment, add the endpoint, review and activate.
The customer keeps its applications, provider relationships and existing baseline pathway. Forge is added as a separate governed layer around eligible activity.
The operating model is designed to be understandable from the customer side: where traffic starts, what Forge is authorized to touch, how results are measured and how the existing path remains available.

Existing and Forge-enabled pathways remain distinct and visible. The existing provider path stays available while approved traffic can be routed through Forge, making optimization and continuity separately observable.
The customer journey stays deliberately simple. Qualification establishes fit, activation establishes controlled access, and operation measures results against the agreed baseline.
Keep the existing connection, create the Forge project, describe the environment, add the endpoint, review and activate.
Eligible production traffic flows through Forge while Proof Audit verifies savings and required quality.
See cost, savings, traffic and Proof Audit status while continuity protections preserve service.
The existing approved provider pathway is retained. If Forge is unavailable or intentionally paused, eligible traffic can return to the customer’s authorized path so service continuity does not depend on Forge optimization being active.
Start with a high-level qualification conversation. No sensitive or confidential information is required.