Atune docs

Customer-understanding infrastructure for B2B SaaS. Install one SDK; understanding comes back through a queryable API.

Atune is the understanding layer for the software stack. You install it the same way you install authentication or payments — one SDK — and it captures how your customers use your product. You then ask grounded, cited questions about any account, user, or feature through a single understand() call.

The API is the product. There is no dashboard to babysit.

const answer = await understand("account:acme", "why did they go quiet?");
// { knows: true, answer: "Acme's weekly active seats fell from 8 to 2…",
//   confidence: 0.72, citations: [...], recommendedNext: "…" }

Start here

Quickstart

One command wires a live Next.js app: npx atune init.

Manual setup

Add the middleware yourself — any framework, no CLI.

Concepts

Capture-first, zero-config, and how understanding emerges.

SDK reference

identify, group, understand, middleware, and the MCP server.

What Atune does

Captures behavior automatically. The middleware records every server request as a signal, resolved to the account and user. Fire-and-forget — it can never block or break a request.
Takes the identity you choose to send. identify() and group() turn user u_123 into "Kari at Acme". Personal data flows only under a data-processing agreement.
Answers questions, grounded and cited. understand() returns a plain-language answer with citations and a confidence score — or says knows: false when there isn't enough understanding yet, instead of guessing.

Zero config

There is nothing to configure. No health-score workshop, no rules to define, no dashboard to set up. Understanding emerges from behavior; you refine it, you don't build it from scratch.