OpenRoot Developer Program

Get rewarded for the projects you are already building.

The OpenRoot Developer Program brings independent developers, called OpenRoot builders, together with partners who want to support useful software. Builders develop and grow projects under the OpenRoot GitHub organization. OpenRoot helps promote member projects through its publication and social channels, completely free of charge and as much as it can. Coverage, reach and success are not guaranteed. Partners supply credits, subscriptions, and developer tools for qualifying projects.

Bring your own ideas in any software category, programming language or repository/documentation language, including non-English content. You direct your project and retain rights to your own code. A private development phase is welcome; any public-release conditions are agreed before enrollment. Organization owners retain administrative access to organization-hosted repositories.

Your project is not exclusive to OpenRoot. You can enter hackathons, collaborate elsewhere and take part in other activities, subject to those activities' rules and your project rights.

Current status

The program is in pre-launch. We are seeking founding partners. Applications are open for review; the private portal is available to approved accounts at https://openroot.dev/portal; reward claims are not open; numerical milestones and final fulfillment terms are being prepared. OpenRoot reports an initial set of offers: one month of DeepLearning.AI (one available until claimed), and AI model API credits for GPT, Claude, Gemini and Grok, delivered through budget-limited third-party API access, valued at EUR 50-1,000. The API allowances have per-key budget limits, with no announced quantity cap. Exact learning product, permitted distribution, expiry and recipient terms still need confirmation. These are not official model-provider sponsorships or guaranteed rewards for every member. A broader selection, including paid subscriptions and developer tools, is coming soon; specific offers and dates are not promised. See reward details.

This repository is the public documentation home. It explains the program, answers questions, and invites partnerships. It does not contain the private portal application or applicant records.

Explore

Languages

All seven public program documents are maintained in these languages. English is the editorial source; translated versions must be updated before documentation changes are published. Translations support understanding and are not separate enrollment contracts.

Repository and licenses

Official documentation repository: https://github.com/OpenRootdev/developer-program.

The written guides are licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). Attribute OpenRoot / Kristofer Jussmann when reusing them. Maintenance scripts in scripts/ use the MIT License. These licenses cover this documentation pack, not builders’ own projects or third-party trademarks, and do not replace program or enrollment terms.

Help builders keep building

We welcome partners who can provide AI or cloud credits, paid tool access, or other useful developer benefits. Start with a bounded pilot and support projects that demonstrate genuine traction.

Partner with us, or email partner@openroot.dev. The website's partner form prepares an email draft locally; it is not a server-side submission.

For general questions, contact hello@openroot.dev.

Documentation corrections and questions are welcome through repository issues. Do not post personal application details, security reports, credentials, or reward redemption codes publicly.

A free sandbox. Keep your accounts safe.

OpenRoot is a sandbox for building and collaborating, not a payment request. We will never ask you to send passwords, sign-in or recovery codes, access tokens, API keys, payment details or a fee to join or unlock rewards. Applications need your email and exact GitHub username; enter a sign-in code only on the official portal, never send it to a person. You can invite collaborators and configure repository-scoped apps within your repository permissions; some organization-level actions need an owner. Keep secrets out of repos, applications and messages. Organization hosting is not unlimited free use of paid services.

Questions: hello@openroot.dev. Follow or message OpenRoot on LinkedIn. After accepting the GitHub invitation, read the members-only quick start.

Existing projects belong in the organization

If you apply with an existing project, the accepted project must be hosted under OpenRootdev: transfer the original repository after review, or create an empty organization repository and copy the code there with Git. Do not migrate before the project and migration are approved. Copying code does not copy stars, issues or other GitHub project data. Existing adoption and rewards are reviewed separately. Read the step-by-step builder instructions.

How the program works

The program rewards project success with non-cash benefits. It does not pay for hours, commits, or simply starting a repository.

Apply

Submit your email and exact GitHub username through the builder application form at https://openroot.dev/apply. A project idea or existing project link helps the review. An application is not approval or a reward commitment.

Get approved and verify your identity

Approval creates a pending portal account and sends an email with instructions. Sign in at https://openroot.dev/portal with your approved email and enter the emailed code only on that page. Kristofer manually sends the GitHub organization invitation before approving the portal account. Approval then sends one combined welcome email with invitation-acceptance and repository-creation steps. Automated GitHub identity linking, project metrics, full enrollment and reward claims are not available yet. Pending accounts keep the application’s original 90-day expiry. Approval alone does not grant a funded reward.

Build and grow

Create an approved project under the OpenRoot GitHub organization and agree its success track. Developers manage development, maintenance, and wider marketing. OpenRoot helps promote member projects through its publication and social channels, completely free of charge and as much as it can, without guaranteeing coverage, traffic or adoption. Your project can also participate in hackathons and outside activities.

Show progress

The planned portal will combine associated repositories, contributions, releases, and milestone evidence. Metrics will identify their source and measurement period. Users and package downloads require evidence beyond GitHub alone.

Reach a milestone

Submit the evidence required by your enrolled project's rules. OpenRoot checks the result, its measurement window, and excluded activity. A threshold crossing can start a review; it is not automatic reward issuance.

Choose a confirmed reward

If your claim qualifies under a funded cohort's terms, select an eligible option from its available non-cash catalog. The reward record tracks approval and delivery. The initial offers are reported by OpenRoot; fulfillment terms and claims are not finalized or open yet. Reporting an offer does not grant every builder an automatic entitlement.

Read the reward rules, builder guidance, or the FAQ.

Joining as an OpenRoot builder

You choose what to build. The program can consider software in any category, provided it is lawful, safe to host, respects others' rights, and meets the published cohort requirements.

Bring your own ideas. Any programming language and repository/documentation language is welcome, including non-English repositories. You choose your stack, scope, roadmap and project direction; this is not an English-only or AI-only project collection.

You can keep a repository private during development. Agree on the duration and any public-release requirement before enrolling in a funded cohort. No arbitrary timer or automatic publication is applied. A milestone requiring public release or adoption still needs its agreed evidence. Other builders do not automatically get access to your private code; organization owners retain administrative access.

Application and access

The application asks for your email and exact GitHub username. OpenRoot approval is required. Portal signup is not open to everyone, and signing in with Google or email does not bypass that approval.

A GitHub account is a prerequisite. Approved builders accept an invitation to the OpenRoot GitHub organization and build their repositories inside it. The website accepts applications for manual review at https://openroot.dev/apply. Submission does not create an account or grant access. Additional accounts, GitHub Apps and project-team requests can be included for review. Never submit passwords, tokens or private keys.

Applying before choosing a project

Check “I’m not sure what I’m going to build yet” if you have not chosen a project. Your interests note is optional and you do not need to invent a proposal or repository URL. This is an undecided application for manual review, not an approved project or reward-bearing cohort. A specific project and milestone terms still need approval before reward eligibility.

Application terms and published policies

Before submitting, explicitly accept the current Application Terms and the published builder and reward policies. Acceptance is separate from privacy consent. The backend requires and records the current terms version, 2026-10-12-1, with your submission timestamp. Unchecked, missing or outdated acceptance is rejected.

Application rules:

Provide truthful information and only material you have permission to share. Do not include credentials, private source code or sensitive personal information.
An application requests manual review, not an account, organization membership, repository access or a promised reward. Applying without a chosen project is allowed.
No project, code rights or repository is transferred by applying. Later accepted projects must respect others’ rights and the published builder policies.
Project approval, access, milestones, reward availability and transfers require separate review and agreed terms. Signup alone is not reward eligibility.
Enrollment, project/departure and funded reward agreements remain separate. Applying does not accept unpublished future terms or unannounced reward thresholds.

Privacy, retention and correction/deletion requests are explained below. Questions: hello@openroot.dev.

Application privacy

OpenRoot, operated by Kristofer Jussmann, collects your email, exact GitHub username, project proposal, optional evidence, collaboration/access requests, referral details, optional discovery source and consent record for application review and related communication. The optional, applicant-declared discovery source helps us understand where builders find OpenRoot; it does not use tracking cookies. Do not submit credentials, private source code or sensitive personal information. List other accounts only with their permission.

Submissions are stored privately on Google Cloud in Finland and are available only to authorized administrators. Records are scheduled to expire after 90 days; automatic deletion is asynchronous. Approved portal accounts will have separate terms before activation. Hosting infrastructure handles technical request logs; the application service does not deliberately log application content.

Applying does not subscribe you to the newsletter. Contact hello@openroot.dev to access, correct or delete a submission, or withdraw consent. Identity verification may be needed before acting on a request. Submission is not proof that you control the supplied email or GitHub account.

Your role

Builders develop their projects, attract users, maintain them, and provide milestone evidence. OpenRoot helps promote member projects through its publication and social channels, completely free of charge and as much as it can. It does not operate every project's marketing campaign or guarantee coverage, reach, a positive review or success.

Participation is not exclusive. Enter hackathons, collaborate outside OpenRoot and take part in other activities with your project. Check the event's own rules and any contributor/license obligations; joining OpenRoot does not require giving up those opportunities.

GitHub teams and repository roles scope collaboration. Access to your project does not grant organization-wide administration. The planned portal shows repositories associated with you, including team projects; the person who created a repository is not automatically its only contributor or reward recipient.

Your project stays yours

The intended program policy is that you retain ownership of your own code and lead your project. The GitHub repository is hosted under OpenRoot's organization, with repository-level Admin for the approved project lead. Organization owners retain administrative access. Repository Admin is not personal ownership of the GitHub namespace; licensing and departure/transfer arrangements must be agreed before enrollment.

Existing projects and collaboration

You may propose an existing repository with users, downloads or stars. Submit its URL and dated evidence first; do not transfer it before review. Membership, transfer approval, enrollment and reward claims are separate manual decisions. Existing metrics qualify only under explicitly agreed baseline and cohort rules, not merely because the repository entered the organization.

Project-specific teams can cover multiple approved repositories. Leads get scoped Admin; collaborators receive the reviewed project role. Avoid blanket write access and unintended parent-team inheritance. Extra automation accounts do not count as independent rewarded builders.

Before you enroll

Project rights, software license, maintainer responsibilities, departure/transfer arrangements, and team reward allocation must be disclosed and agreed. The final project agreement is still being prepared. Joining a GitHub organization alone does not settle these questions.

An enrolled cohort must state the available rewards, its capacity, thresholds, measurement period, and review rules. Until these exist, interest in the program does not establish an entitlement to a reward.

See how it works and milestones and rewards.

Referrals

The planned builder referral program recognizes referrals of approved builders who reach verified project milestones, not signup counts. Applications can include a referrer's exact GitHub username for review. Funding and final eligibility/benefit rules must be published before activation.

Pending portal privacy

A reviewed approval creates a pending portal account with your email, GitHub username and onboarding status. It keeps the original application expiry; it does not extend the 90-day retention window. Sign-in uses a necessary secure browser-session cookie that expires after eight hours. Email-code challenges expire after ten minutes; the service stores code hashes, not plaintext codes. Google Cloud processes private account and review records; Resend processes transactional sign-in and approval emails. Only authorized administrators can review applications, and builders can access only their own portal information. No newsletter subscription, advertising tracking or automatic GitHub invitation is created. Full enrollment and active-profile retention require separate terms. Ask hello@openroot.dev about access, correction or deletion.

Bringing an existing project: step by step

An accepted existing project must be hosted under OpenRootdev. After project review, either transfer the original repository or copy its code into a new organization repository. A link to a repository outside the organization is not enough. These instructions replace the create-new-project step for existing projects.

Before either route: submit the original URL, confirm your authority and contributor/license rights, agree the migration with OpenRoot, and accept your organization invitation. Back up the project and review secrets, integrations and Actions billing before moving or pushing anything. Contact hello@openroot.dev if approval or permissions are unclear.

Option A: Transfer the original repository

Recommended when preserving stars, issues, pull requests and Git history matters.

1. Open the original repository on GitHub, then Settings → General → Danger Zone → Transfer. You need repository Admin and permission to create repositories in OpenRootdev; transfers out of another organization may need its owner.
2. Set the new owner to OpenRootdev. Check the destination name is free, read GitHub's warnings (private repositories may lose paid-plan features on GitHub Free), then type the repository name and confirm.
3. Check the repository URL now starts with https://github.com/OpenRootdev/. Ask OpenRoot to verify your repository-level Admin and the intended team access; organization owners retain administrative access.
4. In each existing local clone run git remote set-url origin https://github.com/OpenRootdev/YOUR-REPOSITORY.git. Check integrations, deployments, Pages, secrets and workflows before resuming work. Do not recreate the old repository path, as this can break redirects.

Option B: Copy the code into a new organization repository

Use this if you want to keep the original repository where it is and maintain the approved project copy in OpenRootdev.

1. Open New repository. Verify Owner = OpenRootdev, choose the agreed name and public/private visibility. Do not initialize a README, license or .gitignore; create an empty repository.
2. In a terminal, replace the example names and use a new local folder: git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY.git openroot-project, then cd openroot-project.
3. Add the destination without changing the original remote: git remote add openroot https://github.com/OpenRootdev/YOUR-REPOSITORY.git.
4. Push the checked-out branch: git push openroot HEAD:main. Confirm the files appear in the organization repository. For later updates, push to openroot, not the original origin. If the destination is not empty or a push is rejected, stop and ask for help; do not force-push.
5. This copies the selected branch's reachable commit history, not stars, issues, pull requests, releases, repository settings or every branch/tag. Git LFS objects and submodules need separate handling; ask for help. Retain license/attribution files, and do not copy secrets.

Send OpenRoot the final organization repository URL to associate it with your reviewed project. Existing adoption and rewards still require an agreed baseline and separate approval; no double-counting across copies. Do not delete the original repository just to participate. You retain rights to your own code; hosting under an organization does not remove its owners' administrative access.

Official references: transfer, new repository, Git push.

Milestones and rewards

Rewards help builders keep building. They are non-cash benefits supplied through confirmed partnerships or an explicitly funded cohort.

What can be rewarded?

A project uses a success track appropriate to what it does:

Track	Possible evidence
Attention	Organic GitHub stars, meaningful external interest, or coverage
Distribution	Release/package downloads, full clones, or container-image pulls within a defined window
Adoption	Active or returning users, or independent projects integrating the software
Sustained use	A relevant adoption measure maintained over time

Stars show interest. Downloads show distribution. Neither automatically equals active users. Repeated automated activity, purchased engagement, and self-generated inflation do not establish genuine traction. Exact exclusions will be published with each cohort.

Numerical targets are not finalized. Every enrolled project must know its metric, source, baseline, threshold, measurement period, evidence requirements, review process, reward, and claim limit.

What can a reward include?

Categories include AI/API access, GPU or cloud capacity, paid subscriptions, IDEs, and other useful developer tools. Builders should have a choice among eligible available options.

Initial offers reported by OpenRoot / 12 October 2026

DeepLearning.AI: one month, with one offer available until claimed. The exact product and redemption terms still need confirmation.
AI model API credits: allowances valued at EUR 50-1,000, with model families including GPT, Claude, Gemini and Grok. OpenRoot reports that each supplied key has a strictly enforced budget limit. There is no announced quantity cap, which does not mean unlimited spend or an automatic EUR 1,000 grant for each person. Permitted distribution, expiry, supported models, recipient eligibility and delivery terms remain to be verified before issuance. This is third-party access, not a transfer of credits into a builder's own model-provider account and not an official model-provider sponsorship.
More benefits coming soon, including paid subscriptions and developer tools. No additional product, quantity or date is promised.

The vendor identity is kept private in this planning stage. Recipient disclosures needed for informed use must be agreed before redemption. Never post API keys, redemption codes or account credentials in public documentation, applications or GitHub issues. No shared personal account or provider-key transfer is promised. Applications are open for review, but reward claims are not open yet; these offers are not confirmed referral rewards.

Each option must disclose account eligibility, service/duration or credit amount, expiry, redemption deadline, and any ongoing billing obligation. OpenRoot will not ask for your account password or distribute shared paid accounts.

Choosing and using a reward

After milestone and claim approval, builders choose among eligible available options for their project or cohort. Credit amount, model availability and terms are confirmed for that offer; the EUR 50-1,000 range is not an automatic grant of the maximum to every builder. Free best-effort promotion is a separate member benefit, not something a builder spends a reward on.

Hermes, OpenClaw and OpenCode support configurable custom providers or OpenAI-compatible endpoints, but the actual reward gateway has not yet been tested with these clients. Cursor custom-key chat needs client/model/gateway verification; these credits do not buy a Cursor subscription or Tab access. Codex requires a gateway that supports the Responses API, streaming and tool-call conversations. Claude Code requires a supported gateway API format, such as Anthropic Messages. Generic OpenAI Chat Completions compatibility alone does not establish Codex or Claude Code support. Exact endpoint, model IDs, client limitations and recipient privacy terms must be confirmed before redemption.

See Codex gateway requirements and Claude Code gateway requirements. No end-to-end client compatibility is promised by this draft.

Funding and fairness

Rewards and funding are confirmed before projects enroll in a reward-bearing cohort. An unfunded interest list carries no reward promise. If inventory is limited, capacity and reservation rules must be visible from the start.

The program must distinguish guaranteed qualifying rewards from judged awards or quotas. Requirements cannot be changed retroactively to reject an otherwise valid claim. Existing-project baselines and whether past success counts will be defined before enrollment.

Rewards are allocated under the agreed project/team terms, not multiplied for every contributor by default. Claims move through submitted, reviewed, approved, and issued states. Redemption may remain unknown if the provider supplies no confirmation. Builders can request a correction or review of a decision.

Non-cash rewards still require appropriate accounting and jurisdiction-specific review before launch. This draft does not define tax treatment.

How it works | Partner with the program

Builder referral program

Pre-launch plan, 11 October 2026. The referral program is not active and no funded referral benefits or claim tools are confirmed.

Refer builders who reach real milestones

The intended program recognizes referrals after the referred builder is approved and reaches a verified qualifying project milestone. An application, signup or repository creation alone is not enough.

Share the program guide with someone who wants to build their own idea. Once intake opens, the applicant can enter the referrer's exact GitHub username. No bulk contact uploads or automatic invitations are part of this plan.

OpenRoot separately reviews membership, project admission, referral attribution, milestone evidence and any funded referral claim. Referral information never bypasses an approval. New projects and approved existing repositories can participate under the same disclosed cohort rules.

Fair attribution

A supplied GitHub username is a claim, not proof of identity. Attribution must be confirmed and linked to verified account IDs. Duplicate or disputed referrals require review. Self-referrals, extra automation identities, duplicate accounts and manipulated usage cannot inflate qualifying referrals.

A referrer does not receive access to another builder's private project data. Any status shown to a referrer must be limited to disclosed information and agreed permissions.

Funding and terms before activation

Potential non-cash rewards can include authorized credits, subscriptions and developer tools. Actual choices, referrer eligibility, milestones, benefit limits, attribution timing, appeals, team handling, capacity and redemption rules must be published and funded before enrollment. No reward quantity or threshold is announced.

A referral reward is separate from the project's own milestone reward. Neither is promised by merely sharing a link, joining the organization or transferring an existing repository. Earlier achievements can count only if the approved cohort explicitly accepts them.

See the referral guide, builder guide, reward model and partnerships.

Partner with the OpenRoot Developer Program

Help builders keep building

Support developers who build innovative GitHub projects and attract genuine use. Provide useful credits, subscriptions, or developer tools when projects reach transparent, verified milestones.

We are seeking founding partners for a small, bounded pilot. OpenRoot reports initial offers, but enrollment and claims are not open. Fulfillment and provider authorization still need confirmation. No official provider sponsorship is implied.

Ways to help

Reward partner: offer authorized recipient licenses, gift subscriptions, or direct credit grants.
Cohort partner: support a limited set of projects with a clearly capped reward inventory.
Technical partner: offer relevant mentoring, office hours, or project support. These supplement the program rather than masquerading as a paid reward.

An optional financial sponsor could fund purchases from the non-cash reward catalog. This requires a separate agreed budget and fulfillment process. Developers would still receive benefits rather than cash payments.

What we can offer

An agreed pilot can include transparent partner acknowledgment, publication/social coverage of relevant projects, links to their public work, and an aggregate report on verified outcomes and reward redemption where available.

Member-project promotion through OpenRoot's publication and socials is completely free of charge, on a best-effort basis. Participation does not prevent builders from entering hackathons or other activities.

We do not promise an audience size, guaranteed customer conversions, favorable editorial coverage, exclusivity, or access to applicant emails. Public acknowledgment requires permission. Sponsor support does not purchase control of the program's success decisions.

Make a small first commitment

Tell us the benefit you can provide, how many developers or projects it can support, its duration/credit amount, eligible accounts and countries, expiry, redemption method, and any billing obligations. A provider should explicitly authorize use in this milestone-based program. Ordinary non-transferable signup or startup credits are not a redistributable prize pool.

Contact

Partner with us or email partner@openroot.dev.

The OpenRoot partner page prepares a draft locally for your email app; it does not submit or store an inquiry on the site. Nothing is received until you send the email.

For general questions, contact hello@openroot.dev.

Program overview | Reward rules | FAQ

Frequently asked questions

What is the program called?

The OpenRoot Developer Program. Its developer participants are OpenRoot builders.

Is it live?

Applications and the approval-only private portal are available. Funded reward cohorts remain in pre-launch, seeking founding partners; reward claims are not open.

Are rewards cash?

No. The planned rewards are subscriptions, credits, and developer-tool access.

Can any type of project join?

Any software category can be considered. Projects must satisfy the published cohort, rights, safety, and conduct requirements. OpenRoot does not need to invent or direct every project.

Any programming language and repository/documentation language is welcome, including non-English repositories. Bring your own ideas; you choose the stack, roadmap and project direction.

Can I apply without a project idea?

Yes. Check “I’m not sure what I’m going to build yet.” An interests note is optional. OpenRoot reviews undecided applications too, but a specific approved project and agreed milestones are required before reward eligibility. Explicit acceptance of the current application terms and published program policies is required before every submission, separately from privacy consent. Read the application rules.

Can I start with a private repository?

Yes. A private development phase is allowed. The duration and any public-release condition are agreed before enrollment, not applied by an automatic timer. Private development does not itself prove a milestone that requires public release or adoption. Other builders do not automatically get private-code access.

Is there a referral program?

A milestone-based builder referral program is planned. The referred builder must be approved and reach a verified qualifying project milestone before a funded referral claim can be reviewed. Signups alone are not rewarded. No benefits, caps or funded availability are confirmed yet.

Does OpenRoot market my project?

OpenRoot helps promote member projects through its publication and social channels, completely free of charge and as much as it can. Builders manage wider marketing and growth. Coverage, traffic and project success are not guaranteed.

Can I enter hackathons with my project?

Yes. You may participate in hackathons, outside collaborations and other activities. OpenRoot participation is not exclusive. Respect the event's own rules and any project/contributor rights.

What are the initial offers?

One month of DeepLearning.AI, one available until claimed, plus AI model API credits for GPT, Claude, Gemini and Grok, delivered through budget-limited third-party API access, valued at EUR 50-1,000. OpenRoot reports strict per-key budgets and no announced quantity cap for API offers. These are not credits transferred to your own model-provider account or official vendor sponsorships. Exact product, permitted distribution, expiry, eligibility and delivery terms remain pending. Claims are not open. Read the offer details.

Does a GitHub star target guarantee a reward?

Only the enrolled cohort's published rules can establish qualification. Attention may have its own track; stronger adoption may unlock a different reward. No numerical target is announced yet; reported offers still require finalized claim and delivery terms.

Can I choose my reward?

That is the intended model: choose among the eligible, available rewards for your cohort and tier. A particular subscription or provider is not guaranteed until confirmed.

Can anyone sign into the portal?

No. You must apply and be approved. Approval creates a program account. Sign-in identifies you; it does not grant membership by itself.

Why enter my exact GitHub username?

It helps locate the correct account. You will also verify control through GitHub linking; merely typing someone else's username cannot claim their projects.

Is the email code MFA?

It is an onboarding email verification check. It should not be presented as strong independent MFA. Any additional passkey/authenticator requirement will be described before access is activated.

Who owns the project, and what if I leave?

The intended policy is that you retain ownership of your own code and lead your project. Your repository is hosted under OpenRoot's GitHub organization and you receive repository-level Admin. Organization owners retain administrative access, so it is not the same as a personally owned repository under your username. Final licensing, maintenance, contribution and departure/transfer terms must be agreed before enrollment.

Can I propose an existing repository?

Yes. Applications are open for manual review. Submit the original URL, your authority to transfer or copy, and dated adoption evidence. Prior achievements count only if the approved cohort's baseline rules allow them. If you apply with an existing project, the accepted project must be hosted under OpenRootdev: transfer the original repository after review, or create an empty organization repository and copy the code there with Git. Do not migrate before the project and migration are approved. Copying code does not copy stars, issues or other GitHub project data. Existing adoption and rewards are reviewed separately. Read the step-by-step builder instructions.

Can I request additional accounts or project teams?

Yes. Include exact GitHub usernames or GitHub App names, their human/machine/integration type, purpose, target repositories and requested roles. Project-specific teams can cover multiple approved repositories without granting organization-wide write access. Never include secrets. Team and automation requests require review.

How are team rewards divided?

The project/team allocation is agreed before enrollment. Repo creation, commit counts, or the final merged PR author do not automatically determine the allocation.

What if sponsors do not provide enough rewards?

Unfunded cohorts cannot promise rewards. Funded cohorts need visible capacity limits and inventory reservations. If an agreed option becomes unavailable, the program follows its disclosed substitution and resolution terms.

How can my company partner?

Read partnerships and contact partner@openroot.dev. The website partner page prepares an email draft locally; nothing is received until you send it from your email app.

For general questions, contact hello@openroot.dev.

A free sandbox. Keep your accounts safe.

Questions: hello@openroot.dev. Follow or message OpenRoot on LinkedIn. After accepting the GitHub invitation, read the members-only quick start.