Joel Weirauch


Tea, Tech, Cycling and general outdoor enthusiast living in a converted cargo van and traveling the USA while Building @TinySurveysIO and some other things.

@marckohlbrugge There are a few differences. You are able to maintain switches for any language/platform from one central location without doing any extra coding. So, for example, your UI team using any JavaScript frontend framework can use a the FeatureSwitches JavaScript library while your backend Ruby/Python/etc can use its own library.

Also, while some of the open source libraries have a UI component it's not nearly as user friendly or full featured. We aim to allow not only developers but also product, marketing and QA to be able to create and manage switches. This is especially helpful with the ability to enable features for certain users/groups, so a product team member could enable a feature for themselves without needing to pester a dev.

And finally, we have, or are working on, more advanced features like A/B testing and gradual rollout instead of simply turning a feature on or off.
@JoelWeirauch Ah yes, that makes a lot of sense. I can see how having to deal with features that span across multiple parts of the application (Javascript, Ruby, etc) would be difficult to manage using a Ruby-only solution. Having a universal way to deal with it, would be quite handy indeed.
Hi Everyone, I'm Joel the founder of Unstacks. I created Unstacks to solve a problem that I have encountered at a number of places I've done work for. Most places waste a ton of time and money managing dedicated testing environments. This usually slows down developers and QA / Product Management and it takes a lot of extra effort to keep straight what branch is where and at what state it is.

I built out bespoke solutions for a few clients and realized that turning them into a SaaS would be a better use of my time. I'm looking for people to help shape the features and functionality so that we can make Unstacks the best it can be.