Sponsorship
Support the project.
Olivares AI is open source and self-hosted: the core is free and stays free, and nothing in it is held back to be sold later. If it is useful to you, sponsorship helps sustain the work that keeps it that way — the development, the integration of every agent surface as it changes, and the signed, verified releases.
What it sustains
Where sponsorship goes
Development
The platform itself — the work plane, the enforcement points, the console, the connectors — built in the open, one verified piece at a time.
Integration
Agent surfaces change often. Keeping Claude Code, Codex, Grok Build and the rest integrated at the depth their tools allow, and saying plainly what each one can enforce and what it can only observe, is continuous work.
Releases you can verify
Signed archives, packages and images, with SBOMs and build provenance, published from infrastructure the project pays for. That infrastructure is concrete: the CI runners that build and sign every release, the domains, and the signing and verification chain.
Documentation
Product documentation and the README in several languages, kept true to the code — including the page that says what the product does not do.
How it works
One channel, no strings attached
Sponsorship runs through GitHub Sponsors — on the project organisation, or on the maintainer’s profile for those who prefer a personal page. Ko-fi is a secondary channel for one-off support. Sponsors who ask to be named are listed in the repository; a sponsor who prefers not to be named is thanked all the same.
Plainly
What sponsorship is not
-
Not a support contract
It buys no priority: questions and bug reports are handled the same way for everyone. A project that lets sponsorship buy queue position stops being predictable for everyone who does not pay.
-
Not a commercial license
Commercial terms and the optional add-ons are a separate matter, described on the pricing page and in the repository’s licensing document.
-
Not a way to change what is open
The AGPL build is the whole platform. Sponsorship funds keeping it that way; it never buys a feature out of the open product.
No mandatory telemetry and no control-plane egress by default; sponsorship changes none of that, and the page that says what the product does not do stays public. What the product does not do
If it is useful to you, that is enough of a reason.
Run it, read the code, and — if you would like to — help sustain it.