Know every step before you connect GitHub.
This guide shows how your annual subscription opens the WebApp, how repository access is authorized, and where you remain in control.
Six clear steps from verified access to a review-ready draft PR
- 01Verify subscription access
Complete secure checkout, then continue in the same browser or use the secure account link sent to the verified buyer email.
- 02Connect one repository
Authorize and select one repository covered by your plan, or create a new repository with a README. No files are changed.
- 03Run the read-only scan
Founder Repo OS checks the repository structure and existing files before proposing any change.
- 04Configure your operating foundation
Answer focused questions about the project, AI workflow, review rules and release process.
- 05Review the complete setup plan
Inspect every proposed file and resolve each conflict before Founder Repo OS can continue.
- 06Create a draft pull request
Founder Repo OS uses a dedicated branch and draft pull request. You review and merge it yourself; main is never changed directly.
A secure account link follows verified subscription activation
Founder Repo OS sends a short-lived, one-time account link to the buyer email verified by Paddle. Only the token hash is stored. The active annual subscription controls setup and update access through the customer account.
Your repository stays review-first
The WebApp scans before it proposes changes. The installation plan is visible before execution, and the final output is a setup branch plus a draft pull request. Main is never merged automatically.
Updates use the same review-first GitHub path
Automatic updates are off. Future package versions require an explicit entitlement decision first. When approved, the WebApp rescans the repository and presents a full diff before creating a dedicated branch and draft pull request. You decide whether and when to merge it.