SQLite

SQLite is a strong fit for applications that need a local, transactional SQL database without a separate server. Its broad SQL support and zero-cost public-domain source make it a practical default for device-local storage; the one-writer-per-file ceiling is the key reason to choose another design for concurrent writes.

Overview

SQLite runs within the application that uses it, rather than as a database server, and needs no configuration. Its complete database resides in one cross-platform disk file, keeping local data storage self-contained. The project recommends it for device-local content below a terabyte when write concurrency is low.

Transactions are atomic, consistent, isolated and durable, including after system crashes and power failures. The source code is in the public domain and can be used commercially or privately without a license. SQLite is self-hosted; there is no managed service.

Key features

SQL in a compact engine

SQLite supports partial indexes, expression indexes, JSON, common table expressions and window functions. That range gives application developers substantial SQL capability without introducing a separate server process.

Concurrency and security

Unlimited simultaneous readers can access a database file, but only one writer can write at a time. Read-oriented applications can benefit from that concurrency; a workload that needs concurrent writes is a poor fit for the per-file limit.

SQLite is extensively fuzz-tested. For applications that accept untrusted SQL, its security guidance recommends defensive settings and lower input limits. The maker also offers a free public forum, alongside paid private email and technical support.

Pricing

The SQLite engine costs nothing, for any purpose, with no license required. The core includes an embedded SQL database engine and has no separate server process. There are no seat or usage charges stated for this plan.

Paid options add support, extensions or licensing terms:

• 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, then decompresses and decrypts it on read.
• SQLite License: $6,000, paid once for a warranty of title and perpetual right to use the SQLite source code.

The free engine is sufficient for users who need the database itself; paid choices are relevant when support, particular extensions or the stated license terms matter.

Platforms

SQLite is available across Android, iOS, Linux, macOS and Windows, as well as through API, web and self-hosted deployments. Downloads include source code and precompiled binaries for Android, Linux, Mac OS X and Windows, plus WebAssembly and JavaScript bundles for web applications.

Who it's for

SQLite suits developers building local-first applications, device storage or other systems with modest write concurrency and less than a terabyte of content. Its single-file format and in-process operation keep the database close to the application. It is less suitable when one database file must accept writes from multiple clients simultaneously.

Pros and cons

• Pro: The database is self-contained in one cross-platform file, with no server process or configuration to manage.
• Pro: Its SQL feature set includes JSON and window functions, alongside transactions designed to remain durable through crashes and power failures.
• Pro: The core is free for commercial and private use without a license.
• Con: Each database file allows just one writer at a time, limiting its fit for write-heavy, concurrent workloads.
• Con: It is self-hosted and has no managed service, so it does not provide a managed database option.

Alternatives

For a different database model or deployment, consider MySQL, Firebird, H2 Database Engine, MariaDB Server, Neon, PostgreSQL, Aiven for PostgreSQL and InterSystems IRIS.

MySQL is worth considering for a free-plan database with replication and high-availability components; its Community Edition is GPL-licensed. Firebird offers a free SQL database with no fees for download, registration, licensing or deployment, including commercial distribution. H2 Database Engine is free to use and includes its source code. MariaDB Community Server is free, GPLv2-licensed and self-hosted for non-production applications.

Neon may suit readers seeking a hosted free tier: it includes 10 projects, 50 CU-hours per month per project, 0.5 GB storage per project, 10 branches per project and 5 GB monthly egress. PostgreSQL is a free, open-source option that can be used, copied, modified and distributed without a fee. Aiven for PostgreSQL offers a free single-node tier with 1 CPU, 1 GB RAM and 1 GB disk, but no support services. InterSystems IRIS is another option, with a free Community Edition; AWS infrastructure costs may apply.

Verdict

Choose SQLite for embedded, device-local SQL storage when a self-contained file, robust transactions and zero-cost commercial use matter more than simultaneous writes. Look elsewhere if the workload requires multiple writers on the same database file or a managed database service.