This is cool – as an open source founder, I've wondered about how to keep things transparent while protecting people's privacy. What’s your general approach to public databases, and when does it make sense to make them public?
Thanks! Yeah we generally recommend not making your databases public and instead connecting to them using a bastion host. We support this at Neosync. Also, ideally, not connecting to a live DB and instead a snapshot or back up. A read replica could work as well but a snapshot is better.
Big fan of what Evis and team are building. We work with lots of orgs in regulated industries at Autoblocks and Neosync's anonymization is a fan favorite for AI teams at these orgs.
Thanks for the question! Faker is useful but doesn't have a lot of features. For example, referential integrity, data orchestration or the ability to read/write to a db. So faker can work for simple API schemas but if you need something more robust for an entire database, then that's where we can help.
This is cool – as an open source founder, I've wondered about how to keep things transparent while protecting people's privacy. What’s your general approach to public databases, and when does it make sense to make them public?
Thanks! Yeah we generally recommend not making your databases public and instead connecting to them using a bastion host. We support this at Neosync. Also, ideally, not connecting to a live DB and instead a snapshot or back up. A read replica could work as well but a snapshot is better.
Big fan of what Evis and team are building. We work with lots of orgs in regulated industries at Autoblocks and Neosync's anonymization is a fan favorite for AI teams at these orgs.
Why this over something like Faker?
Thanks for the question! Faker is useful but doesn't have a lot of features. For example, referential integrity, data orchestration or the ability to read/write to a db. So faker can work for simple API schemas but if you need something more robust for an entire database, then that's where we can help.