Quickstart
1. Create your account
Open Create account and choose Continue with GitHub. Use a GitHub account with a verified email. If invited, use the account associated with the invited email.
2. Register your company
In onboarding, enter the company name and what you will use ZPX Forge for. Your workspace is ready immediately.
3. Connect GitHub
In GitHub → Install on GitHub pick the account or organization and the repos ZPX Forge can see. When you come back, the installation is linked to your company.
You must administer that GitHub account to install the app. This is how we prevent anyone from linking repositories that are not theirs.
4. Create a project and add its code folders
A project can have one or several repos: front, back, an app monorepo… One of them is the
spec home (where SpecKit's specs/ lives).
With Pro, select a starter project in the architecture step. Its charter includes the reference design, suggested first delivery, acceptance test and signals to monitor. Claude or Codex reads the same design with zpx context --json.
5. Protect your branches
On each project repo, Protect develop and main creates a GitHub rule: those branches only change through pull requests, with no deletion and no force-push.
6. Invite your team
With Pro, in Team you invite people by email with a role. Each person can also have a different role in a specific project.
From then on, every push, PR and check in your repos shows up in the project activity.
Release assurance with Pro
In Project → Hitos, agree on an outcome with the person receiving it. Select the repository, workflow, test file and exact job and step names. The workflow must run the agreed test on push to the production branch. Query GitHub CI from the milestone. Without a run for that commit the evidence remains pending.
Create the release from the passing milestone, review risks and share the approved sheet. The designated person accepts that version or requests corrections on their private sheet. To work through this with your agent, open Instructions for Claude or Codex.
Example acceptance test in GitHub Actions
For a Python project with an isolation test in unittest, this workflow runs one specific case. Substitute your production branch, test module and method, and install your project dependencies before the test step. Agree with the customer on the behavior this case demonstrates.
name: Acceptance
on:
push:
branches: [main]
jobs:
acceptance:
name: Customer acceptance
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: "3.12"
- name: Verify customer isolation
run: python -m unittest tests.test_isolation.IsolationTest.test_other_customer_cannot_read
Save the workflow as .github/workflows/acceptance.yml. In the milestone select this workflow, tests/test_isolation.py, job Customer acceptance and step Verify customer isolation. Forge can record an observed result once it finds the agreed commit and step in GitHub.
Activate Pro
Individual includes one company and up to two personal projects. Pro costs US$10 per member and includes unlimited companies, projects and team members, team feedback and release assurance with CI evidence. Sign in and open the company home to review the terms and activate Pro.