Introduction
Poolstatis is source-available, agent-first product analytics for teams that use coding agents to ship software. Instead of expecting a person to translate dashboards or write SQL, it gives an agent a small MCP surface for registering metrics, defining funnels, and asking whether a shipped change is working. The registry preserves meaning: every metric states the decision it supports, every funnel states the journey it measures, and clients query those registered definitions through a typed DSL. Humans retain control through a headless admin that exposes proposals, activation status, keys, recent data, and quality warnings for audit. Teams can use the managed Cloud beta or run a Docker self-host with Postgres and a local MCP runner. The version-pinned public MCP runner is verified; the SDK npm distribution path is not generally available yet. Poolstatis reports observed product behavior. A trend or conversion change can guide investigation, but it does not by itself prove that a release caused the outcome.
Two rules hold the whole system together:
Every metric carries a
purpose— one sentence naming the decision it informs. Every funnel carries agoal— what journey it measures and why.
If you can't name the decision a number informs, you don't track it. That single constraint is what makes an agent's analytics trustworthy instead of noise.
Why it exists
Traditional analytics assume a person is sitting in front of a chart. An agent can write a
feature, ship it, and open the PR — but then it goes blind, because the feedback half of the
loop (ship → measure → decide) lives behind a SQL console and a dashboard UI.
Poolstatis closes that loop. The agent works through a small, typed surface instead of raw SQL, and every number is self-describing.
How it fits together
- Ingest API receives events and entity updates from your product.
- Registry holds the semantic layer: metrics (with a purpose) and funnels (with a goal).
- Query DSL answers questions over registered metrics — never raw tables.
- MCP server exposes all of the above as tools your agent calls.
- Admin panel is a headless console for humans to audit and activate.
When Poolstatis fits
- A coding agent instruments product changes and needs to verify the result after release.
- A product team wants stable metric definitions that both humans and agents can inspect.
- A self-hosting team wants event data and the semantic registry in its own Postgres.
- An MCP client needs narrow analytics tools instead of database or raw SQL access.
Poolstatis is not a replacement for data warehousing, unrestricted BI, or LLM trace observability. Browser Experience is an optional, consent-first interaction signal; it is not full DOM replay.
Agent-first vs dashboard-first analytics
| Concern | Dashboard-first workflow | Poolstatis workflow |
|---|---|---|
| Primary interface | A person navigates reports | An agent calls typed MCP tools |
| Metric meaning | Often documented separately | Required purpose in the registry |
| Funnel meaning | Often inferred from steps | Required goal plus registered metrics |
| Query access | UI builders or SQL | Typed Query DSL over metric keys |
| Human control | Report and workspace settings | Audit and activate agent proposals |
Next: Quickstart.