I’m exploring an idea and would love honest feedback from folks who’ve dealt with config management at scale.

Idea:
An open-source, self-hosted configuration control plane that works in both backend and frontend.

Key principles:

• No SaaS (you host it)

• We never store your config data

• Bring your own storage (DB / Firebase / S3 / etc.)

• SDK-first (Node / Java / frontend)

• Supports overrides org → projects → apps → tenants → environments or org → projects → apps → environments

• Can run embedded or expose an API (Spring Cloud Config–like, but lighter & polyglot)

Why:

• Many teams don’t want config / flags stored in third-party SaaS

• Vendor lock-in + compliance concerns

• Existing tools feel heavy or backend-only

Not trying to replace LaunchDarkly fully — more like:

“infra-owned config runtime + control plane”

Questions:

1. Is this a real pain point or already solved well?

2. Would you use something like this over SaaS?

3. What would be a must-have for v1?

4. Any strong reasons not to build this?

Happy to hear brutal takes.