The cool thing is that I don't intend to take it down now that I built a SaaS around it. I'll keep both open source and SaaS versions of it live, and try to upsell the service to those who don't feel like self-hosting it. Plus, the SaaS version comes with features not available in the open source version (such as support to Android) :)
That's great! We may actually use your hosted service since we haven't had the resources available to setup the self hosted version.
Edit: Some quick feedback. Your pricing uses the word "workflow" but what that means isn't described anywhere on the site or FAQ. I assume it's used once you create an account but it's not clear what it means before signup.
Ooh, that's super valuable feedback, thank you so much!
I'll fix that right away.
PS: Lemme know if you need any guidance setting things up or have any further questions! There's the official support email but also white-glove treatment at t.me/rogerluan ;)
You'll notice that the subscription is based on workflows. A workflow is a connection between a source (e.g., your iOS app) and a destination (e.g., a Slack channel). You can set up as many workflows as you'd like, which is a great way to separate different types of notifications. For instance, #ios-deploys-prod receives updates about your production app, #ios-deploys-staging receives updates about your staging builds, and #android-deploys-beta receives updates about the Beta track of your Android builds. Each of these is a separate workflow.
The cool thing is that I don't intend to take it down now that I built a SaaS around it. I'll keep both open source and SaaS versions of it live, and try to upsell the service to those who don't feel like self-hosting it. Plus, the SaaS version comes with features not available in the open source version (such as support to Android) :)
Thanks for spotting and sharing this!