Founder Repo OSSetup Console
Customer-controlled setup. No direct write to main.
Step 1 of 10 · AccessAbout 8–12 min
Guided repository setup

Start clean. Stay in control.

Turn Founder Repo OS into a repository-specific setup plan, preview every change, then decide what should happen next.

No invisible writesEvery installation ends in a draft pull request preview.
License 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

Have your Founder Repo OS license code ready

After Paddle confirms payment, the confirmation page shows your code once. When transactional email is enabled and its provider confirms delivery, every purchased code and this WebApp URL are also sent to the verified Paddle buyer address. The first license is activated in the current browser.

  • The code determines the purchased product, setup edition, and repository scope.
  • The first code is already active when you continue from the purchase page.
  • A provider-confirmed purchase email is an additional delivery path, not a substitute for saving the one-time codes shown in the browser.
  • Paddle handles checkout; this WebApp stores no card or bank details.
What happens after purchase

From payment confirmation to a review-ready draft PR

About 8–12 minutes
  1. 01
    Payment is verified

    Paddle confirms the completed order to the server. A browser message alone cannot unlock access.

  2. 02
    Your license codes arrive

    The confirmation page shows every purchased code once. When transactional email is enabled and confirmed, the verified buyer email receives the same codes with the WebApp URL.

  3. 03
    Connect one eligible repository

    The first code is active in the current browser. Connect GitHub, then choose the repository covered by that license.

  4. 04
    Review the guided setup

    Founder Repo OS scans read-only, asks focused questions and explains the proposed repository changes.

  5. 05
    Approve a draft pull request

    The final action creates a dedicated setup branch and draft pull request. You review and merge it yourself.

  6. 06
    Apply future updates through review

    Automatic updates stay off. Approved versions repeat the scan, full diff, setup branch and customer-controlled draft pull request.

Watch the setup walkthrough