How Forge Works

Get started with Forge in five simple steps.

The standard objective is easy setup with minimal disruption to the environment already working for you.

Onboarding moves from commercial qualification to controlled technical activation. Each step narrows uncertainty before Forge is allowed to influence production traffic.

Context-specific Forge diagram for this page.

Five steps

A governed path from interest to activation. Qualification, connection, baseline proof, activation and measurement happen in sequence so each dependency is understood before production influence begins.

01Qualify the workloadConfirm the workload is measurable, technically accessible and commercially meaningful.
→
02Create the Forge projectEstablish the customer-scoped Forge project and approved provider pathway.
→
03Describe the environmentCapture workflows, quality requirements, routing identifiers and operating constraints.
→
04Validate safelyRun readiness, routing, security and Proof checks before activation.
→
05Review and activateCustomer-approved activation begins with visibility and continuity controls intact.

What the customer keeps

Setup is additive rather than a forced replacement. Provider ownership, baseline continuity and customer decision rights stay in place while Forge is introduced around eligible activity.

▣

Applications

Your existing applications remain the starting point.

☁

Provider relationships

Provider ownership and billing visibility remain yours.

↔

Baseline pathway

The existing path remains available for Proof and continuity.

Next step

See where Forge could fit your AI environment.

Start with a high-level qualification conversation. No sensitive or confidential information is required.

Let’s Talk →