UptimeSam: uptime monitoring with alerts and a public status page
Watch your websites, APIs, databases, certificates and background jobs, hear about it the moment one of them goes down or slows down, and tell your users what is happening on a status page that updates itself.
- Eleven check types, from HTTP and cron jobs to Postgres and ping
- Alerts by email, Slack, Discord, Teams and more, routed per monitor
- A status page with email subscribers, a widget and badges
More on uptimesam.com:Feature tourREST APIMCP server
Most outages at a small software business are found by a customer. The site has been returning errors for forty minutes, the certificate expired overnight, or the nightly billing job quietly stopped running last Tuesday. Nothing was watching, so the first alert is a support email, and by then the damage is done.
UptimeSam is the thing that watches. You create a board, add monitors for the sites, endpoints, certificates and jobs you care about, and UptimeSam checks them around the clock. When one fails, the board's team hears about it on the channels they already use, and the board's public status page shows it to everyone else.
It is the monitoring piece of the Releasy Suite: UptimeSam watches whether your product is up, Hookfire tells you what it just did, Upvoted collects what users ask for and Indie Polls answers the questions in between.
How UptimeSam works
Everything hangs off a board. A board holds a set of monitors and the team that looks after them, and it publishes its own public status page.
1. Create a board
A board is one product, one client or one environment, with the people responsible for it. Its status page goes live at its own address, like acme.uptimesam.com.
2. Add monitors
Pick a type and point it at a URL, a host or a record. Pro checks every minute and Max every 30 seconds. Each monitor shows up on the board and, in the group you put it in, on the status page.
3. Hear about it when something breaks
A monitor is declared down only after its retries fail, so one slow answer wakes nobody. When it really is down, the alert goes out on the channels the board is connected to.
What UptimeSam can check
Eleven kinds of monitor, all of them on every plan, because an outage does not care which plan you are on.
HTTP(S)
Request a page or an endpoint and check the answer: the status code, the headers, the method, how redirects are followed, and how long the response took.
HTTP keyword
A page can return 200 and still be broken. A keyword monitor checks that the page contains a word it must have, or does not contain one it must never show, such as an error message.
SSL certificate expiry
UptimeSam reads the certificate and warns you 14, 7 and 1 days before it expires, so a renewal that failed silently is found while there is still time to fix it.
Heartbeat for cron jobs and workers
Some failures never answer a request. Your cron job or background worker pings a unique URL each time it runs, and when the pings stop arriving within the interval plus a grace period, the monitor goes down.
JSON fields
An API can answer 200 with an error inside. A JSON check reads a field of the answer, such as data.status, and checks it has the value it should.
PostgreSQL, MySQL, Redis and SMTP
Databases, caches and mail servers are checked in their own protocol, not just with an open port, so a server that accepts connections but cannot serve them is caught. No passwords are needed.
TCP port and ping
Check that any other service accepts connections on its port, or that a server, router or gateway answers a ping.
DNS record
Check that a record resolves and keeps resolving, so a change at the registrar or the DNS host does not take the site down without anyone noticing. UptimeSam also warns 30, 7 and 1 days before the domain itself expires.
Alerts that reach the right people
An alert is only useful if it lands where someone will see it, and only bearable if it is right. UptimeSam is built around both.
Wherever your team already looks
Email to the board's members, Slack, Discord, Microsoft Teams, Telegram and signed webhooks, on every plan, so the outage lands in the place your team reads first.
On your phone, through Hookfire
Hookfire is a built-in alert channel, so a monitor going down arrives as a push notification on your phone, alongside the payments and deploys Hookfire already tells you about.
Each monitor picks its channels
Send the database alerts to the backend channel and the website ones to everyone. A monitor uses every channel of the board, or only the ones you choose.
Slow is an alert too
Set a response time per monitor and hear about it after three slow checks in a row. An outage that drags on alerts again at the interval you choose, so it never gets buried.
No false alarms from a single blip
Every failed check is retried before the monitor is declared down. A slow response or a dropped packet stays a line in the history instead of a message at three in the morning.
Quiet during planned work
Schedule a maintenance window and alerts for it are silenced, while the status page tells visitors the work is planned.
A status page your users can check
Every board publishes a public status page at its own address, like acme.uptimesam.com. It answers the question “is it down or is it me” before it becomes a support ticket.
Current status at a glance
A banner at the top says whether everything is working, followed by your monitors in the groups you chose, each with 90 days of uptime bars and its response times.
Incidents, open and past
Post an incident when something goes wrong, so visitors read it on the page instead of asking you. Past incidents stay on the page, which is the record of how you handled them.
Email updates for your users
Visitors subscribe from the status page and confirm by email. They hear about each incident and update, and leave with one click.
On your own site and in your README
One line of script puts a badge or a status card on your site, and uptime badges go in a README or your docs.
Scheduled maintenance
Announce planned work in advance so visitors know about it before it starts. The same window keeps your own alerts quiet while it runs.
Your brand on it, and your audience, on Max
Add your own logo, favicon and theme, write custom CSS, and remove the UptimeSam branding. Keep the page to your signed-in team, or put it behind a password for customers and partners.
Automate it
Monitors should come and go with your services, and an assistant should be able to tell you what is down without you opening a dashboard.
A REST API
Create, change, pause and delete monitors and post incidents from deploy scripts, CI or infrastructure tools, with keys scoped to one board.
Let an assistant watch with you
UptimeSam ships an MCP server on Max, so an AI assistant such as Claude, ChatGPT or Cursor can tell you what is down and why, add and pause monitors, and post incidents on your status page, as you.
Pro and Max
Both plans have every monitor type and every alert channel. Max is for more monitors, faster checks, more history and a bigger team.
Pro
One board with two seats and 25 monitors checked every minute. A status page with incidents and maintenance, 7 days of check history and a year of uptime history.
Max
Unlimited boards and seats with roles, and 100 monitors checked every 30 seconds. 30 days of check history, private and password-protected status pages, status page branding with custom CSS, the MCP server for AI assistants, and priority support.
Who UptimeSam is for
- SaaS products
- Watch the app, the API and the certificate, and keep customers informed on a status page instead of in a pile of support tickets.
- Background jobs
- A heartbeat monitor on the nightly import or the billing run tells you the day it stops, not the day a customer notices.
- Agencies and freelancers
- One board per client on Max, each with its own monitors, team and status page.
- Solo founders
- Someone has to be watching while you sleep. UptimeSam watches, and retries before it wakes you.
UptimeSam comes with three more tools
is one subscription covering all four apps, on one login and one bill. Buy it inside any of them and the other three unlock on the same account.
Alerts from your whole stack
50+ services including Stripe, GitHub, Sentry and Shopify, turned into a phone notification the second they fire.
About Hookfire
Feature voting from your users
A public board where users post ideas and vote, so you build what people actually want, not the loudest email.
About Upvoted
Answers, embedded anywhere
Lightning-fast surveys you drop in with one snippet. Nine kinds of question, live results, real answers.
About Indie PollsUptimeSam FAQ
What is UptimeSam?
UptimeSam is an uptime monitoring service with alerts and public status pages. It checks your websites, APIs, SSL certificates, domains, cron jobs, databases, mail servers, TCP ports, DNS records and servers by ping, alerts your team when one goes down or slows down, and publishes the status on a public page for each board.
What kinds of monitor are there?
Eleven: HTTP(S), which checks status codes, headers, methods, redirects, response times and, optionally, a field of a JSON answer; HTTP keyword, which checks that a page does or does not contain a word; SSL certificate expiry, with warnings at 14, 7 and 1 days; heartbeat, for cron jobs and background workers that ping a unique URL; TCP port; DNS record; ping; and PostgreSQL, MySQL, Redis and SMTP, each checked in its own protocol. Every type is on both plans.
How do I monitor a cron job?
Create a heartbeat monitor and UptimeSam gives you a unique URL. Have the job request that URL each time it runs. If the pings stop arriving within the interval you set plus a grace period, the monitor goes down and the alerts go out.
Will one slow response wake me up?
No. A monitor is declared down only after its retries fail, so a single slow answer or dropped connection is recorded and nothing more. Maintenance windows also silence alerts during planned work.
Where can alerts go?
Email to the board's members, Slack, Discord, Microsoft Teams, Telegram, signed webhooks, and Hookfire, which turns an alert into a push notification on your phone. Every channel is included on both plans.
What is on the public status page?
A banner with the current status, your monitors in groups with 90-day uptime bars and response times, open and past incidents, and scheduled maintenance. Each board has its own page at its own address, like acme.uptimesam.com, and on Max you can add your logo, favicon, theme and custom CSS and remove the UptimeSam branding.
Can visitors subscribe to the status page?
Yes, on both plans. Visitors enter their email on the status page and confirm it, then get an email for each incident and update you post, with a one-click unsubscribe. You see the subscribers, and can turn subscriptions off, in the status page settings.
Is there an API, and can an AI assistant use UptimeSam?
Yes. A REST API on both plans manages monitors and incidents and reads the status, with keys scoped to one board. On Max, an MCP server lets an AI assistant such as Claude, ChatGPT or Cursor do the same work as you: it signs in with your UptimeSam account and only reaches the boards you are an admin of.
How much does UptimeSam cost?
UptimeSam is included in the Releasy Suite at $69 a month, alongside Hookfire, Upvoted and Indie Polls, each on its Max plan. On its own site it sells Pro at $19 a month or $190 a year, which is one board, two seats and 25 monitors checked every minute, and Max at $39 a month or $390 a year for unlimited boards and seats, 100 monitors checked every 30 seconds, private and password-protected status pages, status page branding and the MCP server.
Can I try UptimeSam before paying?
Yes. Signing up starts a 7-day free trial of UptimeSam, no card required. Hookfire, Upvoted and Indie Polls each start their own 7 days the first time you open them.
Get UptimeSam with the whole suite
$69 a month for Hookfire, Upvoted, Indie Polls and UptimeSam, each on its Max plan. 7-day free trial, no card, cancel anytime.