Choose the right license
After a pricing selection, the main site hands you to this protected WebApp checkout. Three self-service plans are available here. Repository plans cover named repositories; Business Unlimited covers eligible internal repositories for one legal entity, including agencies. Client work uses a separate sales-assisted license.

Understand the handoff
After checkout, the WebApp ignores browser success messages. Paddle sends a signed transaction-completed webhook to the server. Only matching product, price, currency and quantity create access. When email is enabled, the server starts an idempotent delivery.

Save every license code
The confirmation page displays every license code once and reports email status separately. After provider acceptance, the verified Paddle buyer address receives the same codes and WebApp link. Save them in a password manager. Founder Repo OS stores only a cryptographic digest and the final four characters.

Confirm the license scope
The first code is active in this browser. For another purchased code, choose Use another license code in the License Account, then enter the saved code. The server reads package and repository scope; the browser cannot upgrade it.

Connect GitHub
Next, connect the Founder Repo OS GitHub App. The WebApp explains the requested permissions before connection. Tokens stay on the server, and the setup flow never asks for a personal access token in the browser.

Choose an eligible repository
Choose the repository covered by the license. Founder Repo OS records the immutable numeric GitHub repository ID, so a later repository rename does not silently move the license. One-repository plans block a second active binding.

Run the read-only scan
Before proposing changes, the WebApp performs a read-only scan. It identifies existing documentation, workflows and conflicts. At this point nothing has been written to the repository.

Answer guided questions
Answer the guided questions about the project, team, AI tools, review rules and release controls. Recommended defaults are explained, every answer is editable and progress is saved securely during the session.

Review recommendations
Founder Repo OS turns those answers into explainable recommendations. Review the reasoning first, then open the installation plan. Nothing is installed merely because a recommendation was generated.

Inspect every proposed file
The installation plan separates new, modified, unchanged and conflicting files. Open the full diff and choose how each conflict should be handled. Execution remains blocked until every required decision is complete and you explicitly confirm the setup action.

Create a setup branch and draft PR
Only then does Founder Repo OS create or prepare a dedicated setup branch and a draft pull request. It does not write directly to main and never merges automatically. Review the pull request in GitHub and merge only when you are satisfied.

Manage updates and the repository ledger
After setup, the license account records the package and repository ledger. Eligible licenses can add repositories within scope. Approved updates repeat the read-only scan, full diff, setup branch and draft pull request. Automatic updates stay off; you choose every merge.