Questions before you build.

Yes. Use Join the community, verify your GitHub account, choose an optional interest and agree to the community rules. The privacy notice remains available to read. This requests ordinary organization membership in the Community team only. Accept the invitation on GitHub to finish. It does not create a portal account, subscribe you to the newsletter or qualify a repository for rewards. Community members may create repositories under the current organization settings and apply to the developer program later. How community joining uses your information.

OpenRoot is primarily a developer program and builder community for useful open-source projects. Program participants are called OpenRoot builders. The newsletter supports this work by sharing projects, builder stories and practical technical ideas. Its coverage of agents, automation, infrastructure and AI-powered 3D does not limit the program: projects can be in any software category that meets the published requirements.

Yes. Applications are open, approved builders can join the GitHub organization, and approved accounts can use the private portal. We are seeking partners to expand the reward pool. Milestone claims are open for manual review. The first eligible star milestone is 20 stars: 800 points, available for redemption after claim approval. See the full ladder and claim instructions.

Yes. Apply with your exact GitHub username. After approval and identity verification, you join the OpenRoot GitHub organization and create your project there, or use a reviewed transfer or code copy of an existing repository.

We are looking for builders creating, or exploring, projects intended for other people to use: useful tools, software that solves a problem or helps its users do something. New ideas, existing projects and undecided applicants are welcome; your project does not need existing users.

No. Bring your own ideas in any software category or programming language. Repository content and documentation may use any language, including non-English languages. Projects must still respect rights, safety, conduct and the agreed cohort requirements.

Yes. Check “I’m not sure what I’m going to build yet.” Your interests note is optional. A specific project and agreed milestones still need approval before reward eligibility. You must accept the current Application Terms and published program policies before submitting, separately from privacy consent. Read the application terms.

Yes. A private development phase is welcome. The duration and any public-release requirement are agreed before enrollment; we do not automatically publish your repository. Private status does not by itself qualify a public-release or adoption milestone. Other builders do not automatically get access to it.

You retain rights to your own code and lead your project. The repository is hosted under OpenRootdev, with repository-level Admin for the member who creates it or brings it in through an approved transfer. You choose collaborators, roles and contribution rules. Choose a suitable license and respect existing contributor rights.

Read how projects and collaboration work.

Not through default write access. The planned organization model has no blanket write permissions. Access is granted to your approved project repositories or an explicitly approved collaboration. Everyone can still read and fork public repositories and propose changes through pull requests.

Yes. Apply with its URL and dated evidence for manual review. An accepted existing project must be hosted under OpenRootdev: transfer the original after review, or copy the code into a new organization repository. Do not migrate before agreement. Copying code does not copy stars, issues or other GitHub project data. Prior adoption and rewards are reviewed separately. Read the step-by-step options.

Not automatically. Existing traction can support review, but prior achievements count only if the approved cohort explicitly permits them. Funding, capacity, measurement windows, baselines and verified evidence still apply. The published star ladder applies to agreed eligible new growth. Manual claims are open; historical stars need a separate agreement.

Yes, the planned model supports project-specific teams and projects spanning multiple repositories. List exact GitHub usernames, repository URLs and proposed roles. Lead maintainers and collaborators get scoped access. Team reward allocation must be agreed before enrollment.

The repository admin chooses collaborators, project-specific teams, repository roles and contribution rules without separate OpenRoot approval. You can organize one project across multiple repositories. Other members do not automatically receive access to private code or write access to your repository. Repository-scoped apps use GitHub's normal permission controls; organization-wide changes may need help from OpenRoot.

Existing organization members can create new repositories without another application or separate OpenRoot approval. New repositories created from scratch automatically join the program, subject to its policies. OpenRoot manually reviews repositories and contacts the repository admin if changes or removal are needed. Policy bots are planned as the organization grows; they are not active yet. Program enrollment does not automatically approve rewards: private projects must become public and meet the agreed milestone and funding conditions before earning rewards.

No. Signing in identifies a person; it does not approve them. Only approved accounts can sign in with email-code verification. GitHub identity linking and project metrics are not connected yet; manual milestone claims are available through hello@openroot.dev, not an automated portal wallet. Account approval is separate from funded enrollment.

Current offers reported by OpenRoot

• DeepLearning.AI: one month, with one offer available until claimed. Exact product and redemption terms are being confirmed.
• AI model API credits: $20-$10,000 budget-limited allowances. This is not an automatic $10,000 reward per person.
• More benefits coming soon.

Current partner-reported models: GPT-6 Astra, Claude Fable 5.1 and Gemini 4 Argon. Availability is confirmed for each approved offer. We aim to switch to successor models after their API release when partner support, provider terms and similar pricing allow; this is not a guaranteed release-day upgrade.

Significant inference-provider pricing or terms changes can change the available models or make API grants temporarily unavailable. Approved unspent points remain recorded and may be redeemed for other eligible available rewards under the agreed terms. Points are not cash; alternative inventory and immediate redemption are not guaranteed. Existing agreed rewards are not cancelled by a catalog update.

These are third-party allowances, not credits transferred into your own model-provider account or official sponsorships. Distribution authorization, expiry, recipient eligibility and delivery terms are confirmed for each offer before issuance. Milestone claims are open for manual review. See the points and milestone table. These offers are not confirmed referral rewards.

Yes. You can participate in hackathons, external collaborations and other activities. OpenRoot participation is not exclusive. Respect event rules and project/contributor rights.

Hackathon builders are welcome, whether preparing to enter or continuing a project. Additional rewards for strong results in eligible, pre-approved hackathons are planned. Events, outcomes, evidence, funding and bonus terms must be published and agreed before a reward-bearing offer begins. A win does not automatically earn points or a reward. No specific eligible events or bonus amounts are announced yet; hackathon bonus claims are not open.

Builders manage growth, users and maintenance. OpenRoot helps promote member projects through its newsletter and socials, completely free of charge and as much as it can. It does not guarantee coverage, audience reach or project success.

Promotion is not limited to one feature. Projects may appear multiple times in the newsletter and on social channels through project highlights, showcases and deep dives. Builders can send releases, substantial updates and user stories to hello@openroot.dev for editorial consideration. This support is completely free of charge and does not require earning or redeeming a reward. Timing and format depend on editorial fit and available capacity; OpenRoot does not guarantee repeat coverage, reach or results.

Yes, a milestone-based program is planned. A referral can qualify only after the referred builder is approved and reaches a verified project milestone. Signups alone are not rewarded. Funding, eligible benefits, referrer eligibility and caps must be published before activation. Read the referral plan.

No. This is a free sandbox for building and collaborating. OpenRoot will never ask you to send passwords, sign-in or recovery codes, access tokens, API keys or payment details, or pay a fee to join or unlock rewards. Applications need an email and exact GitHub username; enter sign-in codes only at the official portal, never send them to a person. Keep secrets out of repositories, forms and messages. Paid third-party services are not automatically funded by organization membership.

For general questions, email hello@openroot.dev or follow or message OpenRoot on LinkedIn. For partnerships and sponsorships, email partner@openroot.dev.

Visit Partner with us or email partner@openroot.dev. The partner form prepares a draft on your device. OpenRoot receives it only when you send it from your email app.

Visit the archive on Beehiiv or explore the newsletter. The publication is hosted at openroot.beehiiv.com.