Keith's right: "database on remote filesystem" is not the same thing as "remote database". Stock SQLite via the interfaces discussed in this thread get you the first option, which is likely to cause [problems]. If you want the latter, SQLite on a remote system with a remote DBMS API to manipulate it, you don't want any of the interfaces discussed in this thread so far. You want something like [BedrockDB], [rqlite], or [dqlite]. [problems]: https://www.sqlite.org/howtocorrupt.html [BedrockDB]: https://bedrockdb.com/ [rqlite]: https://github.com/rqlite/rqlite [dqlite]: https://dqlite.io/