What do you want Forge to do?
No model picker. Forge routes models automatically.
No verified build yet
Run Forge or test a project to generate evidence.
Task evidence
Tell Forge what you want above.
What Forge remembers
Review before accepting
Test → Fix → Retest
Forge marks a build Verified only when required checks pass.
Browser & visual validation
Open a public staging URL, capture runtime errors, layout overflow and screenshot evidence.
No browser check yet.
No test run yet.
Explicit permissions. Nothing hidden.
Editors, CI, SDKs & cloud
Install an adapter, use your normal Forge API key, and keep the same verified run workflow everywhere.
Forge Core 1.0
Forge IR → dependency impact → atomic patch → specialist verification → proof receipt → privacy-safe learning.
Legacy Forge 0.2.2 remains available automatically if the Core runtime has an internal failure.
What Forge has actually delivered
These figures come from your real Forge jobs and integration runs. Forge does not invent financial savings.
Proof contract
Understand → Plan → Build → Test → Fix → Verify. A result is not presented as verified unless the required checks pass.
Release manifestExport proof JSONObserved workload
Bounded by design
Deploy verified release
Project tests must pass before activation. Forge keeps previous verified releases available for rollback.
No active release yet.
Active and previous releases
Workspace access
Simple by default
Automatic by default. Pin only when you want to.
Connect Alibaba Cloud / Qwen, NVIDIA NIM, or another configured provider without changing the Forge workflow. Stored keys are encrypted and never displayed again.
Usage generated through Forge
—
No production credentials are exposed in this staging workspace.