Yep! That was one plan for deploying cr-sqlite to "the cloud."

D1, unfortunately, doesn't support loading extensions into SQLite.

fly.io, and their sqlite solution, does however!

I've been using fly.io to run cr-sqlite in the cloud and act as a sync server for non peer to peer use cases. Eventually I'll have finished up a re-write of strut.io[1] atop vlcn/cr-sqlite which'll serve as a good end to end example of how to make applications with this sort of architecture.

Some discussion about this setup on the fly.io forums: https://community.fly.io/t/litefs-many-tens-to-hundreds-of-t...

[1] https://github.com/tantaman/strut

D1 is eventually consistent so better not use it with that. I'd rather use Durable Objects

I believe that the entire point of using CRDTs in your database is eventual consistency. (At least, to some degree. The definition/requirements of "consistent" may change from app to app.)