governance & transparency
This page describes the project's structure, funding, infrastructure, and policies. It exists so that anyone using Odyssey knows exactly what they are installing — and who is behind it.
policy · 01 · project structure
Odyssey Linux is maintained by one person, working under the pseudonym "nobody". There is no company, no foundation, no legal entity behind the project. There is no team. There are no employees, contractors, or volunteers with administrative access.
This is a deliberate choice for the current phase of the project, not an ambition. The project is tied to me, and only to me. If I disappear, the project slows down. I am telling you this because you deserve to know.
policy · 02 · funding
Odyssey is funded exclusively through direct donations from individual users. Donations are received and managed by me, personally. There is no organization in the middle, no fiscal sponsor, no payment processor running a foundation.
Donations are used to cover concrete project costs:
Nothing else. No salaries to non-existent employees. No marketing budget. No conferences.
policy · 03 · sponsorship
Odyssey will never accept corporate sponsorship, in any form. This is a hard rule, not a current preference.
The only acceptable form of financial support is donations from the people who actually use the system. If a company wants to support Odyssey, they can donate as individuals, with no acknowledgement and no influence.
policy · 04 · financial reports
Starting from the project's first full year, Odyssey publishes an annual financial report covering total donations received and how they were spent. The report is public, simple, and not audited by anyone — it is published on trust, like the rest of the project.
financial reports
First annual report: 2026.
no reports available yet — the project is in its first year
policy · 05 · code & repository
The Odyssey source code lives on a self-hosted Forgejo instance at code.odysseylinux.org. Self-hosted, not GitHub, not GitLab — because the project insists on controlling its own infrastructure.
If the project ever stops, the code remains. Anyone can take it and continue.
policy · 06 · signing keys & infrastructure
Package integrity matters. The keys that sign Odyssey's xbps packages are kept offline, on dedicated hardware separate from the build server. They are never present on the build infrastructure during normal operations. Signing happens on isolated hardware; signed packages are then transferred to the public repository.
The infrastructure is minimal by design:
fail2ban and minimal exposed ports on all servicesIf the build server is ever compromised, the procedure is straightforward: revoke the affected keys, rebuild and re-sign all packages from offline keys, publish a public advisory.
policy · 07 · privacy
Privacy is not a feature added to the system — it is a precondition.
odysseylinux.org) runs no analytics, no cookies, no third-party scripts — what you see is what is loadedpolicy · 08 · continuity
Right now, if I disappear, Odyssey disappears with me. The signing keys, the build procedures, the server credentials — all of it is held by one person.
I am working on building a structure that survives me — succession of signing keys, documented build procedures, a small group of trusted people with revocation power, a clear handover path. This is a priority. It is not done yet.
Until that structure exists, the realistic outcome of my disappearance is this: the source code remains public on Forgejo and can be forked by anyone. The ISOs already released continue to function — they are built on Void Linux, which is maintained independently. New Odyssey releases would stop until someone else picks the project up.
I am telling you this because you deserve to know.