Our principles
Running our software means trusting code we wrote with your infrastructure, your data and, ultimately, part of your business. We don't take that lightly, and this page says plainly what we do — and deliberately do not do — with that trust.
You are our customer, not our source of data
Rilbo is designed on the assumption that your systems belong to you. We don't collect telemetry about how you use it, we don't send your project data back to us, and we don't require a connection to our services for your installation to keep working. There is no analytics script on this site either.
We don't host your projects, so we cannot read your tickets, profile your developers, train models on your work or count your keystrokes. This is not a policy that could quietly change in an update: the product contains no machinery for any of it.
Rilbo is not an AI service either. It bundles no model, runs no inference on our servers and makes no outbound AI calls to model vendors. Its MCP server is the boundary for an agent you bring — including an MCP-capable agent backed by a fully local model — while the tracker stays on your infrastructure. The MCP & agents documentation explains the tools and the independent controls available at that boundary.
Zero egress by default — proven, not promised
Rilbo makes no outbound network connection at all unless you explicitly configure a notification channel. No telemetry, no analytics, no update check, no licence activation. A fresh install, left alone, talks to nothing.
Plenty of software says something like that. What we can add is that we check it, on every single change. One check reads the source and fails the build if anything outside the five notification sinks can open a socket. A second starts the release image on a network with no route off it and requires an outbound connection to fail. Publishing a release image is gated on both, so an egress regression goes red before it can ship. The profile CI runs is the same one we ship you, in the same file — so you can run it that way too, and stop taking our word for any of it.
The network egress section has the full inventory: every destination, the exact hostnames so you can write a narrow allowlist instead of opening egress, and both no-egress deployment recipes.
Your installation does not depend on us
Rilbo runs on your infrastructure: one binary and one SQLite file, on a disk you control. Licences are small signed files verified offline against a key built into the binary — no licence server, no activation call, no phoning home to ask permission to keep existing. It works air-gapped, because nothing about it needs the network.
If we disappeared tomorrow, your installation would carry on untouched.
A licence is never a hostage
If a paid licence expires — or you simply decide to stop paying — Rilbo reverts to the free edition. Premium actions pause; nothing else happens. Your database is never locked, nothing is deleted, and rilbo export and rilbo backup work regardless of licence state. The full mechanics are on licensing & plans.
What we promise, we pin down
Vague reassurance is cheap, so where we can we turn a principle into a contract you can hold us to:
- The API stability promise says exactly what may and may not change under
/api/v1, and logs every correction. - The security page states the trust boundary and the threat model — including what Rilbo does not defend against.
- Releases are signed; the verification procedure lets you check a download before you run it.
If you find the product contradicting any of this, that is a bug, and we want to hear about it: [email protected].
Your infrastructure is yours. Your data is yours. Your work is yours. We think software vendors should behave accordingly.