What is Stealth Analytics?

Stealth Analytics is a privacy-first, developer-oriented analytics platform built around one core idea: if a system can make a POST request, it can send telemetry to Stealth. Instead of limiting tracking to browser pageviews, it accepts raw event payloads from a tiny frontend script or directly from backend services, edge workers, payment funnels, or hardware projects. It is aimed at developers who want speed, minimal footprint, and freedom from per-domain pricing.

What makes it different from traditional analytics

Most analytics platforms are built around the browser. They assume your data comes from a JavaScript snippet watching page loads. Stealth Analytics treats the browser as just one possible source.

The site states its core capability plainly: "If it can make a POST request, we can track it." That means the same platform can ingest:

• Web traffic from a frontend script
• Backend system events from a server
• Custom conversions from a payment funnel
• Telemetry from a background worker or a robotics project

This is a meaningful shift. Traditional tools often require a specific SDK or software kit. Stealth's documented approach is to accept a standard JSON payload sent to an edge endpoint, so any language or framework that can issue an HTTP POST can participate.

How ingestion works

There are two documented channels, and you can use either or both.

Frontend script

A small script is dropped into the HTML <head> for web traffic. The site describes the payload as 0.7 KB and the install as 1 line.

REST API

You bypass the browser entirely and hit the edge workers directly. The documented pattern is a standard JSON payload:

await fetch('https://api.stealth...', {
  method: 'POST',
  body: JSON.stringify({ name: 'sale' })
});

The expected result is that the event lands in your dashboard, whether it originated from a browser, a server cron job, or a custom backend process. The site frames this as "two minutes to first event."

Footprint and performance

Analytics scripts can hurt performance scores if they are heavy or block rendering. Stealth positions its script as "virtually invisible to the browser," loading in milliseconds without blocking rendering.

The site provides a direct size comparison:

If page speed or Core Web Vitals matter to you, the 0.7 KB figure is the headline number. Smaller scripts generally mean less main-thread work and less render-blocking risk, though real-world impact also depends on how and where the script is loaded.

Pricing and usage model

Stealth does not charge per domain. Its usage-based buckets cover your entire portfolio, so tracking one site or fifty counts toward the same event limit. The site lists three tiers:

All tiers include full CSV exports. The "upgrade" signal on the page points to the paid tiers, so the free plan is a real entry point but with a 30-day retention cap and a low custom-event ceiling.

Who it is for

Stealth Analytics fits developers and small teams who:

• Want to track events beyond pageviews, including server-side and backend processes
• Prefer a REST API over a vendor-specific SDK
• Care about a minimal frontend footprint
• Run multiple sites and do not want per-domain billing
• Are comfortable formatting JSON payloads and making HTTP requests

It is less suited to non-technical users who expect a plug-and-play dashboard with no code, or to teams that need the deep out-of-the-box integrations and reporting ecosystem of a larger platform.

Mobile and dashboard

The dashboard is described as fully responsive and engineered to feel like a native app, so you can check active web traffic on a commute or verify a server cron job from your phone. This matters if you monitor systems away from a desk.

What to verify before committing

The site does not publish details on data residency, retention enforcement mechanics, or how privacy compliance is handled beyond the "privacy first" positioning. If those are hard requirements for you, confirm them directly before migrating. The free tier is the lowest-risk way to test whether the ingestion model fits your stack: send one frontend event and one backend event, then confirm both appear in the dashboard.