SQLly is going source available, and where I want it to end up

SQLly's desktop source is coming to GitHub under PolyForm Small Business. What source available means, how it differs from open source, and the plan to open the client.

By

The source code for the SQLly desktop app is going up on GitHub soon. You will be able to read it, build it, change it, and send patches. Each release will land there as a snapshot, tagged to match the version you download from this site.

It will be source available, not open source. Those two phrases get used as if they meant the same thing, and they don’t, so this post explains the difference, why SQLly starts on the source-available side, and where I want it to end up.

What “open source” actually means

“Open source” has a specific definition, maintained by the Open Source Initiative. Being able to see the code is not enough. An open source license has to let anyone use, change and redistribute the software, for any purpose, without singling out any person, group or field of work. The MIT, Apache 2.0 and GPL licenses all meet that bar. A license that says “free, unless you’re a large company” does not, however generous it is to everyone else.

“Source available” is the broader, looser term: the source is published and you can read it, but the license puts some limit on who can use it or how. That is where SQLly starts. I would rather use the accurate label than borrow a term the software doesn’t meet. Calling something open source when it isn’t is a habit I’ve watched annoy a lot of developers, and they’re right to be annoyed.

Open sourceSQLly’s source-available license
Read the codeYesYes
Build it yourselfYesYes
Change it and share your changesYesYes, under the same license
Use it free at any company sizeYesNo: free under 100 people and USD 1M revenue, plus personal, educational and non-profit use
Meets the Open Source DefinitionYesNo

The license SQLly will use

The desktop app’s source will be offered under two licenses, and you use whichever one applies to you:

  • The PolyForm Small Business License 1.0.0, free. It covers companies with fewer than 100 people and less than USD 1M in revenue. I’m adding a grant on top that also covers personal and hobby use, teaching and study, and registered charities and non-profits of any size.
  • A commercial license for everyone else. Any paid SQLly plan is that license, whether you bought it on the pricing page, in the Mac App Store or in the Microsoft Store.

What goes public is the desktop app, sqlly-cli, the browser build, and the core libraries under them: the database engines, IntelliSense, the SQL language crates and the wire protocol. The hosted pieces stay private: the bridge, the relay behind Cloud Relay, and SQLly Embedded. The SQLly name and logo aren’t licensed for your own builds, so a fork has to go by another name.

I’m a big fan of open source

I want to be plain about this, because a license with a revenue line in it can look like the opposite. Nearly everything SQLly stands on is open source: Rust, the GPUI framework that draws the interface, the database drivers, the parsers, the TLS stack, and hundreds of crates written by people I’ll never meet. My own results grid, sqlly-datatable, is published openly for the same reason. I have spent my whole career reading other people’s source to understand what my code was really doing, and a tool you can’t read is a tool you have to take on faith.

A database client is a particularly good case for that. It holds your connection strings and passwords, and it sits between you and production. You should be able to check what it does with them, not just take my word for it.

Where I want this to end up

My long-term goal is to make the SQLly desktop app fully open source, and to earn a living from the parts that are actually a service: the cloud features, like Cloud Relay and team sharing, and the enterprise features, like SQLly Embedded and what large teams need on top of it. Those cost money to run and support, and charging for them is a fair trade. The editor on your own laptop shouldn’t have to be the thing that pays the bills.

I’m not there yet, and I’d rather say so than promise a date. SQLly is built by one person, and today the desktop licenses are what keep it going. The cloud and enterprise features are still being finished. Once they are ready, and they can carry the project on their own, I intend to move the client to an open source license. Source-available is the step I can take now without betting the project on it.

The setup is designed to keep that door open. Contributions come in under a short contributor agreement in which you keep your copyright and give the project permission to license your code under other terms. That’s what makes a later move to an open source license possible, without tracking down every contributor to ask.

What changes for you

  • If you use SQLly today, nothing changes. Your license works as it did.
  • If you’re curious how something works, you’ll be able to read it: how IntelliSense ranks completions, how results stream to disk, how the read-only guardrails classify a statement.
  • If you find a bug, you’ll be able to send the fix, not just the report.
  • If you care about security, you can audit the code that touches your credentials. The protocol between the app and the bridge relies on published cryptography and keys held on servers, not on keeping the code secret, so publishing it doesn’t weaken anything.

I’ll post again when the repository is live, with the link. If you have questions about the license, or whether it covers you, email [email protected].