Open where it runs. Hosted where it helps.
Every kit in the family is a library that runs inside your app, on the database you already operate. That code is open: yours to read, embed, self-host and fork. QuxCloud is the other half, the same software run for you, for when operating it yourself is not the point. Open core is simply the line between the two. The library is the product; the managed service is the convenience.
The library is the product. The service is the convenience.
Open core is not a teaser build with the good parts removed. The open libraries are the whole thing. What we run in QuxCloud is the same code, plus the operating of it. Three commitments hold that line honest.
The kits install as packages and run on your own Postgres. Nothing phones home, and there is no runtime dependency on us. Clone it, read every line, change what you need.
The schema and the data are yours. The exit is a technical task you control, never a contract you have to escape. No lock-in is not a promise here; it is the shape of the thing.
Most of the family is Apache-2.0, free for any use, commercial included. A few pieces — billing-kit first among them (BUSL-1.1, each version converting to Apache-2.0) — carry a source-available licence so the work cannot be repackaged as a rival service, while you stay free to build your own product on top.
Run it yourself, or let us run it.
The same software sits behind both. You choose who operates it, and you pay us only when that someone is us, or when you intend to resell a protected kit as a service of your own.
Install the kits and run them on the stack you already have.
- Embed on the database you already run
- Self-host, fork and ship
- Read and audit every line
- Community support
The same kits, run for you: hosting, scaling, upgrades and a managed control plane.
- We operate it; you point your app at it
- Scales without your pager
- Upgrades and backups handled
- Support and SLAs
For offering a protected kit as a service of your own, or embedding it in a product you sell.
- A licence that fits your use
- Terms for the source-available kits
- A conversation, not a gate
- Direct support
Not sure which applies to you? If you are building a product and running it for your own customers, the open libraries cover you, free and without a conversation. You reach for QuxCloud only when you would rather not operate the infrastructure, and for a commercial licence only when you mean to offer a protected kit as a service in its own right. When in doubt, ask us. We would rather tell you it is free than have you wonder.
Start with the open kits.
Install one package and build. Host it yourself, or hand the operating to us when you are ready.