Your site is for people familiar with SQLite. Imagine a person, who knows about vtable, wal, vfs, json1, fts5 and even blockcachevfsd, reading your page. It is between AI slop domain parking and a targeted phishing campaign. The first reaction is either to report scam or block spam. 90% of your comments here do not discuss your project but give assurance sqlite name is not being used unlawfully. Back when it was just vector extension, it at least made some sense, but this new web page is a complete assault on anyone familiar with sqlite internals. Please tune your messaging! Currently your prized "sqlite" trademark is being used like "with a computer", left and right.
Just to clarify a point that seems to come up in several comments: we are backed by SQLite’s author, and we have explicit permission to use “SQLite” in the company and product names.
We believe SQLite on the edge is a major opportunity, and our focus is on building genuinely new features and infrastructure on top of it.
I understand your concerns about the license, but our goal was simply to prevent large corporations from taking our work, forking it, and offering it to their customers while we struggle to sustain development. We need to monetize our work in order to survive, though we do offer very generous commercial licenses for those who are interested.
Why not release the source under AGPL (where 'network use' counts as distribution, unlike GPL), and offer commercial licences for those who want more favourable terms?
The maintainer of libxml2, Nick Wellnhofer, will be moving all his future contributions over to an AGPL fork as corporate users of libxml2 were unwilling to contribute financially.
reply