Know every step before you connect GitHub.

This guide shows exactly how the license reaches you, how the WebApp uses it, and where you remain in control.

What happens after purchase

From payment confirmation to a review-ready draft PR

About 8–12 minutes

01
Payment is verified
Paddle confirms the completed order to the server. A browser message alone cannot unlock access.
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.
03
Connect one eligible repository
The first code is active in the current browser. Connect GitHub, then choose the repository covered by that license.
04
Review the guided setup
Founder Repo OS scans read-only, asks focused questions and explains the proposed repository changes.
05
Approve a draft pull request
The final action creates a dedicated setup branch and draft pull request. You review and merge it yourself.
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.

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.

Payment verification and one-time code delivery
License activation and package confirmation
GitHub connection and repository selection
Read-only scan and guided questions
Installation plan, setup branch and draft PR
License account, repository ledger and controlled product updates

Read the complete transcript

After checkout, Founder Repo OS waits for Paddle's signed server confirmation. When the order is verified, the confirmation page shows every license code once. When transactional email is enabled and confirmed, the buyer email receives the same codes with the WebApp URL. Save all codes in a password manager before leaving the page. The first code is already active in the current browser. In a new browser, paste the code on the license screen. Confirm the package 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 license account then records the repository by its immutable GitHub ID. Future product updates are never applied automatically. After an explicit entitlement approval, each repository repeats the read-only scan, full-diff review, dedicated branch and draft-pull-request flow.

English transcript Deutsches Transkript

License delivery

Codes are displayed once after verified payment

Founder Repo OS stores only a cryptographic digest and the last four characters. The full code cannot be read back from the database, so the confirmation page requires you to acknowledge that every code is saved before setup continues.

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