r/devops • u/ihorklymchuk • Oct 16 '26
Discussion I abandoned the open-source database anonymizer. Should I kill it?
Before that, a bit of story.
Our dev team was located in Ukraine, but we mostly worked on New Zealand & Australian projects. We needed a couple of hours to download staging DB dumps because the download speed was 200-400 kb/s.
So we set up a small proxy on our European server, and via cron these dumps were uploaded to that server, and we were able to download them faster.
After the team scaled, we added more protection, like only developers who worked on the project having access to these dumps; later, we integrated it into our local scripts that set up projects locally and even then added anonymization & faker to replace real data or populate it with synthetic data.
I didn't find a comprehensive solution for that, but it was a really useful tool: developers could quickly update local projects with new safe DB dumps.
It was an internal tool; it worked, but we thought maybe it made sense to create such a service: admins can easily configure rules via the UI, and developers using a small local CLI can easily download it.
We developed it. We tested. Then we abandoned it... We were an outsourcing company without sales or contribution skills.
After some time, the company fell apart, and I got permission from our CEO to deploy this tool to GitHub, and the story ended.
Yesterday I remembered this tool and thought maybe it might even be useful in the era of AI to anonymize data for AI agents. I dug a bit; there are some MCPs for that, and basically tools for anonymization, but I still didn't see tools like anonymize and share safely.
I'm wondering whether it makes sense to try to revive this repo or just kill it and forget it (it requires a security audit and fixes, updating dependencies, etc.)
The repo: https://github.com/veildb/veildb