Analytics for every request, with no script to install
Every HTTP request that reaches your server passes through its reverse proxy, so that is where the platform reads it. Requests, errors, latency, bandwidth, and visitors for every application — without adding a tag, a cookie, or a line of code.
What you get
No tracking script
Collected from the proxy’s access log, so it counts what actually reached your server — including the clients that never run JavaScript.
Latency that means something
p50, p95, and p99 from merged histograms, error rates by status class, and bandwidth — with every deployment drawn as a marker on every chart.
A request explorer
Filter a week of stored requests by status, method, host, path, network, referrer, or duration. Open any one, and pivot on its fields.
Live tail
Watch requests arrive as they happen, filtered the way you want, and pause to read without losing count.
Who your visitors are
Unique visitors, countries, devices, browsers, and operating systems, plus routes grouped into templates so /users/42 and /users/43 rank together.
Alerts on traffic
A raised 5xx rate, degraded p95, a sudden spike, or an application that stops serving traffic altogether — each opens an alert and closes itself when it clears.
In detail
- Client addresses are truncated before they are stored — /24 for IPv4, /48 for IPv6.
- Unique visitors use a daily-salted hash: not reversible, and not joinable across days.
- Sensitive headers are dropped at the proxy, and query string values are dropped by default.
- Stored requests are kept for seven days and export to CSV or NDJSON, each export audited.
- Charts read pre-aggregated rollups: minutes for seven days, hours for ninety, days for up to 400.
- Country data comes from DB-IP Lite, credited on the analytics pages.
- The application’s CPU and memory sit on the same timeline as its traffic.
Works well with
AI traffic
See which AI crawlers read your site, verify them, and catch the impostors.
Alerts
Alerts that open and resolve themselves — in the portal, email, webhook, or Telegram.
Domains and HTTPS
Add a hostname, create the record it shows you, and HTTPS arrives on its own.
Your server is ready when you are
Create an account, connect a VPS, and ship your first application.