ServerStats
Sign in
Built by one developer, running in production

Know what your API is doing before your customers tell you

Multi-tenant API observability and alerting — traffic, error rates, latency, and incidents, reported from any language with a single HTTP call.

Sign in See the integration guide
app.yourdomain.com/overview

Total hits

482K

Error rate

0.42%

Avg latency

118ms

Endpoints

63

GET

/checkout/session

payments-api

2.1%
POST

/orders

orders-api

0.8%
⚠

High error rate

4m ago · payments-api

⚠

Latency spike

1h ago · search-api

Integration

Works from any language

One HTTP endpoint, one API key. No SDK to install, nothing to keep up to date.

1

Create an API key

From API keys in the dashboard, scoped to an environment (development, staging, production).

The key is shown once, at creation time — copy it straight into your service's environment as MONITORING_API_KEY.

2

Send your first event

Report a hit after each request completes — the block below follows the language picked above.

curl -X POST https://api.serverstats.space/api/v1/ingest \
  -H "x-api-key: $MONITORING_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "serviceName": "checkout-service",
    "endpoint": "/orders/:id",
    "method": "GET",
    "statusCode": 200,
    "latencyMs": 42
  }'
3

Or auto-instrument your whole app

Drop-in middleware reports every request without touching individual routes.

cURL is for one-off calls, not a running app — pick Node.js, Python, or Go above to see whole-app middleware you can drop in.

What you get

Everything after the API key

Real-time analytics

Traffic, error rates, and latency the moment they happen — not in tomorrow's report.

Alerting that meets you where you are

Threshold rules and digest summaries, delivered to email, Slack, Discord, or your own webhook.

Multi-tenant by design

Onboard as many clients as you need, each with its own users, keys, and alert rules.

One incident feed

Every fired alert, across every rule, in one chronological feed — not buried in a dozen inboxes.

Inside the dashboard

Every number, one click away

app.yourdomain.com/analytics
GET

/search

search-api

128K
GET

/users/:id

users-api

94K
POST

/orders

orders-api

61K
GET

/inventory

catalog-api

47K

Analytics — timeseries and top endpoints by hits, errors, or latency.

app.yourdomain.com/alerts

Error rate > 5%

Threshold

Traffic silent 15m

Threshold

Weekly digest

Summary

Latency > 800ms

Threshold

Alerts — threshold rules and digests, enabled with one switch.

Why this exists

I didn't set out to build a monitoring platform

I just wanted to know what my own side projects were actually doing in production — which endpoints were slow, which ones were quietly failing at 3am — without paying for an enterprise observability suite built for teams fifty times my size.

So I built the smallest version that could tell me the truth: send a hit, watch it show up, get pinged when something breaks. It kept growing from there — multi-tenant support, real alert rules, an incident feed that doesn't make me check five different places — until it turned into the platform you're looking at right now.

Still one developer. Still running in production.

N