Built in the open.
We believe software you can read is software you can trust. Most of what we ship is open source, the rest is source-available or source-published, and everything we make is documented, inspectable, and built to outlast us.
Why open source
Transparency is a feature.
Open source isn't just a licensing choice, it's a commitment to the community. When you can read the code, inspect the decisions, and contribute fixes, you're not dependent on us to keep things working. That's how software should be.
Licence reference
What ships under which licence.
Each product page goes deeper. This is the quick view of which bucket every project sits in.
- Nubisco UIMITGitHub ↗
- Verba CEAGPL-3.0Coming soon
Get involved
Contributions welcome.
Found a bug? Have an idea? Pull requests are open. We review contributions seriously and maintain a respectful, focused community.
Read the code
Browse the repo, understand the architecture, check the open issues.
Open an issue
Describe what you want to fix or build. We'll discuss the approach before you start.
Send a PR
Keep it focused. One thing per pull request. We'll review it promptly.
Licensing
Open by default, fair by design.
Our libraries and shared foundations are MIT-licensed: free to use, fork, and deploy. Our open-core applications ship a self-hostable community edition under copyleft (AGPL-3.0), alongside commercial or managed editions that fund continued development. Some products are source-available rather than open source: the code is public so you can read, audit, and build it for personal use, while commercial use requires a paid licence. A small number of services are released under the Business Source License (BUSL), which becomes Apache 2.0 after a published change date. Every product page, and every repository's LICENSE file, tells you exactly which bucket that product is in.
View on GitHub