SQLite vs turbopuffer

Yes, SQLite is open source and in the public domain. The complete source code and binaries are free to download and use for any purpose without restrictions.

There is no open source or community edition. Single-tenant and bring-your-own-cloud deployments exist as commercial arrangements, but there is no way to run it independently of the vendor.

SQLite is a self-contained, serverless SQL database engine that reads and writes directly to disk files. It requires no separate server process and runs within your application, making it ideal for embedded systems and local storage.

Warm queries perform comparably to in-memory search engines. Cold queries, where data is not cached, have a documented p90 around 1,214 ms on a million documents. Write p90 is around 248 ms for a 512 KB upsert because writes go straight to object storage.

SQLite does not support true multi-user concurrency. Only one process can write to the database at a time, and it lacks user management and access control features. It is designed for small to medium projects, not enterprise applications with many concurrent users.

Eventually consistent by default, with the vendor reporting that over 99.8% of queries return consistent data. Strong consistency can be requested per query at a latency cost. Large write bursts have a longer visibility delay while indexing catches up.

SQLite can work for single-server web applications with modest concurrency needs. However, it lacks features like user management, granular security, and sophisticated query optimization needed for large-scale applications.

Large numbers of namespaces where most are idle. The architecture makes cold data cheap to keep, which is exactly the shape of a multi-tenant product with a long tail of inactive customers.

Up to 128 billion documents and 256 TB per namespace, 500 million documents per shard, 64 MiB per document, 10,752 dense vector dimensions, roughly 10,000 writes per second per namespace and a maximum result set of 10,000.