Mattermost SQLite write concurrency limits for low-traffic production

Mattermost offers SQLite as an embedded database option, which can remove the cost of a separate PostgreSQL server for a low-traffic workload. Documentation describes SQLite as suitable for evaluation and small teams, while warning of write-locking contention under concurrent write loads. PostgreSQL remains the only recommended production database for high availability, and no official guidance quantifies a maximum safe user count or message rate for SQLite.

The goal is to determine whether SQLite can safely serve a small, low-traffic production deployment without a separate database instance, given the absence of defined concurrency limits.

• What concurrent write volume or active user count represents the practical boundary for SQLite-backed Mattermost before write-lock errors become likely?
• Is SQLite officially supported for production use in single-server, low-traffic deployments that do not require high availability?
• What backup and migration constraints should be evaluated before choosing SQLite over PostgreSQL for cost reduction?