ServerStats
Sign inSign up
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.

Start monitoring See the integration guide
ingest.sh
curl -X POST .../ingest \
 -H "x-api-key: $KEY" \
 -d '{
 "endpoint":"/orders",
 "status":200}'
live logs
  • GET/api/orders/:id200
  • POST/api/payments/charge200
  • POST/api/notifications502
app.serverstats.space/overview
Live24h

Hits

0

Error rate

0.00%

Why this exists

The gap between something breaking and you finding out — that's the whole product.

Somewhere, right now, an endpoint starts failing.

No dashboard open. No one watching. Just a status code nobody sees.

checkout-service · logs
POST/api/payments/charge200
POST/api/payments/charge502
POST/api/payments/charge502

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.

Everything after the API key

One ingest endpoint gets the data in. This is what happens to it once it's there.

Real-time analytics

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

analytics · overview
Live24h

Hits

482,190

Error rate

0.42%

Real-time analytics

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

See it in action

The same dashboard you'll be running — real components, no staged demo.

app.serverstats.space/overview
Live · updating in real time

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

Traffic, error rate, and latency at a glance — the first thing you check.

Questions, answered

One API key away from your first event

Sign up, create a key, send a request. The dashboard fills in from there.

Start monitoring