Just kicked off a project to explore open-sourcing what we've built (VC funded). I'm considering a different tack which I think may be interesting. We have a l

Just kicked off a project to explore open-sourcing what we've built (VC funded). I'm considering a different tack which I think may be interesting. We have a lot of client libraries, already open sourced. Then we have the hosted APIs and DB which are not open. Making all the close-source stuff open, feels like a big effort, with an unclear reward and more likely that we just end up with a hard to install OS project, since it feels like the hosting expertise _is_ part of the core value prop. What I'm excited about though is whether we could take the hosted piece out of the equation and find something that is pretty different, but has its own niche. For us this would be replacing the web UI and DB hosting of the paid product, with a CLI and simpler git based hosting for an open source version. ie If you want hosted feature flags, we think you should use the hosted thing, but if you want gitops style feature flags (100% reliable), then use the OS version. I like the idea that we could really focus on making the open version great in its niche, but have a super clear line about what is paid / hosted, to help us avoid the complexity of always needing to decide how to nerf the OS version.