Start on solid ground.

Understand the parts of ForgeZero, then connect your first workspace.

Two deployments. One workspace.

The public website and console are a static SvelteKit application on Cloudflare Pages. Browser requests go to a separate ForgeZero API. The API, database and workload Agents run inside the project’s dedicated server guest. A static site does not require a frontend server inside that guest.

Sign in, then create a workspace

Open Log in and request a code for your email address, or use an already registered passkey. Email verification starts activation. Save and confirm your account backup, then set a passkey to complete access. Use Activate or recover account to resume onboarding or replace a lost passkey with your saved phrase. Your workspace has a separate random seed and independent governance; an account session does not bypass its custody policy.

Connect only what you need

Create your workspace, organize projects and bind scoped credentials. Configure custody and approval policies before governed infrastructure actions. Connect Git automation after the platform is live. Never place provider secrets in frontend configuration.