The earlier GitHub-username-based builder referral plan is not an active rewarded scheme. The separate affiliate pilot below accepts applications for review from 14 October 2026; affiliate self-service reward redemption remains unavailable.
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. The application is open, and 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.
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.
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.
Affiliate terms and privacy version: 2026-10-14-affiliate-1. Apply at the affiliate page. Self-service signup requires owner approval, then email-code verification at the portal. A GitHub account or builder project is not required for affiliate-only participation. After approval, the portal provides a unique link and code. Affiliate approval gives no GitHub organization membership, builder badge, project access or private applicant data; building requires a separate application.
The builder submits one code with their first application. A link fills the code into the form without affiliate tracking cookies. Attribution is a claim until reviewed and attached to the approved builder account. The affiliate receives an additional 20% non-cash reward value on eligible rewards actually delivered during the builder's first 12 calendar months after builder approval. Builders retain 100% of their rewards. No commissions arise from signups, pending milestones, undelivered offers or other affiliate commissions. No self-referrals, duplicate identities, retrospective attribution to already-approved builders or fabricated activity. Disputes and mistaken codes need owner review; contact hello@openroot.dev before approval.
Example: an eligible delivered EUR 100 API allowance can generate EUR 20 of affiliate reward value. This is not cash or official provider sponsorship. Funded offers, delivery rights, valuation, currency, expiry and redemption must be agreed before issuance. Subscriptions and indivisible benefits need an agreed value; no fractional subscription or currency conversion is promised. This release has no spendable wallet, automatic issuance or open reward redemption.
Affiliates must clearly disclose their relationship when promoting OpenRoot, respect community rules and avoid spam or guaranteed-reward claims. There is no participation fee. Signup requires separate affiliate-terms and privacy acceptance, not a newsletter subscription.
Google Cloud privately stores name, email, promotion plan, consent and review records. Signup applications expire after 90 days through asynchronous deletion. Approval creates a separate active affiliate profile, code and portal account retained while participating; existing builder-account expiry is not extended. Resend processes transactional approval and sign-in emails. Necessary session cookies last up to eight hours; codes expire after ten minutes. Affiliates receive no identifiable builder list or private project details. Signup and portal pages load no site analytics. Request correction, closure or deletion at hello@openroot.dev; approved-profile closure and unresolved reward records need manual review. General privacy notice.