kaicorplabs.com / for teams

03 In your organisation

Three ways to run these tools at work.

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

Run it yourself

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

Use our instance

The five 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

Have it deployed and kept running

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

Hesperia Labs

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 a deployment actually includes

  • Installation on infrastructure you own, or a tenancy you control.
  • Single sign-on against your existing identity provider — any standard OIDC one.
  • Backups, with a restore that has been tested rather than assumed.
  • Updates as new versions are released, applied deliberately and not automatically.
  • Somewhere to write when something breaks, and an agreed time to answer.
  • Changes to the tool itself, when what you need is close to what it does.

Beyond what is published

The five 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.

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.

Get in touch

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.