Better Stack alternative for teams who only wanted uptime checks
Logdash gives you the HTTP monitors, status page and alerts without the on-call schedules, escalation policies and incident timelines you are being billed for and never configured.
Better Stack is a competent incident management platform that happens to include uptime checks. If you run a rotation, escalate to a second responder, and write postmortems afterwards, it earns the money. The part small teams actually use is much narrower: is the API answering, tell me on my phone, and show customers a status page while I work out what happened.
The bill tracks the suite rather than the usage. Monitors are priced per monitor, log ingestion is priced by volume and retention, seats are priced per person, and the plan you land on is sized by incident tooling instead of by the four checks you run. The paging features are the expensive ones and they are the exact features a three-person team never sets up, because the rotation is one phone and the escalation policy is your co-founder.
Logdash does the narrow version on purpose. HTTP checks with status code and response time, push heartbeats for background jobs, a public status page with a custom domain on Pro, and alerts on Telegram or a webhook. No schedules, no escalation ladders, no acknowledgement tracking. If the second name has to get called when the first one sleeps through, that is a real requirement and Better Stack has it.
The health check the monitor reads
export async function GET() {
try {
await sql`select 1`;
return Response.json({ ok: true });
} catch {
// 503, not 200 with a body the monitor cannot read
return Response.json({ ok: false }, { status: 503 });
}
}- Recreate the monitors One monitor per app, one URL each. Every check keeps the status code and the response time, and the uptime history is drawn from those rather than a separate counter.
- Move the status page Publish a status page and repoint the DNS record your customers already use. Custom domains are a Pro setting, so the address on your support docs does not need editing.
- Retire the escalation policy Connect Telegram, take the staging app down on purpose, and watch the alert arrive with the failing endpoint in it. That is the whole on-call configuration, and it behaves the same at 4am as it does at 4pm.
Better Stack status page API alternative
Better Stack already exposes its pages. Add /index.json to any status page URL and you get public JSON with no token, and the authenticated API manages pages, resources and status reports. So the API is not the edge. Logdash serves a published page at /v1/status_pages/:id with no key and open CORS, so a browser can call it straight from your site. On top of it ships a typed client, a status page component for React or Svelte that follows your shadcn theme, and a Next.js starter. Better Stack wins on writes: its API posts status reports, and Logdash has no incidents to post.
# Better Stack: any status page as public JSON
curl https://status.example.com/index.json
# Logdash: the same idea, no key
curl https://api.logdash.io/v1/status_pages/your-status-page-id
# Then the page itself, as a component in your Svelte app
npx shadcn-svelte add https://logdash.io/r/svelte/status-page.jsonLogdash vs Better Stack
| Feature | Logdash | Better Stack |
|---|---|---|
| On-call schedules and escalation | Not built | Rotations, escalation policies, acknowledgements |
| Phone and SMS alerts | Telegram and webhook only | Phone, SMS, Slack, email and more |
| Uptime checks with response time | Both stored on every check | Both stored on every check |
| Heartbeats for background jobs | Pro only, a ping every 15 seconds, no grace period | Heartbeat monitors with a period and grace |
| Cost at four services and one person | Free plan covers five monitors | Priced as an incident platform |
| Logs | Eight SDKs, retention by plan | A full log platform billed by volume |
| Source code | AGPL-3.0 licensed, public repository | Closed source |
When Better Stack is the better pick
- You have a genuine on-call rotation. Schedules, escalation and acknowledgement tracking are the product, and Logdash has none of it.
- You need a phone call, not a Telegram notification that a do-not-disturb setting can swallow.
- Your logs already run through them at volume, and moving ingestion is a far bigger job than moving four monitors.
- Someone external asks for incident timelines and postmortems held in one system.
What migrating costs
The monitors take twenty minutes and the status page takes a DNS change and a wait. The part that is not free is the habit. If your team currently relies on an escalation policy to guarantee somebody answers, a Telegram channel is a downgrade, and it is better to know that now than to discover it during the first incident after the switch. Run both for two weeks and cancel only once you have missed nothing.