The history of SQLite: From a battleship to the entire world
D. Richard Hipp created SQLite in 2000 to solve complex valve configuration problems on a battleship. Today, the engine powers over 4 billion smartphones and supports 2.5 billion WhatsApp users through a highly reliable, public domain architecture.
Richard Hipp worked as a contractor for Bath Iron Works on the DDG-79 Oscar Austin battleship. The ship’s software relied on an Informix database that failed whenever the server went down. This failure stopped the damage-control software from working. The mission required reliable data to isolate damaged pipes and manage valve locations. Hipp found that the problem was computationally complex because the general description of the valve configuration was NP-complete. He needed to use heuristics to find optimal solutions quickly. An algorithm would get stuck in an exponential search trying every valve combination. The battleship software had to function even if the vessel took battle damage.
He built a byte code engine and a compiler in 2000.
Motorola paid $80,000 as a one-time payment to integrate SQLite into a new cell phone operating system in 2001. This payment allowed Hipp to hire two additional developers. Since then, the engine reached over 4 billion smartphones. You know how many databases run on your phone.
AOL wanted SQLite for databases on their CD-ROMs. This request prompted Hipp to add a feature for creating temporary indexes on real tables. SQLite 3.0 was partially funded by AOL. Chrome holds 65.54% of the worldwide mobile browser share in April 2026. Safari holds 26% of the market. Together, these two browsers handle most mobile sessions. Chrome for Android and Safari for iPhone together account for roughly 86% of global mobile browser usage. WhatsApp uses SQLite to store messages for its 2.5 billion users. Each client hosts a local database for conversations to avoid downloading everything from the cloud. Every message for the 2.5 billion WhatsApp users passes through an encrypted SQLite database on their devices.
| Specification | Limit/Value |
|---|---|
| Maximum database file size | 281 terabytes |
| Production source code | 156,000 lines |
| Total test code | 92 million lines |
| Active databases | Over 1 trillion |
The engine implements ACID guarantees and full relational model support. It lacks many features found in enterprise databases like PostgreSQL, including materialized views and complete support for triggers. The library is included in Windows 10 and macOS installations. Most programming languages ship with built-in support for the library, including Python, PHP, and Ruby. Android and iOS devices use SQLite extensively. Each smartphone holds hundreds of SQLite database files. SQLite is a single cross-platform file.
The software is the most widely deployed database engine in existence.
The development team consists of exactly three people: D. Richard Hipp, Dan Kennedy, and Joe Mistachkin. They do not accept outside contributions from the public. Only invited developers who sign affidavits can submit code. This process prevents proprietary code from contaminating the public domain. The team works without venture capital or outside acquisitions.
The testing regime is massive. The team uses a massive suite of over 92 million lines of test code, including 2.4 million test cases and 248.5 million tests in a pre-release soak test, to ensure the engine stays reliable. There are over 600 lines of test code for every line of production code. This includes fuzz testing and simulations of power loss during write operations. The team achieved 100% branch coverage at the machine code level.
Airbus uses SQLite in the flight software for the A350 XWB aircraft family. This software meets the highest safety requirements for aviation. The developers plan to support the software through 2050. SQLite also runs in Tesla cars and handles metadata for Dropbox. SQLite is public domain.
How will the team maintain this scale as more machines join the network?