Independent software studio

A small studio building useful software.

We build for engineers, creatives, homeowners, and the software agents working alongside them. The range is wide, but the bar is the same: clear, reliable, structured.

How we work

Focused products. One small studio.

Nubisco is small on purpose. We pick problems we use ourselves, ship in the open where we can, and resist the pressure to be everything to everyone. Every product has to earn its place in the lineup, and the license we choose for it has to match what it actually is. Open where it earns trust, commercial where it earns a living.

What we believe

Principles over process.

Simplicity is earned

Making something simple is harder than making it complex. We take the time to get the interface right.

Reliability over speed

We ship conservatively. A stable release you can count on is worth more than a fast release you can't.

Honest about what's open

The tools you build on are open source, so you can read what you run. Our products are commercial, and we say so plainly. No vague open badge over a closed core.

Agent-ready by design

Where it makes sense, products expose explicit, auditable interfaces so software agents can use them safely alongside humans.

No hype

We don't make claims we can't back up. If something works well, we show you, we don't tell you.

How we license

Open where it earns trust, commercial where it earns a living.

Libraries are MIT. Verba is open-core: a self-hostable AGPL community edition alongside a managed cloud. OpenBridge and its plugins are MIT. Our commercial products are closed source, because selling them is how we keep the lights on. A few services ship under the Business Source License (BUSL) and convert to Apache 2.0 after a published change date. We are precise about which is which on every product page, and the LICENSE file in each public repo is authoritative.

View on GitHub

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.