What it is and why it exists
The Foundation operates a pass-through access service for users who cannot easily set up their own AI provider relationships. The service is one of the Foundation’s operational functions, not a separate organization and not a commercial entity. It exists for a specific structural reason and operates under five public principles that constrain what it can drift into.
Public-domain release of the architecture is the primary commitment. Without a working access path, that release is partially defeated. The architecture is free; the model relationships that make the architecture useful are typically not. A user who installs Ora and has nothing to connect it to does not, in any operationally meaningful sense, have access to the technology the Foundation has released to the public domain. The access service closes that gap for the populations the gap most affects.
Many of the people who would benefit most from Ora cannot easily obtain AI provider accounts of their own. They may not have credit cards that work with US payment processors. They may not be able to manage API keys and rate limits. They may be displaced workers without the technical sophistication to manage provider relationships. They may be in developing markets where AI provider accounts are difficult to obtain. They may be working under non-disclosure constraints that make individual commercial-provider accounts complicated. They may simply prefer to deal with the Foundation rather than with a frontier lab whose business practices they want no part of.
The access service is the operational complement to public-domain release. The architecture is free, and the access pathway through the Foundation is free of friction beyond actual cost. This is what makes the public-domain commitment honest in practice rather than only in form.
The five operational principles
The access service operates on five principles that are stated publicly and reviewed by the board annually. The annual review with public comment is the discipline that keeps the principles operative — they are not stated and forgotten; they are the basis on which the service’s operation can be evaluated by anyone.
Pure pass-through. Users pay actual provider costs at the prices the Foundation pays. The Foundation does not mark up provider costs. If the Foundation pays a frontier lab $0.10 for a query, the user pays the Foundation $0.10 for that query. There is no margin on the underlying model usage. This is the most load-bearing principle and the one that distinguishes the access service from any commercial AI reseller.
Capped administrative fee. A minimal administrative fee covers infrastructure costs only — server operations, account management, payment processing, the small amount of staff time the access service requires. The fee is publicly published. It is capped at a level that just covers operations. Initial estimate: $1–2 per active user per month. The fee is reviewed annually with public comment, so any change to the cap is visible and contestable before it takes effect.
The administrative fee is the only revenue the Foundation receives from the access service. It is not calibrated to user value, not calibrated to ability to pay beyond cost recovery, not calibrated to the price the market would bear. It is calibrated to operations cost.
No revenue to the Foundation beyond administrative cost recovery. The access service is not a fundraising mechanism. Revenue from the service balances against operating costs. Surplus, if any, is treated under the Foundation’s general reserve and endowment policies rather than as discretionary funds. The Foundation does not set the administrative cap at a level designed to produce surplus and does not adjust pricing to extract additional revenue from access service users beyond what operations require.
This principle is what prevents drift. Without it, an access service that begins as cost recovery becomes, over time, a revenue source the Foundation depends on, then a revenue source the Foundation grows, then a revenue source whose growth is the operational priority. With it, the access service stays small, stays cost-aligned, and stays subordinate to its purpose.
No special Foundation-favored status for any provider. The Foundation routes user requests to providers based on user choice, cost, capability, and availability. The Foundation does not preferentially route to providers who offer better commercial terms to the Foundation. A frontier lab cannot pay the Foundation, in any form, for preferred routing through the access service. Provider relationships are evaluated on the user’s interest, not the Foundation’s.
This is the equivalent in the access-service context of the donor-screening provisions that prevent commercial AI companies from buying influence over Foundation programs. The principle prevents the access service from becoming a soft commercial channel for any particular vendor.
Competition welcomed. Anyone can run their own Ora instance with their own provider relationships. Anyone can offer competing access services. The Foundation provides one path among many; the existence of a public-domain accessible path does not depend on the Foundation’s continued cooperation with anyone. Competition is itself a protection against organizational drift: if the Foundation ever raises prices beyond costs, users migrate to competitors, and the migration both signals the drift and corrects it.
The five principles compose. Pure pass-through plus capped administrative fee plus no-surplus-as-fundraising plus no-favored-provider plus competition-welcomed produce an access service that cannot grow into something else without explicitly violating one of the five public commitments.
Legal architecture
The access service is structured as a managed-services arrangement rather than a reseller relationship. Users have direct relationships with AI providers through the Foundation’s infrastructure. The Foundation does not own or claim to own the AI capability being accessed.
This distinction matters operationally. As a managed-services arrangement, the Foundation is the infrastructure layer between the user and the provider; the provider’s relationship is with the user, governed by the provider’s terms; the Foundation’s role is operating the infrastructure that lets the user reach the provider without setting up the provider relationship themselves. As a reseller relationship, the Foundation would be acquiring AI capability from providers and selling it to users, which would put the Foundation in the position of being the merchant and would create commercial complications the Foundation explicitly does not want.
The managed-services structure also keeps the Foundation out of the position of claiming AI capability it did not produce. The Foundation does not produce models. It does not own model outputs. It does not warrant that a model will produce any particular output for any particular query. The provider does what the provider does; the Foundation provides the conduit; the user pays the actual cost plus the small administrative fee.
Specific legal mechanics — terms of service, data handling, payment processing, dispute resolution — are post-incorporation work to be drafted by the Foundation’s attorney against the operational principles above. The principles constrain what the legal architecture can be; the attorney’s work is to encode the principles in language that holds up in the relevant jurisdictions.
Pre-incorporation operation
The access service launches before the Foundation is incorporated. During the pre-incorporation period, the service operates under the founder’s name with transparent framing about the eventual transition. Users know, when they sign up, that the service is currently a personal operation that will transfer to the Foundation when the Foundation exists.
This is not a workaround. It is the right way to operate during the period when the Foundation is being built. The need for the access service exists immediately — the disruption that motivates the Foundation begins immediately, and the populations who need a pass-through access path need it now, not after the Foundation’s incorporation paperwork has worked through state and federal review. The founder can operate the service, with the same five principles publicly stated, and transfer it to the Foundation when the Foundation is ready to operate it.
The transparent framing matters for two reasons. It tells users what they are signing up for and what will happen, so the eventual transition is not a surprise. It establishes, by public commitment in advance, that the founder is not building a personal commercial product under the Foundation’s eventual name; the service is the Foundation’s by intent from day one and is operating under the founder’s name only because the legal vehicle does not yet exist.
The five operational principles apply to the pre-incorporation operation in the same form they will apply post-incorporation. Pure pass-through, capped administrative fee, no surplus, no favored providers, competition welcomed. The founder’s personal operation is not a different service that will be replaced by the Foundation’s service; it is the same service, operating under the same principles, with a legal-vehicle change at incorporation time.
What the access service is not
Not a commercial product. The access service does not have a marketing budget, a sales team, a customer-acquisition strategy beyond making its existence known to users who would benefit from it. The Foundation does not promote it as a product. It is operational infrastructure for the public-domain release; it is announced when users need to know it exists, and not promoted further.
Not a profit center. The access service does not produce revenue beyond cost recovery, and the Foundation does not seek to make it produce revenue beyond cost recovery. The administrative fee is set to cover operations, not to fund the rest of the Foundation’s work. The Foundation’s operating budget is funded through donations and grants under the standard nonprofit pattern; the access service is not the funding mechanism.
Not a technical-sophistication gate. The access service exists precisely so that users do not have to manage their own provider relationships in order to use Ora. A user who can manage their own provider relationships is welcome to do so and is welcome to bypass the access service entirely; a user who cannot, for whatever reason, has the access service as a path. Either path is supported equally by the architecture.
Not the only path. The Foundation does not steer users toward the access service over local or self-managed alternatives. Local open-weights models running on the user’s machine are encouraged; user-managed provider accounts are encouraged; alternative access services run by other organizations are welcomed. The Foundation’s access service is one path among many. The architecture is designed so that no path requires the others, and the user’s choice is the user’s.
Not a reseller business. The legal structure is managed services, not reselling. The Foundation does not acquire AI capability and sell it. The Foundation operates infrastructure that lets users reach AI providers more easily than they could on their own. The distinction is what keeps the Foundation out of the commercial AI business while still serving the access need.
Not a vehicle for influence. The Foundation does not use the access service to gain leverage over providers, does not negotiate preferential access for the Foundation’s own use, does not accept inducements from providers for any form of preferential treatment in routing or display. The five principles are the architectural constraint that prevents the access service from becoming an influence vehicle.
The summary
The access service is the operational complement to public-domain release. It is one of the Foundation’s functions, not a separate organization. It exists because the populations the Foundation specifically commits to serving include users who cannot easily set up their own AI provider relationships, and without an access path those populations are excluded from what the public-domain release is meant to make available.
Five operational principles, publicly stated and annually reviewed: pure pass-through with no markup on provider costs; capped administrative fee that covers operations only and is publicly published; no revenue beyond cost recovery; no favored-provider status for any commercial actor; competition welcomed because the existence of accessible alternatives does not depend on the Foundation. The five principles compose into an access service that cannot grow into something else without explicit violation of public commitments.
Legal structure is managed services rather than reselling — users have direct relationships with providers through Foundation infrastructure. Pre-incorporation, the service operates under the founder’s name with transparent framing about transition. Post-incorporation, the service operates as a Foundation function under the same five principles.
The access service is one path among many, deliberately. Local models, user-managed provider accounts, and competing access services from other organizations are all part of the ecosystem the Foundation expects and supports. The Foundation’s path is the one that exists for users who could not otherwise easily reach the technology, operated under the discipline that keeps it from becoming anything else.