A small house, built in the open
CodigoSH is a free-software collective focused on self-hosted, private and well-crafted tools. We make a few of them, we look after them for years, and we publish everything.
We think the software you depend on should be readable, runnable on your own hardware and small enough to understand. So that is the only kind we make.
What we believe
Six commitments
Privacy by default
Your data is yours. Nothing we ship reports back to us, there are no accounts to create to use what you run, and you can read the code that proves it.
Open source
All our work is public and auditable on our own forge, under Apache-2.0. Read it, fork it, run it, study it.
Quality over quantity
Few projects, crafted in detail and seriously maintained. A tool is worth adding when we can look after it for years.
Small and fast
A single binary or a container, light enough for a Raspberry Pi. We would rather remove a dependency than add one.
Easy to leave
Your data sits in one SQLite file you can copy, and where a tool offers an export it is an open, documented format. Trying a tool costs you nothing, and leaving it costs little.
Plain language
Documentation written for the person installing it, audited against the code, and fixed when it turns out to be wrong.
What we will never do
A promise you can check
- ×Phone home, or collect anything about how you use a tool
- ×Ask you to create an account just to run what you installed
- ×Depend on a third-party cloud to work
- ×Sell a paid tier, show ads or hold features back
- ×Change the terms: the licence is Apache-2.0 for every project
- ×Load anything from outside on this website
How we work
Four things that do not change
- Open code, small team
- Every line is public to read, run, fork and study. Development happens inside the team, which keeps the products coherent; questions, problems and ideas from anybody are welcome on the support desk.
- Our own forge
- The code, the releases and the container images live on our own forge, not on a platform that owns the relationship with you. Nothing about a project depends on a third party staying friendly.
- Self-funded, in public
- There is nothing to buy and no plan to sell anything. What little it costs is paid by the team and by donations, and the finances are public on Open Collective.
- Documentation next to the code
- Each project's documentation lives in its own repository and is published here from it at every build, so a page can never be older than the release it describes.
How a release reaches you
Nothing in between
- 01Built in the openThe change lands in the project’s repository, where anyone can read it.
- 02Checked before it shipsThe tests and the analysers run before a release can be tagged.
- 03SignedThe release comes with checksums signed by the project’s own key.
- 04Verified by youThe tools that update themselves check the signature before they replace anything.
Shipping, in the open
Every release of every project