I built Upty after getting frustrated with expensive status page tools like Statuspage.io. I needed something simpler and cheaper for my side projects, so I spent the last few weeks building this. I needed something simpler and cheaper for my side projects, so I spent the last few weeks building this.
What it does: Upty is a status page tool with automated health check monitoring. You add your services as components, configure HTTP health checks with customizable intervals and thresholds, and it automatically updates your public status page when things go down. It also handles manual incident management, webhooks, and has a REST API.
It's built with Go + MySQL and runs fast. Currently free to use while in beta.
It's in early beta and likely has bugs, but the core features work. I'd love feedback on what's missing or what doesn't make sense. No signup required to view the demo at status.upty.dev
Technical details: Multi-tenant with subdomain isolation, configurable downtime thresholds, 30-day uptime visualization, RSS feeds, incoming webhooks, HTTP health checks, and API access. Built by someone who's been paged at 3am too many times
talonx•3h ago
I understand this is an initial launch, so not trying to nitpick, but these are what felt like would add immediate value:
- Adding a social login like Google would allow faster signups.
- Maybe I missed it - but I could not find any options for automatic monitoring which would update the status page. There are manual options for adding an incident.
- Post-signup, it takes me to a login page. Why ask to enter the company name instead of user/pass directly?
- If I could click on "Components" on my dashboard (/admin) and go directly to the Components page, that would be nice.
I like it that you took the time to write a privacy policy that is both readable and precise, especially as to the list of third-party services.
artemlive•3h ago
1. Social login is almost done - decided to ship without it to get feedback faster, but it'll be added soon.
2. Yes! Automated health checks are there - check out step 4 on the tour page (https://upty.dev/tour). They automatically update component status when thresholds are crossed. Auto-creating incidents from health checks isn't ready yet, but you can use the API to create incidents programmatically in the meantime.
3. Good catch on the post-signup flow - I'll fix that.
4. Noted on the dashboard navigation, makes sense.
Thanks for the kind words about the privacy policy! Let me know if you hit any other issues.
talonx•2h ago
Thanks for explaining #2 - but the text "Auto" might be a bit non-intuitive for a user.
artemlive•2h ago
talonx•1h ago