kaicorplabs.com / for teams
03 In your organisation
Everything here is open source and free to run yourself — that is the point, and it does not change. What follows is for when a team needs one of these tools and has to answer to someone about where the data lives.
Option one · free
Every service publishes a container image built by CI from a tagged commit, scanned for known vulnerabilities before release and shipped with provenance and an SBOM. Pull it, point it at your identity provider, and it is yours — no licence, no seat count, no call with us. Each project page has the exact command.
Option two · by invitation
The six services we run are open to people we approve one at a time. Fine for individuals and small groups who trust us with what they store. It is not sold, has no uptime guarantee, and we would not recommend it for anything your organisation depends on.
Option three · commercial
On your own servers or your own cloud tenancy: installed, integrated with your identity provider, backed up, monitored and kept up to date as new versions ship. The data never leaves your infrastructure — which is the entire reason most teams end up here.
Who does it
The commercial work is delivered by Hesperia Labs, which builds local-first infrastructure for organisations that cannot send sensitive data to a third party. Same principle as everything on this site, with a company, a contract and a response time behind it.
What happens after that is a conversation, not a package. Some teams take the keys and run it themselves — that is a perfectly good ending, and the reason everything here is open source. Others would rather we kept it updated as new versions ship, and had somewhere to write when something breaks. That part is agreed per engagement, with a response time written into the contract rather than advertised on a page.
The six tools ship as a single instance on SQLite because that is the right shape for a homelab or a team — a deliberate choice for how they are published, not a ceiling we ran into. A larger deployment gets the architecture it needs: a different database, work split across machines, redundancy, whatever the load and the audit actually require. The published code is where we start from, not where we stop.
That work happens here first. These six tools run on our own hardware, on the same images, the same compose files and the same deploy-and-roll-back procedure we would hand you — so when something needs to change, it gets built and broken and fixed on our machine before it goes anywhere near yours. A deployment on your servers is not a first attempt at a new shape; it is the shape we already run.
And this portfolio is not a catalogue. If what you need is one of these with real changes, an integration with systems you already run, or a tool that does not exist here at all — that is ordinary work for us. Ask.
Tell us which tool, roughly how many people, and what constraint you are working under — a regulation, an audit, a data residency rule, or simply not wanting your files on somebody else's server. Write to contact@kaicorplabs.com and a person reads it.
