You still wait for a user to tell you it's broken.

Relia watches your product, learns what's normal for it, and tells you only what needs you, with the cause and what to do next. Built for founders who don't have an SRE.

Start free Try the live demo Watch the one-minute demo

Free for one product. Set up in about five minutes. The live demo needs no sign-up.

Relia · its own productsnapshot from 20 Oct

2 things need you.

UsersNeeds you
133 sessions from 10 visitors in 24 h; 10,857 requests, 10 failed
Page speedNormal
Last 7 days (p75): page load 2.3 s (good), responsiveness 64 ms (good), layout shift 0.03 (good)
APIsWatch
Nothing you need · 2 worth watching
DatabaseNormal
33,752 database calls in 24 h (clickhouse, mongodb), 50 failed; slowest p95 1.9 s
ServersNeeds you
2 hosts in the last hour; highest CPU 16%, memory 68%, disk 90%
Uptime & checksNormal
Relia's checks: 3 of 3 passing
PromisesWatch
3 promises; lowest error budget 34% left
Status pageNormal
Published: 3 of 3 parts operational

Relia is watching 8 parts of its own product. Open the public status page

One minute, start to finish.

Setup, the alert, the write-up, the fix plan and the check that your fix worked, on a sample project.

How it works.

Four stages, each shown the way the app shows it for Relia's own product. Scroll on, or drag the slider; on a phone, swipe or tap a stage.

First, it watches everything

Sessions, requests, database calls, servers, uptime and agent runs, drawn as one map of your product.

Map

6 parts of your system are failing right now.

Users

Browser users

507 sessions

Services

backend4

1.2k requests · p95 543 ms

SLO · 34% budget left

Depends on

mongodb/relia1

2.7k calls

clickhouse/default1

1.0k calls

mongodb/admin1

4 calls

127.0.0.1

5 calls

Hosts

worker-11

CPU 1% · mem 54% · disk 67%

api-12

CPU 8% · mem 72% · disk 90%

What Relia hands you.

Five things, all written from your own project's evidence. Pick one to see it the way you'd get it.

An incident, explained

Every problem that needs you, in plain words: what happened, why Relia thinks so, and one thing to do next. Written from the requests, sessions and server metrics it collected, and it names who was hit: “38 customers, 9 on Pro”. Once it is fixed, one click writes the postmortem.

Arrives the moment something needs a fix.

Needs youHighInfrastructurecame back

The server api-1 is almost out of disk space, which could make the whole backend stop working.

153 occurrenceslast seen just now Host

What happened

The server named api-1 has its disk 90% full, and it was 94% when this warning was first logged. The warning has come up 152 times since October 14, most recently on October 20. Nothing has failed for users yet: the impact shows 0 visitors, 0 sessions and 0 failed requests. A full disk can make the backend start failing, so the space should be freed before that happens.

Why Relia thinks so

Confidence high: linked end to end with a code or infrastructure cause

Seen in host only; not yet linked to another part of your stack.

1 other possibility

Do this next

Free disk space on api-1 by clearing old logs and temp files, then check that the backend still runs normally.

I'm on it Show how to fix

Written by Relia

It checks your fix against live traffic.

A fix isn't done when you ship it. Relia keeps watching until real traffic says it held.

Relia finds it
An incident, with what happened and one thing to do.
You ship a fix
Relia notices the deploy on its own, or you press “I fixed it”.
It watches live traffic
At least 20 requests over 15 minutes without the problem; 30 quiet minutes for server and UX issues.
You hear the result, once
“Your fix worked” or “Still happening after your fix”. Too little traffic after 24 hours: “Couldn’t confirm”.

Your fix worked

Back to normal. Was: Signed-out users were refused by GET /api/v1/vitals on /vitals

Your backend deploy 20314b0d landed at 15:40. No recurrence in the 30 minutes after it, so Relia marked this fixed.

1 user affected

Open in Relia

Watching
Verified

Fix confirmed

Fixed: no sign of the problem in 30 min and real traffic since backend 20314b0d.

Deploy of backend 20314b0d · 15:40

Deploy and Relia notices on its own; or press “I fixed it” and it watches for you. If it comes back, you hear “still happening after your fix”, once.

Ask it anything about your product.

Should I worry about the servers?

Mostly no, but disk is at 88%, so keep an eye on it.

You have 2 hosts in the last hour: highest CPU is 9%, memory 72%, disk 88% Servers.
CPU and memory look comfortable right now Servers.
Earlier, CPU on both servers peaked at 99% (api-1) and 92% (worker-1) during the /investigations problem on GET /api/v1/projects, and api-1's memory hit 91% incident 4. You marked that fixed and Relia is confirming it from real traffic; it has been quiet for 1 minute so far incident 4.
Relia doesn't show how fast the disk is filling, so I can't say when it would run out.

Answers use only this project's data and link to the evidence.

Or start from what Relia suggests for this project:

What is wrong with the servers?
Should I worry about my promises?
What changed since yesterday?

Every claim cites the evidence. Relia can also draw a chart or build a dashboard when you ask for numbers. Ask it yourself in the live demo

Fix it where you code.

Your editor sees your code. Relia sees production: which deploy broke it, the path from the button to the line, and which customers it hit. Connect the two once, and your AI assistant fixes the right thing, then Relia confirms it on live traffic.

Works with
Claude Code
Cursor
VS Code
Any MCP client

orders/service.py

def create_order(order):

customer = load_customer(order["customer_id"])

items = price_items(order["items"])

method = order.get("shipping_method") or STANDARD_SHIPPINGverified live

quote = shipping.quote(method, items)

return save(customer, items, quote)

Your AI assistant Relia connected

Use Relia: what's broken in production?

relia_status1 thing needs you · Checkout fails since 10:02, 4 min after deploy 1.42.0

relia_get_incidentPay → POST /api/orders → 500 KeyError at orders/service.py:88 · 38 customers hit, 9 on Pro · 31 pressed Pay again

Deploy 1.42.0 made the shipping choice optional in the checkout form, but line 88 still requires it. I've given it a default. Deploy, and Relia checks it on live traffic.

relia_get_incidentFix verified: 64 orders in 18 min, no failures

See how the MCP server works

Connect once per project. Relia only reads; your assistant changes code in your editor, with your approval. It can even set Relia up for you.

How it works

It reaches you where you already are.

Email
Needs your attention
The server api-1 is almost out of disk space, which could make the whole backend stop working.
The server named api-1 has its disk 90% full, and it was 94% when this warning was first logged. The warning has come up 152 times since October 14, most recently on October 20.
Do this: Free disk space on api-1 by clearing old logs and temp files, then check that the backend still runs normally.
153 occurrences so far
Open in ReliaI'm on it
Slack
@you you're on call. You're on call: The server api-1 is almost out of disk space, which could make the whole backend stop working.
You're on call
The server api-1 is almost out of disk space, which could make the whole backend stop working.
Relia found a problem that needs a fix. Press “I'm on it” so the next person isn't paged.
Do this: Free disk space on api-1 by clearing old logs and temp files, then check that the backend still runs normally.
153 occurrences so far
Open in ReliaI'm on it
ClickUp
Needs your attention: The server api-1 is almost out of disk space, which could make the whole backend stop working.
The server named api-1 has its disk 90% full, and it was 94% when this warning was first logged. The warning has come up 152 times since October 14, most recently on October 20.
Do this: Free disk space on api-1 by clearing old logs and temp files, then check that the backend still runs normally.
153 occurrences so far
Open in Relia · I'm on it
Jira
New issue
[Relia] The server api-1 is almost out of disk space, which could make the whole backend stop working.
Needs your attention: The server api-1 is almost out of disk space, which could make the whole backend stop working.
Do this: Free disk space on api-1 by clearing old logs and temp files, then check that the backend still runs normally.
153 occurrences so far
Open in Relia · I'm on it
PagerDuty
Triggered
The server api-1 is almost out of disk space, which could make the whole backend stop working.
Severity
error
Source
relia
Impact
153 occurrences so far
Open in Relia

Only what needs a fix. At most five an hour, the rest bundled. On-call rotation and escalation built in.

You decide how much it tells you.

These are Relia's real settings. Flip one to see the rule it follows.

Email me only when something needs me.
At most 5 messages an hour; the rest arrive bundled. Nothing for things Relia is only watching.
Send me one summary a day.
Let Relia keep its own checks and promises.
Ask me before adding an uptime monitor.
One question a day at most, five a week. “Not sure” is always an answer.
Keep everything over my monthly units.

Running in five minutes.

Two commands in your app, or one sentence to your AI assistant. The setup finds your API and web app, asks two questions, and Relia starts learning from the first request.

Install the SDK
npm install relia-sdk
Node and browser apps. For Python: pip install relia-sdk.
Run the setup
npx relia-sdk@latest init
It finds your API and web app, asks two questions and writes the files. Python: python -m relia. Or tell your AI assistant “Set up Relia”.
Restart your app
Your project’s Setup tab turns green as data arrives, and Relia starts learning what’s normal.

Terminalmy-app

$ npm install relia-sdk
$ npx relia-sdk@latest init

◆ RELIA Observability Setup

 What should Relia set up? › Everything Relia found here: Express API + React app (Vite)
 How would you like to set up your project? › Select existing project (my-app)
 Select your project: › my-app (production)
   Service "my-app" created
   Service "my-app-web" created
 Also record screen replays for this app? (y/N) › n
 Tell Relia who your users are? (Y/n) › y
[relia] done — watching: requests & errors, user sessions, project: 6a744ab9c3b399376c2a55d9
  generated: relia.tracing.js, src/relia.ts
  Next: restart your app and open it. Relia shows the first request and session within a minute.

relia.tracing.js

// Generated by relia-sdk. Re-run `npx relia-sdk@latest init` to change.
require('relia-sdk/node').start({
  serviceName: "backend",
  projectId: "6a744ab9c3b399376c2a55d9",
  projectName: "my-app",
  otlpEndpoint: "https://devotel.tryrelia.com/v1/traces",
  key: "relia_live_…",
});

// Generated by relia-sdk. Re-run `npx relia-sdk@latest init` to change.
import { Relia } from "relia-sdk"

Relia.init({
  endpoint: "https://devreliaapi.tryrelia.com/api/v1",
  project_id: "6a744ab9c3b399376c2a55d9",
  key: "relia_live_…",
  project_name: "my-app",
  service_name: "web",
  captureText: false,
  replay: false,
})

"""
RELIA APM Tracing Initialization
Import and call `init_tracing()` at the top of your application entrypoint before importing web frameworks.
"""
import relia

def init_tracing():
    return relia.start(
        service_name="backend",
        project_id="6a744ab9c3b399376c2a55d9",
        otlp_endpoint="https://devotel.tryrelia.com/v1/traces",
    )

def setup_fastapi(app):
    from relia.integrations.fastapi import instrument_fastapi
    instrument_fastapi(
        app,
        service_name="backend",
        project_id="6a744ab9c3b399376c2a55d9",
        otlp_endpoint="https://devotel.tryrelia.com/v1/traces",
    )

def setup_flask(app):
    from relia.integrations.flask import ReliaFlask
    init_tracing()
    ReliaFlask(app)

if __name__ == "__main__":
    init_tracing()

No agents to install, no dashboards to build. Your project key, two lines, done. Full setup guide

Works with what you already run.

Node: ExpressFastifyNext.jsNestJSKoaHapiBullMQKafkaGraphQL
Python: FastAPIDjangoFlaskCeleryrequestshttpx
Data: PostgreSQLMongoDBMySQLRedisClickHouse
Browser: ReactVite source mapsweb vitals
AI: Vercel AI SDKagent runs in Node and Python
Deploys: GitHub ActionsRenderVercelwebhooks

Plans
	Free$0	Growth (recommended)$12 a month	Pro$29 a month
Units a month	500,000	5 million	20 million
History	7 days	30 days	90 days
Services	3	10	Unlimited
Uptime monitors	5	20	50
Ask Relia questions a month	30	80	180
Fix plans a month	3	30	50
Incident write-ups a month	300	2,000	5,000
Postmortems a month	2	10	30
Synthetic check runs a month	3,000	20,000	60,000
Status page on your own domain	No	Yes	Yes
Over the limit	Sampled, never cut off	Sampled, or paid extra use	Sampled, or paid extra use
Extra use	Not available	$2 per million units, with a limit you set	$2 per million units, with a limit you set
Choose a plan	Start free	Start on Growth	Start on Pro

Plans

Free$0
Units a month
500,000
History
7 days
Services
3
Uptime monitors
5
Ask Relia questions a month
30
Fix plans a month
3
Incident write-ups a month
300
Postmortems a month
2
Synthetic check runs a month
3,000
Status page on your own domain
No
Over the limit
Sampled, never cut off
Extra use
Not available
Start free
Growth$12 a month
Units a month
5 million
History
30 days
Services
10
Uptime monitors
20
Ask Relia questions a month
80
Fix plans a month
30
Incident write-ups a month
2,000
Postmortems a month
10
Synthetic check runs a month
20,000
Status page on your own domain
Yes
Over the limit
Sampled, or paid extra use
Extra use
$2 per million units, with a limit you set
Start on Growth
Pro$29 a month
Units a month
20 million
History
90 days
Services
Unlimited
Uptime monitors
50
Ask Relia questions a month
180
Fix plans a month
50
Incident write-ups a month
5,000
Postmortems a month
30
Synthetic check runs a month
60,000
Status page on your own domain
Yes
Over the limit
Sampled, or paid extra use
Extra use
$2 per million units, with a limit you set
Start on Pro

A request or a log line is 1 unit, a session minute 35, an agent run 5. One project per plan; your first project is free. Prices exclude tax. Every plan includes the MCP server for your AI assistant, a public status page, Slack alerts and People (which customers each problem hit).

Questions

Will Relia change my code or my servers?

No. Relia reads telemetry your SDK sends and tells you what it found. It never opens pull requests, and it never acts on your servers on its own: when an incident follows a deploy or a memory leak, it can propose a rollback or a restart through Render, Vercel, GitHub Actions or a webhook you connected, and that runs only after an owner or admin approves it. The only things it changes on its own are inside Relia: its own checks, promises and learned patterns, each logged with Undo.

What does it watch?

Users' sessions (clicks, inputs, navigation, errors; no screen recording by default), API requests, database calls, servers (CPU, memory, disk), uptime from outside, your status page, web vitals and AI-agent runs. One project per app.

Does it work with Cursor, Claude Code or VS Code?

Yes, through MCP. Create a token in your project settings and paste the one line Relia shows into your tool. Your AI assistant can then read what needs you, incidents, fix plans and Ask Relia answers, and fix the code in your editor. A token is read-only, for one project, and every read is in your audit log. Details: tryrelia.com/mcp.

Can Relia tell me exactly which customers hit a problem?

Yes, once you tell it who is signed in: one Relia.identify() call in your web app (and setUser on your server). Incidents then say “38 customers, 9 on Pro” instead of “38 visitors”, the People page shows each person's sessions and errors, and you can reach out before they write to you. Only the id, e-mail, name and plan you pass are kept; names and e-mails never go to the AI or into alerts, and you can export or erase anyone.

How long does setup take?

About five minutes. npx relia-sdk@latest init finds your API and web app, asks two questions and writes the config; or ask your AI assistant to “Set up Relia”. Node (Express, Fastify, Next.js, NestJS, Koa…) and Python (FastAPI, Django, Flask…) are supported.

How is “normal” decided?

From your own traffic: four weeks of per-route behaviour (error rate, speed, volume by hour of the week) and what your users usually do. Relia raises latency or error alarms only when they are also above your app's learned normal, so a busy Monday morning is not an incident.

Will it flood me with alerts?

No. Only incidents that need a fix are sent, at most five an hour (the rest bundled), one “came back”, one “resolved” per incident per day. Everything else waits for the daily summary or Home.

What happens when I go over my units?

Nothing is cut off and nothing already stored is deleted. New normal requests and sessions are kept 1 in 10 until the month resets; errors, slow requests and anything an incident points at are always kept in full. Growth and Pro can switch on paid extra use instead, with a monthly limit.

Where is my data and how long is it kept?

In Relia's databases (MongoDB Atlas and ClickHouse), scoped to your project. Request and session data is kept for your plan's history (7, 30 or 90 days); older data is deleted. Statement values in database queries are masked in the SDK before they leave your server.

Can my team use it?

Yes. Invite members as owner, admin, member or viewer. On-call rotation, Slack mentions and PagerDuty are built in.

yourapp.comFree

Your product right now

Relia hasn't seen data from your product yet. The parts it watches appear here as they send their first requests.

Sign up and name your project.
Run npx relia-sdk@latest init in your app.
Your first requests arrive and Relia starts learning what's normal.