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

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.

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.

Detailed customer walkthrough

Watch the complete purchase-to-install journey

The recording uses the real local WebApp with test data. Pause, seek, enable English or German captions, or read the transcript at any time.

Native pause and seek controls
Demonstration only: no real payment, buyer data, customer repository or automatic merge is used in this recording.

Silent visual walkthrough. English and German captions, plus both complete transcripts, are available in the player.

  1. Annual subscription verification and secure account delivery
  2. Customer-account verification
  3. GitHub connection and repository selection
  4. Read-only scan and guided questions
  5. Installation plan, setup branch and draft PR
  6. Customer account, repository ledger and controlled product updates
Read the complete transcript

Repository Starter is USD 149 net per year, Repository Pro is USD 399 net per year, and Repository Unlimited is USD 699 net per year for eligible internal repositories of one legal entity. The subscriptions renew once a year until canceled. Repository Agency is a separate sales-assisted USD 1,499 net annual subscription for up to ten named client repositories. After checkout, Founder Repo OS waits for Paddle's signed server confirmation. When the subscription is verified, the current browser receives a secure customer session. Resend sends the verified Paddle buyer address a short-lived, one-time account-access link with the WebApp URL. The verified subscription controls customer access and repository scope. Connect the GitHub App and select an eligible repository. Founder Repo OS reads the repository before proposing changes. Answer the guided questions, review the recommendations, inspect every proposed file and resolve any conflict. Only after your final confirmation does Founder Repo OS prepare a dedicated setup branch and draft pull request. It never writes directly to main and it never merges for you. Your customer account then records the repository by its immutable GitHub ID. Future product updates are never applied automatically. After an explicit subscription update approval, each repository repeats the read-only scan, full-diff review, dedicated branch and draft-pull-request flow.

English transcriptDeutsches Transkript
Account delivery

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.

GitHub control

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.

Product updates

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.

Start Guided Setup