SQLite

Overview

SQLite is an SQL database engine built into an application rather than run as a separate server. It is especially suited to developers adding structured, local storage to an app; its single-file design and broad SQL support are compelling, provided writes to each database remain low in concurrency.

Key features

Embedded, single-file storage

A complete database lives in one cross-platform disk file, and SQLite runs in-process without a separate server or configuration. That makes it a practical fit for device-local application data and avoids operating a database service. It is not a managed database offering: deployment is self-hosted.

SQL, transactions, and concurrency

SQLite supports partial indexes, expression indexes, JSON, common table expressions, and window functions, giving applications a substantial set of SQL tools. Transactions are atomic, consistent, isolated, and durable even after crashes or power failures. Unlimited simultaneous readers are supported, but a database file can have only one writer at a time. Read-heavy use can suit that model; applications requiring concurrent writes to the same file should look elsewhere.

Security and distribution

Downloads include source code and precompiled binaries for Android, Linux, Mac OS X, and Windows, along with WebAssembly and JavaScript bundles for web applications. SQLite is extensively fuzz-tested, and its security guidance recommends defensive settings and lower input limits when applications accept untrusted SQL. Those precautions matter to developers embedding the engine; fuzz testing is not a substitute for configuring an application carefully.

The source code is public domain and free for commercial or private use without a license. A free public forum is available, while private email and technical support are paid options.

Pricing

The core SQLite engine costs free, for any purpose, with no license required. This is the relevant option for most developers embedding the database; it includes the engine, not a separate server process.

Paid options are aimed at organizations needing support, extensions, or specific rights:

• SQLite Consortium Membership: $150 a year for premium enterprise support, on-site visits, proprietary extensions, and test suites.
• Technical Support: $885 a year for high-priority email and phone support; a guaranteed response time is available as an option.
• Annual Maintenance Subscription: $1,500 a year for private expert email advice from SQLite developers.
• SQLite Encryption Extension (SEE): $2,000, paid once for source code that reads and writes AES-encrypted databases.
• CEROD: $2,000, paid once for source code that reads compressed and encrypted databases.
• ZIPVFS Read/Write Compressed Database Extension: $4,000, paid once for source code that compresses and encrypts data on write and decompresses and decrypts it on read.
• SQLite License: $6,000, paid once for a warranty of title and perpetual right to use SQLite source code.

The free engine is sufficient for use without a license; the paid license is for buyers seeking its stated warranty and right-to-use terms. The support and extension purchases serve narrower enterprise or technical needs rather than changing the basic engine's free pricing.

Platforms

SQLite supports Android, iOS, Linux, macOS, Windows, web, API, and self-hosted use. Its downloadable binaries and web bundles give developers several ways to incorporate it, while the self-hosted model means teams manage deployment themselves.

Who it's for

SQLite is a strong choice for developers building device-local storage into applications, particularly where content is below a terabyte and reads are more frequent than writes. It is less appropriate for workloads that need multiple writers to a single database file at once, or teams seeking a managed database service.

Pros and cons

• Pro: The entire database is one cross-platform file, and the engine runs inside the application without a separate server or setup.
• Pro: Public-domain source code can be used commercially or privately without a license fee.
• Pro: Broad SQL support includes JSON, window functions, and common table expressions, alongside durable transactions.
• Con: Only one writer at a time can access each database file, which rules it out for some concurrent-write workloads.
• Con: There is no managed service; users must handle self-hosted deployment.
• Con: Private support, proprietary extensions, and specialized encryption or compression source code carry substantial paid prices.

Alternatives

Choose MySQL if you want a database with SQL and NoSQL applications, replication, and high-availability components; its Community Edition is GPL-licensed. InterSystems IRIS is another option with a free Community Edition, though AWS infrastructure costs may apply.

H2 Database Engine is a free database alternative with source code included. For a hosted PostgreSQL option with published free-tier limits, Neon offers 10 projects, 50 CU-hours per month per project, 0.5 GB storage per project, 10 branches per project, and 5 GB monthly egress on its free plan. MariaDB Server offers a free, self-hosted Community Server for non-production applications, while PostgreSQL is free and open source for use, copying, modification, and distribution.

Microsoft SQL Server is an alternative with freemium pricing and edition options. Aiven for PostgreSQL is a hosted alternative whose free plan includes one CPU, 1 GB RAM, 1 GB disk, a single node, and no support services.

Verdict

Choose SQLite for application-embedded, device-local storage when a compact, self-contained database and zero license cost matter more than simultaneous writes. Its capable SQL feature set and durable transactions make it useful well beyond trivial data storage, but the one-writer-per-file limit is decisive for write-heavy concurrency. If that constraint or self-managed deployment does not fit, choose another database model.