Why your instance runs on PostgreSQL
SFTPGo's default data provider is SQLite, which is fine for a single machine and a handful of users. Every DANIAN-managed SFTPGo instance instead runs on PostgreSQL, for one practical reason: SQLite locks under concurrent access, and the lock issue is the most common production failure in self-hoste
SFTPGo's default data provider is SQLite, which is fine for a single machine and a handful of users. Every DANIAN-managed SFTPGo instance instead runs on PostgreSQL, for one practical reason: SQLite locks under concurrent access, and the lock issue is the most common production failure in self-hosted SFTPGo, documented in the project's own issue tracker.
What it means for you: concurrent transfers, several admins clicking at once, and event rules firing in parallel all work without database lock errors, and user, folder, and rule management stays responsive under load. You do not manage the database; it is part of the managed instance, included in the plan.
If you are migrating from a self-hosted setup that hit SQLite lock errors, that problem does not follow you. Users, folders, rules, and settings import cleanly, and the transfer paths are unchanged.
