Live data from Hacker News

Show HN: We built an open-source LaunchDarkly alternative for B2Bs

enrolla.io

31–40 of 53 posts

Re: Show HN: We built an open-source LaunchDarkly alternative for B2Bs

#31

Congrats on launching! I really like the dashboard UI and the clean documentation. We are running an open source React-based framework called "refine" for building any kind of CRUD app like admin panels, dashboards, forms and internal tool etc. If you want to take a look, here is the repo: Repo: https://github.com/refinedev/refine

Cool spam but I don't think HN is the right place for non-constructive comments that seem to be written just in order for you link to your own products. We're supposed to ( https://news.ycombinator.com/newsguidelines.html ) have discussions about various things here, not just your own stuff :) https://news.ycombinator.com/threads?id=necatiozmen

The funniest bit here is that OP is already using Refine.

Re: Show HN: We built an open-source LaunchDarkly alternative for B2Bs

#32
post #31

Earlier quoted context omitted.

Cool spam but I don't think HN is the right place for non-constructive comments that seem to be written just in order for you link to your own products. We're supposed to ( https://news.ycombinator.com/newsguidelines.html ) have discussions about various things here, not just your own stuff :) https://news.ycombinator.com/threads?id=necatiozmen

The funniest bit here is that OP is already using Refine.

You're right! https://github.com/enrolla/enrolla/search?q=refine

That makes the spam hilarious and sad! Hilarious because they didn't notice but sad because they didn't even check. The spam could have been a happy "Wow, so cool you're using what we're building" but instead it turned into a generic "Hey please use this thing I made" message.

Re: Show HN: We built an open-source LaunchDarkly alternative for B2Bs

#33
post #23

I know this is a peak HN comment, but I really fail to see the appeal of using a third-party solution for something so basic. In my applications, feature flags are simply controlled via a "tags" field per user and per team. Additionally, each subscription plan has a "tags" field attached to it that is merged with the user and team tags. The logic of how the application behaves in each case is something you have to wr…

Most companies are not in the business of building UIs for rule engines, A/B-testing, user segmentation, etc. The value of giving non-engineers the power to roll out features without code changes is worth quite a lot. (Where I work we recently went from a home-rolled feature flag system similar to what you described to using LaunchDarkly)

Agreed, dynamically serving features based on a database flag is just one part. There's A/B analytics, rolling out to specific user segments, recognizing stale flags etc...

You could always build it all your self, but I guess you could build a lot of things your self...

Re: Show HN: We built an open-source LaunchDarkly alternative for B2Bs

#34
post #26
post #8

Earlier quoted context omitted.

Great points! I think the main differentiation for us is the connection to pricing and billing. Let’s say you have a feature like “how many seats (users) this customer has” it’s not enough to just be able to define it and fetch it where’ve you need it - which is basically what the tools you mentioned will give you. It depends on which pricing tier the customer’s in. Maybe they bought 5 seats but then 2 more as an add…

Do you expect Enrolla to cover the ground that Lago [0] covers, wrt metering and billing? Or would the golden path for a SaaS startup be to integrate both? For context: we're in the process of evaluating/integrating Lago after several years of writing custom billing logic while figuring out "pricing-market" fit. [0] http://getlago.com

Yes, we're actually working on supporting metering and billing these days. I think the golden path for a SaaS startup is to have as few products as possible.

Re: Show HN: We built an open-source LaunchDarkly alternative for B2Bs

#35
post #27
post #24

Earlier quoted context omitted.

Having had to implement custom billing logic and working in a startup that is still figuring out how to best price & bundle its product, I can see the value of this. I think this enables non-engineers to define pricing rules and the associated features. I wonder if this could integrate well with getlago.com (we're looking at integrating that after years which feel partially wasted on implementing custom billing logic…

We're currently working on metering and billing integration so I'm not sure if such integration makes sense.

Thank you for the reply. If anything, you can learn from the choices Lago made. It's not easy making a metering and billing system that works well enough for the majority of use-cases.

Re: Show HN: We built an open-source LaunchDarkly alternative for B2Bs

#36
post #23

I know this is a peak HN comment, but I really fail to see the appeal of using a third-party solution for something so basic. In my applications, feature flags are simply controlled via a "tags" field per user and per team. Additionally, each subscription plan has a "tags" field attached to it that is merged with the user and team tags. The logic of how the application behaves in each case is something you have to wr…

That works great for simple things. how do you tie a specific feature flag to a cross-engineering organization feature that's under rollout with input from multiple projects?

django-waffle is an example of your approach, and worked pretty well in a monolithic environment. But it also exposed multiple issues in coordination in a service oriented environment, which is one reason why O'Reilly went to LaunchDarkly around 2018.

Re: Show HN: We built an open-source LaunchDarkly alternative for B2Bs

#37

Seems that no-one mentioned my favorite feature flagging + A/B testing open source tool: https://www.growthbook.io/

I'll second GrowthBook. I was able to drop out of a LaunchDarkly subscription that was costing thousands of dollars per month and into a nice, cozy $29 Growthbook plan with zero loss in fidelity, while also increasing capabilities.

Growthbook has a Chrome dev plugin that allows you to simulate feature flags and value changes without having to modify the actual flags and watch the page update in response to the flag changes, which made it not only cheaper than LaunchDarkly, but markedly better to work with.

Re: Show HN: We built an open-source LaunchDarkly alternative for B2Bs

#38

Seems that no-one mentioned my favorite feature flagging + A/B testing open source tool: https://www.growthbook.io/

I love growthbook! We’re building a different kind of feature flag framework - one that is for b2b and connects to your billing and pricing systems (because which feature is enabled is connected to what the user paid for).

Re: Show HN: We built an open-source LaunchDarkly alternative for B2Bs

#39
post #22

Earlier quoted context omitted.

Thanks again; glad to shed some light :) I totally get you; we're struggling to find the correct wording. As an engineer, I also bump into the "gradual (temporal) rollout" as the first association of "Feature Flags". What wording would make sense to you now that you understand the vision?

For me, it's that you described it as a LaunchDarkly competitor, which is mainly that "rollout" use case. It makes me expect the features they have, like alerts that a flag is serving the "launched" variation to everyone, and can be ripped out, or code search to see if any references to a flag remain. I gather you're probably not doing that stuff? That said, I have LaunchDarkly for feature rollout, an ACL layer for c…

Yes that’s our long term goal. I don’t like having to adapt 4 different tools to do things which are quite similar.

Re: Show HN: We built an open-source LaunchDarkly alternative for B2Bs

#40
post #24
post #23

I know this is a peak HN comment, but I really fail to see the appeal of using a third-party solution for something so basic. In my applications, feature flags are simply controlled via a "tags" field per user and per team. Additionally, each subscription plan has a "tags" field attached to it that is merged with the user and team tags. The logic of how the application behaves in each case is something you have to wr…

Having had to implement custom billing logic and working in a startup that is still figuring out how to best price & bundle its product, I can see the value of this. I think this enables non-engineers to define pricing rules and the associated features. I wonder if this could integrate well with getlago.com (we're looking at integrating that after years which feel partially wasted on implementing custom billing logic…

I'd love your feedback on https://priceops.org

We recently open sourced Tier http://github.com/tierrun/tier which combines metering, entitlements, feature flags and a client side SDK to simplify things.

Post reply on HN