Founder Repo OSSetup Console
Customer-controlled setup. No direct write to main.
Step 2 of 8 · Customer account25%
Guided repository setup

Start your guided setup. Stay in control.

Open the secure account link from your purchase email, then build a repository-specific setup plan and review every proposed change.

No invisible writesEvery installation ends in a draft pull request preview.
Subscription scope enforcedNamed, unlimited-internal and client-delivery scopes are validated before a repository can be bound.
Review every diffExisting files are preserved until you choose how conflicts are handled.
Post-purchase onboarding

Open the secure account link from your purchase email

After Paddle confirms the annual subscription, this checkout browser receives a secure customer session. Resend also sends a short-lived, one-time account link and this WebApp URL to the verified Paddle buyer address.

  • The subscription determines the purchased product and repository scope.
  • The checkout browser is already authenticated after provider confirmation.
  • The emailed account link is hashed server-side, expires quickly, and can be used only once in another browser.
  • Paddle handles checkout; this WebApp stores no card or bank details.
What happens after purchase

From secure checkout to a review-ready draft PR

About 8–12 minutes
  1. 01
    Complete secure checkout

    Choose your annual plan and pay with Paddle. Founder Repo OS waits for Paddle to confirm the subscription directly.

  2. 02
    Open your customer account

    Continue in the checkout browser or use the short-lived, one-time account link sent to the verified buyer email.

  3. 03
    Connect GitHub

    Authorize only the repositories you want Founder Repo OS to see. Connecting GitHub does not change files.

  4. 04
    Choose or create a repository

    Select one authorized repository covered by your plan, or create a new GitHub repository and return to select it.

  5. 05
    Run the read-only scan

    Founder Repo OS checks the repository structure and existing files before proposing any change.

  6. 06
    Configure your operating foundation

    Answer focused questions about the project, AI workflow, review rules and release process.

  7. 07
    Review the complete setup plan

    Inspect every proposed file and resolve each conflict before Founder Repo OS can continue.

  8. 08
    Create 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.