Solutions
Who runs next-story
next-story fits teams that run their own Next.js sites and want journey signal an agent can read.
Teams with many Next.js sites
One collector and one database behind every property.
- Every event, token and query scoped to a site
- Per-site token keys through the site registry
- One agent token can read a chosen set of sites
Control-plane and agent builders
Structured journey data an LLM can read without guessing.
- Three fixed endpoints, each with its own scope
- Absolute time windows and rule versions on every response
- no_data and quota_exceeded told apart
Teams that cannot use session replay
Frustration signals without capturing page content.
- No DOM snapshots, video or keystrokes
- Route patterns only, no query strings
- Self-hosted: data stays in your Postgres
See the questions it answers
Example agent questions, each with the endpoint behind it.