All in one Status Pages, Uptime Monitoring, and Incident Management. Communicate about incidents and server status. Save money and time during critical hours.
Anima - Vibe Coding for Product Teams — Build websites and apps with AI that understands design.
Build websites and apps with AI that understands design.
Promoted
Maker
📌
Heyyy everyone! 👋
We are very excited to do our first launch for Garmingo Status! 🚀
Garmingo Status allows you to easily monitor your websites, APIs and all other IT-systems in an easy & reliable way. It is designed for teams of all sizes… from small Startups all the way up to large Enterprises.
Quick list of the top Features:
🖥️ Monitor Types: HTTP(s), TCP, UDP, E-Mail Server, SSL Certificates and many more
✉️ Integrations: Mobile Notifications, SMS, E-Mail, Discord, Slack, Teams, …
🌎 Locations: Monitor from up to 8 different locations (more to come)
🚧 Maintenance: Communicate about planned downtimes (and of course don't get incident spammed) 😉
Yes, we followed the no config files principle from the beginning. Everything in the Web-UI is designed to be user-friendly and welcoming for non-tech people.
This means:
No config files - everything via easy to use, self explanatory UI elements
Every input field has an explanation
Everything is designed to be as simple as possible
Split large configurations in different logical sections
Separate more advanced, less common, settings from the basic settings
...
There is an extensive documentation that we are constantly updating to explain everything
We are currently also producing guide videos for everything
The Status Page Editor has a live visual preview and a simple drag and drop editor (screenshot here)
I hope that answers your question :)
~Alex
Report
Incident response can be chaotic and this tool looks like a vital tool to keep customers informed while teams focus on fixes.
I am really glad to hear that you like it. And yes, it is really good for both keeping customers informed and helping the team identify and fix the issue :)
~Alex
Report
I love the simplicity but how does your solution deal with false positives in monitoring?
Does it have built in intelligence to minimize unnecessary alerts and prevent alert fatigue?
Report
Maker
Hi @tabbunuru, We introduced a retry-system that performs multiple checks before marking a service as offline to prevent false positives. And if your service is very likely to produce false positives you can also customize the retry behavior (including the delay and number of retries) to deal with that - making false positives very unlikely.
That reduces unnecessary alerts and allows you to take each alert seriously. In addition to that you can configure multiple different alert/notification methods for different monitors, allowing you to have "dedicated channels" for high priority services.
I hope that answers your question:)
~Alex
Report
Absolutely love it! Used it from the beta on, and it’s just great 😊
The difference between Garmingo Status and Atlassian Statuspage is of course, that we have an all in one solution, for all 3: Monitoring, Incident Management and Status Pages. Also our Status Pages are highly customizable and have a modern appearance by default.
It can also definitely keep up with Better Uptime in terms of scalability and reliability. In addition to that there are of course also some differences...
In many areas Better Uptime focuses on simplicity and is missing out some more complex customization options/subfeatures. Our goal was to find a good way in between. Making it simple enough for everyone to understand, but also offering all the features we think you could need. So that both the "average user" and the "power/advanced user" can get everything they want. Also our monitors can work through proxies to allow monitoring of services that run in internal networks.
For example the Better Uptime Maintenance functionality is afaik limited to onerecurring maintenance for each monitor individually or globally. On the other hand we allow you to create multiple maintenances for one/all/specific monitor(s) that can be either recurring or one-time only.
Also we have a totally different approach on reporting. In my personal opinion the Better Uptime Reporting feature seems to be focused on providing an analytical dashboard. On the other hand our reporting feature is focused on compliance. You don't have to manually put all the elements from the analytics together, instead you get a handy PDF file you can work with. Especially non-technical teams probably prefer that way. And the automatically generated monthly reports also come in handy.
Our Status Pages are also way more customizable to allow our customers to match their own brand style in a simpler way. Not only custom-css but also many simple options to customize the appearance without coding.
We also found that the Better Uptime Dashboard becomes increasingly hard to navigate when there are many monitors. Some of our customers needed multiple thousand monitored services and scrolling through a list or using just a search bar was not enough. That is we introduced a filter card that allows to narrow down the displayed monitors very easily. And we also added a keywords functionality to the monitor settings, so that you can add additional search keywords without renaming the monitor.
Pricing wise we found that many solutions on the market are definitely overpriced and not really affordable for small startups, which we also wanted to change. We also knew that pay-as-you-go is scary for beginner startups, so we decided to go with a tiered plan approach instead - that offers fair pricing while still allowing enterprise customers to pay for exactly what they need.
Of course there are many more differences, but it would take a while to go trough all of them as well. I hope I could give you a first insight into how we stack up.
Heyyy everyone! 👋
We are very excited to do our first launch for Garmingo Status! 🚀
Garmingo Status allows you to easily monitor your websites, APIs and all other IT-systems in an easy & reliable way.
It is designed for teams of all sizes… from small Startups all the way up to large Enterprises.
Quick list of the top Features:
🖥️ Monitor Types: HTTP(s), TCP, UDP, E-Mail Server, SSL Certificates and many more
✉️ Integrations: Mobile Notifications, SMS, E-Mail, Discord, Slack, Teams, …
🌎 Locations: Monitor from up to 8 different locations (more to come)
🚧 Maintenance: Communicate about planned downtimes (and of course don't get incident spammed) 😉
📈 Status Pages: Create private/public Status Pages just like these two: https://status.garmingo.com, https://status.gommehd.net
👫 Collaboration: Work with Teams of all sizes & assign Roles
📊 Reports/Compliance: See how well your infrastructure did & check Compliance Targets
THANK YOU to all of you who have followed our journey so far and helped us shape Garmingo Status and its future 🙏
Product Hunt Coupon 💸
To thank you for this opportunity, we created the code PH30 for 30% off all plans. (Just enter it at the checkout)
Let us know if you have any questions or feedback :)
This is like a fantastic all in one solution but can a non technical team configure status pages and monitoring without developer assistance?
Hi @contact_umair ,
Yes, we followed the no config files principle from the beginning.
Everything in the Web-UI is designed to be user-friendly and welcoming for non-tech people.
This means:
No config files - everything via easy to use, self explanatory UI elements
Every input field has an explanation
Everything is designed to be as simple as possible
Split large configurations in different logical sections
Separate more advanced, less common, settings from the basic settings
...
There is an extensive documentation that we are constantly updating to explain everything
We are currently also producing guide videos for everything
The Status Page Editor has a live visual preview and a simple drag and drop editor (screenshot here)
I hope that answers your question :)
~Alex
Incident response can be chaotic and this tool looks like a vital tool to keep customers informed while teams focus on fixes.
Hi @faith_foster ,
Thank you!
I am really glad to hear that you like it.
And yes, it is really good for both keeping customers informed and helping the team identify and fix the issue :)
~Alex
I love the simplicity but how does your solution deal with false positives in monitoring?
Does it have built in intelligence to minimize unnecessary alerts and prevent alert fatigue?
Hi @tabbunuru,
We introduced a retry-system that performs multiple checks before marking a service as offline to prevent false positives.
And if your service is very likely to produce false positives you can also customize the retry behavior (including the delay and number of retries) to deal with that - making false positives very unlikely.
That reduces unnecessary alerts and allows you to take each alert seriously.
In addition to that you can configure multiple different alert/notification methods for different monitors, allowing you to have "dedicated channels" for high priority services.
I hope that answers your question:)
~Alex
Absolutely love it! Used it from the beta on, and it’s just great 😊
Hi @kuuzoo ,
I am really glad that you like it. Thanks a lot :)
May I ask what you like the most?
~Alex
Im very satisfied so far and havent had any problems
Hi @niko_biberhofer ,
I am very glad to hear that you like Garmingo Status and have not had any issues.
May I ask what you like the most?
~ Alex
I love the concept. @alexanderneitzel How does your solution stack up against established platforms like Statuspage or Better Uptime?
Hi @emily_hernandez3,
The difference between Garmingo Status and Atlassian Statuspage is of course, that we have an all in one solution, for all 3: Monitoring, Incident Management and Status Pages.
Also our Status Pages are highly customizable and have a modern appearance by default.
It can also definitely keep up with Better Uptime in terms of scalability and reliability.
In addition to that there are of course also some differences...
In many areas Better Uptime focuses on simplicity and is missing out some more complex customization options/subfeatures. Our goal was to find a good way in between. Making it simple enough for everyone to understand, but also offering all the features we think you could need.
So that both the "average user" and the "power/advanced user" can get everything they want.
Also our monitors can work through proxies to allow monitoring of services that run in internal networks.
For example the Better Uptime Maintenance functionality is afaik limited to one recurring maintenance for each monitor individually or globally.
On the other hand we allow you to create multiple maintenances for one/all/specific monitor(s) that can be either recurring or one-time only.
Also we have a totally different approach on reporting. In my personal opinion the Better Uptime Reporting feature seems to be focused on providing an analytical dashboard. On the other hand our reporting feature is focused on compliance. You don't have to manually put all the elements from the analytics together, instead you get a handy PDF file you can work with.
Especially non-technical teams probably prefer that way. And the automatically generated monthly reports also come in handy.
Our Status Pages are also way more customizable to allow our customers to match their own brand style in a simpler way. Not only custom-css but also many simple options to customize the appearance without coding.
We also found that the Better Uptime Dashboard becomes increasingly hard to navigate when there are many monitors. Some of our customers needed multiple thousand monitored services and scrolling through a list or using just a search bar was not enough.
That is we introduced a filter card that allows to narrow down the displayed monitors very easily.
And we also added a keywords functionality to the monitor settings, so that you can add additional search keywords without renaming the monitor.
Pricing wise we found that many solutions on the market are definitely overpriced and not really affordable for small startups, which we also wanted to change.
We also knew that pay-as-you-go is scary for beginner startups, so we decided to go with a tiered plan approach instead - that offers fair pricing while still allowing enterprise customers to pay for exactly what they need.
Of course there are many more differences, but it would take a while to go trough all of them as well.
I hope I could give you a first insight into how we stack up.
~Alex