I've been thinking about this quite a bit recently. I want to start adding features where LLMS can help with data cleanup, but for that to be useful it will need VERY robust "undo" for if they make mistakes.
I've also had a lot of success using GitHub itself for versioned data. If your data is less than a GB (and each file is under 50MB) you can dump it out to a GitHub repo and use that to track changes over time.
I wrote up one of my explorations here: sqlite-history https://simonwillison.net/2023/Apr/15/sqlite-history/
I've also had a lot of success using GitHub itself for versioned data. If your data is less than a GB (and each file is under 50MB) you can dump it out to a GitHub repo and use that to track changes over time.
One example of that is my personal blog, here: https://github.com/simonw/simonwillisonblog-backup/tree/main...
That's using this tool: https://datasette.io/tools/sqlite-diffable
I imagine Datasette Cloud will end up with some sort of hybrid of those approaches.