Why SQLite should not be used in production

SQLite is supported by Strapi and is well suited to local development, testing, and proof-of-concept work. However, it is not recommended for production Strapi deployments, and we do not encourage using it in live environments.

SQLite is an embedded, file-based database, designed to be tightly coupled to a single application process with a very controlled operational model. Strapi, by contrast, is a long-running server application with concurrent admin usage, API traffic, background jobs (such as cron tasks and webhooks), and regular restarts during deployments. These characteristics introduce operational risks that SQLite is not designed to handle.

In production, SQLite’s file-based architecture can lead to locking and write contention as real-world usage increases. Overlapping admin actions, API requests, and background tasks can result in slow responses, timeouts, or failed writes. These issues are often intermittent and difficult to diagnose once a system is live.

There is also an increased risk during restarts and deployments. Because all data is stored in a single file, crashes, abrupt restarts, or infrastructure interruptions can leave the database in an inconsistent or corrupted state—particularly in containerised or managed hosting environments.

Finally, SQLite lacks the operational robustness expected of a production data store, including mature tooling for backups, recovery, monitoring, and long-term maintenance. While workarounds exist, they add complexity and fall outside supported Strapi usage.

Recommended approach

For production deployments, Strapi recommends using a server-based relational database, such as PostgreSQL (recommended) or MySQL/MariaDB. These databases are designed to handle concurrent workloads reliably and support stable operation over time.

SQLite should be limited to:

• Local development

• Automated testing

• Proof-of-concept or demo environments

If your production environment is currently using SQLite, we strongly recommend planning a migration as early as possible. Please contact support if you need guidance—we’re happy to help.