I built Cassie.fm (https://cassie.fm) website and API monitoring service.
Why?
I run a tiny software shop, and bulk of our work consists of integrating our products (field service management app) on top of various ERPs (local and ancient for the most part). These ERPs often have APIs tacked on as a afterthought. These go down very often . If the API we integrate with goes down, it looks bad for us since our product does not work, so in order to drive accountability and transparency I hacked together an API monitoring solution. I wanted something that:
- Scales as we add more monitors: Pay only for what you use. No subscriptions. (We're actually paying for our own credits, its a bit weird with accounting but it forced me to do a proper Stripe integration)
- Real-time alerts, sms, email and webhooks, so that we can keep everyone in the loop including our user facing apps.
- Simple, transparent pricing, maybe we decide to invest more heavily in marketing this to our existing clients, and most pricing these days is garbage
What’s Next?
I'm building this to solve a specific business problem for my shop. I like to be driven by actual users, so as adoption grows so will the feature set. Some things I'm considering are
analytics, and customisable alerts, response structure checks and schema validation.
Get Started
Register - https://cassie.fm/account/register. You get free 1600 daily credits, no strings attached. Accounts that have no monitors are automatically purged after 30 days, and I promise I won't send you any emails unless you send some first :).
Hi HN,
I built Cassie.fm (https://cassie.fm) website and API monitoring service.
Why?
I run a tiny software shop, and bulk of our work consists of integrating our products (field service management app) on top of various ERPs (local and ancient for the most part). These ERPs often have APIs tacked on as a afterthought. These go down very often . If the API we integrate with goes down, it looks bad for us since our product does not work, so in order to drive accountability and transparency I hacked together an API monitoring solution. I wanted something that:
- Scales as we add more monitors: Pay only for what you use. No subscriptions. (We're actually paying for our own credits, its a bit weird with accounting but it forced me to do a proper Stripe integration)
- Real-time alerts, sms, email and webhooks, so that we can keep everyone in the loop including our user facing apps.
- Simple, transparent pricing, maybe we decide to invest more heavily in marketing this to our existing clients, and most pricing these days is garbage
What’s Next?
I'm building this to solve a specific business problem for my shop. I like to be driven by actual users, so as adoption grows so will the feature set. Some things I'm considering are analytics, and customisable alerts, response structure checks and schema validation.
Get Started
Register - https://cassie.fm/account/register. You get free 1600 daily credits, no strings attached. Accounts that have no monitors are automatically purged after 30 days, and I promise I won't send you any emails unless you send some first :).