Uptime monitoring
Your site says 200. Your app is still broken.
Uprail checks your pages, APIs, cron jobs and the API accounts your product runs on, and tells your team the minute one stops working, including the failures a green ping misses.
The outages a simple ping never sees
The 200 that's really an error
Your health route answers 200 with {"db":"down"} inside, or a framework error page. Uprail reads the body: text that must or must not appear, and JSON rules like status = ok or queue.depth < 500.
The API account that ran dry
OpenAI out of quota, DeepSeek or DataForSEO balance at zero, a Stripe key someone revoked. Your site is up and every request that matters fails. Uprail checks the account itself, with a key you give it.
The cron job that stopped
Backups, invoices, a queue drainer. Nothing errors when a job just never runs. Each job pings a URL, and silence past the deadline opens an incident.
The slow page and the expiring certificate
Down includes slower than the limit you set, and a certificate that expires in 14 days. Both alert before your users notice.
How it works
- 1
Add what to watch
A URL, a heartbeat or a provider account. Test a URL before you save and see exactly what Uprail sees.
- 2
It checks every minute
From outside your network. One failed check is a blip, so an incident opens only after the number of failures in a row you pick.
- 3
You hear right away
Email to your team, Slack, or a signed webhook into anything else. A second message when it's back, with how long it was down.
- 4
Your users see a status page
A public page with the monitors you pick and 90 days of bars. Names and up or down only, never your URLs or keys.
One price per workspace, not per seat
Every new account gets 14 days of Team on its first workspace.
Free
$0 forever
- ✓20 monitors, checks every 5 minutes
- ✓3 heartbeats
- ✓Email alerts to your team
- ✓1 status page
- ✓3 people
Team
$19 a month per workspace
- ✓200 monitors, checks every minute
- ✓500 heartbeats
- ✓Provider checks: OpenAI, DeepSeek, DataForSEO, Stripe
- ✓Slack and signed webhook alerts
- ✓10 status pages, no Uprail link
- ✓25 people
Team is included in the Railhq Pass, with every other Rail app.
Questions
- What counts as down?
- A status code you didn't list as healthy, a timeout, a body missing the text you need (or showing the text you don't), a JSON rule that fails, slower than your limit, or a certificate close to expiring. For heartbeats, a ping that doesn't arrive in time or a call to /fail.
- Is it safe to give Uprail my API keys?
- Provider keys are encrypted at rest, never shown again after you save them, and only used to read the account's balance or check the key works. Use a restricted or read-only key where the provider offers one, and revoke it any time.
- Can my AI assistant use it?
- Yes. There's an API and an MCP server, so Claude or ChatGPT can list what's down, read an incident, add a monitor, pause one during a deploy, or acknowledge an incident. Read keys can only look.
- What happens when the trial ends?
- The workspace moves to Free. Nothing is deleted: checks slow to every 5 minutes, provider checks stop, and Slack and webhooks pause until you subscribe.