A few months ago, I was working on a side project that should have been fun… but I kept getting tripped up by config management. Every small change meant digging through bloated files, double-checking docs, and hoping I didn’t break something critical.
I realized I was spending more time wrestling with configs than actually building features. That frustration stuck with me so I decided to do something about it.
That’s how togglit.dev was born. I wanted a lean, focused config-as-a-service no bloat, no endless YAML, just a simple way to manage configs and get on with building.
I’m sharing this because I know I’m not the only one who’s been burned by config chaos. If you’ve got a config horror story, or if you’ve ever wished config was just… easier, I’d love to hear from you.
What’s the worst config mess you’ve had to clean up? And what would your dream config tool look like?
Here’s what I’ve built so far: https://togglit.dev
Thanks for reading I’m all ears for feedback, stories, or feature ideas!
Top comments (0)