This is Bemi's blog and their solution seems quite good for the larger scaled problems. I'm rather experienced on Rails+PaperTrail and believe it to be a great

This is Bemi's blog and their solution seems quite good for the larger scaled problems. I'm rather experienced on Rails+PaperTrail and believe it to be a great solution for startups. If you're looking at this for consideration, a few things I recommend: - Critical models should get their own PaperTrail table. - Install `--with-changes` always! The extra data is worth it. Direct DB changes, changes via `.update_columns` will all skip PaperTrail (Actually this is where Bemi could be helpful due to WAL based). - PaperTrail is not true Disaster recovery, I argue Bemi isn't either nor are read-replicas. You want an off-site dump to be that.