You'll need each sqlite db to be relatively small for this approach to work well. Probably well under 1gb. If you construct a clever way for many small sqlites to form a bigger whole, that could work really well! Is that along the lines of what you are thinking?

As an example, you could imagine each Notion document being a separate sqlite...

Good questions. I think that at the lowest level, the per document model is a nice abstraction to build on top of. But I have a lot of plans on the cloud side to make it easier to integrate into the rest of your backend and your existing dbs.

I also am thinking about adding partial replication to the SQLSync model which could enable storing multiple documents in the same database on the server side.

Lots of different ways to go with this in the future :)