Questions before you build.

OpenRoot combines a newsletter, builder community and planned open-source developer program. Program participants are called OpenRoot builders. The newsletter covers agents, automation, infrastructure and AI-powered 3D; program projects can be in any software category that meets the published requirements.

Not yet. We are seeking founding partners and preparing enrollment. Applications and the approval-only private portal are available; reward claims are not open. OpenRoot reports initial offers whose final delivery terms are being prepared.

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.

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.

The intended policy is that you retain ownership of your own code and lead your project. Your repository is hosted under OpenRoot's organization with repository-level Admin for you. Organization owners retain administrative access. Final licensing and departure/transfer terms must be agreed before enrollment. Read the distinction between project rights and GitHub control.

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. No star target is announced; claims and final fulfillment terms are still pending.

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.

Include exact GitHub usernames or GitHub App names, their account type, purpose, target repositories and requested permissions. Every request needs review. Prefer scoped GitHub Apps to shared human credentials. Never put passwords, tokens or private keys in an application.

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; reward claims are closed. Account approval is separate from funded enrollment.

Initial 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: EUR 50-1,000 allowances for GPT, Claude, Gemini or Grok, with strict per-key budgets reported by OpenRoot. No quantity cap is announced; this does not mean unlimited spending or an automatic EUR 1,000 reward per person.
• More benefits coming soon.

These are third-party allowances, not credits transferred into your own model-provider account or official sponsorships. Permitted distribution, expiry, supported models, recipient eligibility and delivery terms must be finalized before issuance. Applications are accepted for review; reward claims are not open. These offers are not confirmed referral rewards. Explore the reward pool or read the full offer terms.

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

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.

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 currently uses its existing readbitstream address while OpenRoot's branding is applied.