EFEnvForgeJoin waitlist

Private build waitlist

Bring EnvForge to your first branch workspace.

Tell us how your developers and AI agents should use envforge up, which GitHub repositories need onboarding, and how your organization wants Auth0 access, signed dev links, and awake-only runtime billing introduced.

CLI entryenvforge up

Developers and agents attach to an always-ready shell before the runtime finishes waking.

OnboardingAuth0 + GitHub

Auth0 handles user identity while GitHub App access stays limited to the repos you choose.

Billingawake runtime only

Runtime CPU and memory bill while services are awake; idle sleep keeps the shell ready without metering the VM.

workspace signupstatic intake

No backend integration yet. This validates the intake flow and keeps your entered context on the page.

What we will review

The signup asks for the workspace shape, not a generic demo.

Early access planning starts with the repositories, organization membership, first runtime size, and awake/sleep policy your team needs before agents rely on branch workspaces.

  • Auth0 organization membership and EnvForge product roles for CLI and dashboard access.
  • GitHub App installation scope for the repositories that should receive envforge.yml setup PRs.
  • First envforge up workflow: shell baseline, services, resources, signed dev links, and readiness checks.
  • Runtime billing expectations while web, API, workers, database, cache, mail, and storage are awake.

After signup

First-release onboarding should leave a receipt.

A private-build follow-up should end with a concrete first workspace receipt: who owns repo setup, which access policies are active, what signed dev link a reviewer opens, and what runtime policy controls cost.

Review first workspace docsReview signed dev links
  1. Repo setupenvforge.yml PR owners

    Selected repositories and envforge.yml PR owners are named before the first workspace depends on generated setup.

  2. Access setupAuth0 + GitHub App

    Auth0 organization, EnvForge roles, and GitHub App install scope are agreed before CLI or dashboard access opens.

  3. First workspaceenvforge up receipt

    The handoff includes the envforge up command, resource readiness, and signed dev.envforge.ai URL for the first reviewer.

  4. Runtime policysize + sleep + cap

    The receipt calls out runtime size, idle sleep, and cap posture so awake-only billing expectations are reviewable.