Capture-first & zero-config
Why Atune captures behavior broadly by default and exposes nothing to configure.
Two principles shape everything about how Atune works. They are why setup is one command and why there's nothing to tune.
Capture-first
Atune captures behavior broadly and automatically from the moment the middleware is installed. You don't declare which events matter up front, because you rarely know that on day one — and understanding that depends on hand-picked events is understanding built on a guess.
- Every server request becomes a signal, resolved to an account and user.
- Capture is fire-and-forget: it never blocks, delays, or breaks a request.
- Request bodies are never read. No passwords, tokens, or card numbers.
The result: the day you first ask a question, there is already history to answer from.
Zero-config
Configuration is failure. Every manual rule is evidence that the product could have been smarter.
Atune exposes no health-score builder, no rules engine, no event schema to maintain. There is nothing to configure because understanding is meant to emerge from behavior, not be assembled by hand.
Emerge, don't configure
Software should learn what success looks like and recognize when people struggle. Humans refine that understanding — they don't create it from scratch. That's the difference between an analytics tool you operate and infrastructure you install.
What this means for you
- No onboarding project. Install, and signals start flowing.
- No decisions to get wrong. There's no schema to design badly, no rule to misconfigure.
- The API is the product. You query understanding; you don't operate a dashboard to produce it.
Next: how those raw signals become answers in Understanding & the Context Layer.