Self-hosting FAQ

Partly, by design. The agent layer (the MCP tool definitions, the setup and recipe skills, per-agent connection guides, and examples) is open source in the public billr-agents repo, MIT licensed.

The billr.cc platform itself (the app, the database, the MCP server implementation) is closed source. We may open more of it later, but only after a proper security audit; we're not going to ship that lightly given it handles client data and money.

Not today. Billr is a hosted service: your account, your data, and your invoices live in our infrastructure, and that's the only way to run it right now. There is no self-hosted or on-prem deployment path.

Billr agent tools operate on real client data, invoices, and sending: the kind of thing that needs auth, rate limiting, and scoping done once and done carefully, not re-implemented by every self-host. A hosted service lets us own that security work and keep improving it in one place. It's a deliberate tradeoff, not an oversight.

Everything in the agent layer: install the skills, wire up your own automations in your CLAUDE.md, and run your agent against your Billr account with your own API key. That code is yours to read, fork, and modify. It just talks to the hosted platform rather than replacing it.