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

Launch HN: GrowthBook (YC W22) – Open-source feature flagging and A/B testing

growthbook.io

Post reply on HN
Print view View original

11–20 of 47 posts

Re: Launch HN: GrowthBook (YC W22) – Open-source feature flagging and A/B testing

#11

Post by dasternberg »

barrrrald wrote: post #8

How is this different than Eppo [1] or Optimizely? [1] https://www.geteppo.com

Re: Eppo - they're similar in setup but Growthbook is open source with an optional cloud SaaS offering. Eppo is currently cloud SaaS only AFAIK.

Re: Optimizely - Optimizely is a walled garden, you need to push all of your metrics as events to Optimizely from your apps for any experiment analyses. Eppo and GrowthBook both connect to your data warehouse and support any metrics you can design in query form using your existing warehouse.

Re: Launch HN: GrowthBook (YC W22) – Open-source feature flagging and A/B testing

#16

Post by joecot »

This looks great, but if I can make a suggestion, a guide in your docs on how to use this with Matomo[1] would go far. Growthbook provides Feature Flag and A/B Testing, but you have to bring your own analytics. Matomo provides those analytics and is also open source and self hosted, and would be an excellent match. There's been an issue in about integrating since September[2], and having a guide with SQL examples for using this with Matomo would take it to the next level.

1. https://matomo.org/ 2. https://github.com/growthbook/growthbook/issues/86

Re: Launch HN: GrowthBook (YC W22) – Open-source feature flagging and A/B testing

#18

Post by jrdorn »

Plasmoid wrote: post #14

How do you differentiate yourself from tools like Flagr? [ https://github.com/checkr/flagr ]

Tools like Flagr typically function as a microservice that handles all of the feature evaluation. That means you need a network request every time you want to get a feature's value. With GrowthBook, there's a single cacheable JSON definition of all of the features and then evaluation happens locally within the SDKs. We found this approach to be much better for performance and scalability.

The other missing part in most feature flagging tools is the analysis side. Most tools let you run an A/B test, but it's up to you to track the data, process it, and run it through a stats engine. We built that part directly into GrowthBook.

Re: Launch HN: GrowthBook (YC W22) – Open-source feature flagging and A/B testing

#19

Post by chambers »

Nice launch. Will Growthbook one day support "Feature Rollouts" like statsig? https://www.youtube.com/watch?v=aFmSVP5Jxmc

A lot of big companies need to gradually introduce a new feature to an audience while also seeing how that feature impacts their metrics. If they go with just feature flagging, they have to build their own logging and analysis. But if they go with experiments, then they're overly constrained by that analysis since experiments are meant to be statistically rigorous.

It's a tricky problem which I think statsig solved with "pulse metrics" and "feature gates".

Post reply on HN