Databases 7 min read

The World's Most Widely Used Database Is Maintained by Just Three Developers

SQLite powers virtually every mobile app, browser, TV and car system, with an estimated trillion live instances, yet it is written and maintained by only three people who enforce a public‑domain license and a rigorous aerospace‑grade test suite.

Java Tech Enthusiast
Java Tech Enthusiast
Java Tech Enthusiast
The World's Most Widely Used Database Is Maintained by Just Three Developers

Origin and Early Development

In spring 2000 Richard Hipp was contracted by General Dynamics to write software for a U.S. Navy missile destroyer. The ship used Informix, which required a full system shutdown for each upgrade, so Hipp needed a database that could operate while the system was down. No suitable embedded database existed, leading him to write his own.

On May 29 2000 Hipp wrote the first line of SQLite code and released it publicly, expecting only a handful of downloads.

Adoption by Mobile Manufacturers

Motorola contacted Hipp shortly after release, requesting technical support to embed SQLite in feature‑phone firmware because existing databases were too large for the limited storage of those devices. SQLite’s implementation consists of a single C source file that can be compiled directly into an application, eliminating the need for a separate database server.

Following Motorola, Nokia, Apple (iPhone) and Google (Android) adopted SQLite, making it the de‑facto standard for embedded databases across smartphones, browsers, TVs, and automotive infotainment systems.

Public‑Domain Licensing

SQLite’s source code is placed in the public domain, unlike permissive or copyleft licenses such as MIT, Apache, or GPL. This means anyone can use, modify, or redistribute the code without attribution, fees, or notification.

The project does not accept external contributions unless the contributor signs an affidavit placing the contributed code into the public domain. The policy aims to avoid legal complications that could arise if a contributor retained any copyright.

Team Size and Code Base

The core development team consists of three people: Richard Hipp, Dan Kennedy, and Joe Mistachkin, distributed across multiple time zones. Over 26 years they have maintained SQLite, which now contains approximately 155,800 lines of source code .

Testing Infrastructure

SQLite’s test suite comprises roughly 9.2 million lines of test code , about 590 times the size of the source. The suite follows the DO‑178B standard used for aerospace safety‑critical software. SQLite achieves 100 % branch coverage and 100 % Modified Condition/Decision Coverage (MC/DC). Hipp stated in a SIGMOD interview that reaching 100 % coverage required a full year of twelve‑hour‑per‑day work.

The test harness, named TH3, is closed‑source and requires a paid license to view, providing a commercial revenue stream that supports the three‑person team.

Version‑Control System

SQLite’s source is stored in Fossil, a distributed version‑control system written by Hipp, rather than Git. This reflects the project’s independent tooling philosophy.

Recognition

In June 2026, at the Cesium Developer Conference in Philadelphia, Keith Bentley of Bentley Systems presented Richard Hipp with the Bentley Lifetime Achievement Award, acknowledging the impact of a database maintained by a three‑person team for over two decades.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

TestingSoftware HistorySQLiteEmbedded DatabaseFossil VCSPublic Domain
Java Tech Enthusiast
Written by

Java Tech Enthusiast

Sharing computer programming language knowledge, focusing on Java fundamentals, data structures, related tools, Spring Cloud, IntelliJ IDEA... Book giveaways, red‑packet rewards and other perks await!

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.