4 ms·
It's a one-time 4.99 fee (covers a year of monitoring or 50 downtime events).
by SantiagoVargas 1y ago
It's a one-time 4.99 fee (covers a year of monitoring or 50 downtime events).
- Zanfa 1y agoThat’s an annual subscription.
- SantiagoVargas 1y agoI suppose you're right, unless your server goes down more than 50 times. I saw it as credits that expire in a year, would be a bit scary to offer monitoring in perpetuity for $5 if they didn't expire.
- lurk2 1y agoConsider changing your landing page to reflect the price (“Only $5 Annually!”). The reason I asked was because the way it is now makes it look like the service is being offered for free, which made me think it was a phishing scheme.
- SantiagoVargas 1y agoI appreciate the feedback! Just implemented this, hadn't thought of that. Cheers.
- thinkingemote 1y agointeresting, how did you come up with the pricing? Similar other services?
- SantiagoVargas 1y agoNot quite - just thought of what I would actually pay for it. Looked at others and saw most done for you solutions were monthly subscriptions ~$9. Couldn't see myself being excited by that pricing model + another dashboard to manage, so I made it $5 for the year and built the most simple solution that's easy to set up and reliable (while not losing money). Almost all monitoring services I found target enterprise, and the ones that don't are self-hosted. This solution is for the small teams/indie devs that just need to know when their servers down. Might raise the price though, thinking the low price might work against me for quality perception. What do you think?
- thinkingemote 1y agoI used a hobby tier service which would send free emails but you would buy credits for SMS. Now I do it myself with simple Cron script One thing with the events model is that for some webhosts which do maintenance or small periods of downtime often a user might see many through the year. Or in other words the hobby dev might see them but I imagine a production level small team shouldn't be using those servers anyway