Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

enrolla.io

Post reply on HN
Print view View original

11–20 of 53 posts

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

#11

Post by capableweb »

nirga wrote: post #9
FailMore wrote: post #7

Looks good. My friend launched Flagsmith a few years back too - https://github.com/Flagsmith/flagsmith . I have used it on a few of my own projects and it’s been great/easy to integrate

I love flagsmith! I just commented below that I think what makes what we’re doing different is the focus on SaaS and costumer features - so which features are enabled for whom based on the pricing tier they’re at.

Hmm, Flagsmith is also for SaaS and can do different feature flags for different users, so doesn't sound like it's that different.

Is there any unique features Enrolla has that none of the competitors don't? If there isn't, you might want to come up with some, otherwise it'll be a hard sell to sell something newer, less polished and with no unique selling points.

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

#12

Post by capableweb »

necatiozmen wrote: post #10

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

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

#15

Post by nirga »

capableweb wrote: post #11
nirga wrote: post #9

Earlier quoted context omitted.

I love flagsmith! I just commented below that I think what makes what we’re doing different is the focus on SaaS and costumer features - so which features are enabled for whom based on the pricing tier they’re at.

Hmm, Flagsmith is also for SaaS and can do different feature flags for different users, so doesn't sound like it's that different. Is there any unique features Enrolla has that none of the competitors don't? If there isn't, you might want to come up with some, otherwise it'll be a hard sell to sell something newer, less polished and with no unique selling points.

Yeah I know :) I meant that there are some things specific to SaaS that we're trying to solve - like connecting it to pricing and package tiers. So if we have a feature flag called "SAML enabled" its value is based on what pricing tier that specific customer uses.

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

#18

Post by capableweb »

nirga wrote: post #15
capableweb wrote: post #11

Earlier quoted context omitted.

Hmm, Flagsmith is also for SaaS and can do different feature flags for different users, so doesn't sound like it's that different. Is there any unique features Enrolla has that none of the competitors don't? If there isn't, you might want to come up with some, otherwise it'll be a hard sell to sell something newer, less polished and with no unique selling points.

Yeah I know :) I meant that there are some things specific to SaaS that we're trying to solve - like connecting it to pricing and package tiers. So if we have a feature flag called "SAML enabled" its value is based on what pricing tier that specific customer uses.

> like connecting it to pricing and package tiers. So if we have a feature flag called "SAML enabled" its value is based on what pricing tier that specific customer uses.

But that's not a unique feature, it's a fairly basic feature for a "Feature toggle" service to have, you'd be looking for a while if you're trying to find one that doesn't have that.

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

#19

Post by [deleted] »

capableweb wrote: post #18
nirga wrote: post #15

Earlier quoted context omitted.

Yeah I know :) I meant that there are some things specific to SaaS that we're trying to solve - like connecting it to pricing and package tiers. So if we have a feature flag called "SAML enabled" its value is based on what pricing tier that specific customer uses.

> like connecting it to pricing and package tiers. So if we have a feature flag called "SAML enabled" its value is based on what pricing tier that specific customer uses. But that's not a unique feature, it's a fairly basic feature for a "Feature toggle" service to have, you'd be looking for a while if you're trying to find one that doesn't have that.

[deleted]

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

#20

Post by GalKlm »

capableweb wrote: post #18
nirga wrote: post #15

Earlier quoted context omitted.

Yeah I know :) I meant that there are some things specific to SaaS that we're trying to solve - like connecting it to pricing and package tiers. So if we have a feature flag called "SAML enabled" its value is based on what pricing tier that specific customer uses.

> like connecting it to pricing and package tiers. So if we have a feature flag called "SAML enabled" its value is based on what pricing tier that specific customer uses. But that's not a unique feature, it's a fairly basic feature for a "Feature toggle" service to have, you'd be looking for a while if you're trying to find one that doesn't have that.

It goes beyond a feature toggle. Pricing Tiers/Packages tend to consist of more "sophisticated" pricing mechanisms, usually split into Licensed Features (simple toggles like SAML enabled and limits like Seat Count) and Metered Features (either quotes/limits or pay as you go). We're currently working on the metering functionality together with billing systems integration. That's the difference, IMO, from the common Feature Flags solution.

Thanks for the comments; they are much appreciated and help us shape our messaging and understand what's not going through.

Post reply on HN