Dianthan documentation
Dianthan is a backend you share across all of your apps. It handles sign-in, billing, usage metering, data, messaging, background work, analytics and feature flags over one HTTP API, so each new product starts with all of that already in place.
How it fits together
Your account owns any number of apps. An app is one product: it has its own users, domains, keys, data and limits. You turn systems on for the apps that need them. Every system is reached through the same base URL, with the same keys and the same error format.
your sites api.dianthan.com systems
────────── ──────────────── ───────
fieldnotes.app ──┐ ┌── identity billing
├── X-App-Id + key ──► one API ──┼── metering data
tally.so ──┘ └── messaging automation
observe flagsA person who signs in to two of your apps has one Dianthan identity and two memberships. Their data in each app is kept separate. You see both memberships in your dashboard.
Where to start
- New to Dianthan: follow the Quickstart. It takes about ten minutes to get from no account to a signed-in user.
- Planning an integration: read Concepts for apps, keys, sessions and how isolation works.
- Working with an agent: point it at Agents and MCP, or give it
/llms.txt, the whole documentation as one plain-text file.
Conventions in these docs
Examples use curl against https://api.dianthan.com, which works from any language. Where a TypeScript SDK call is shorter, it appears next to the HTTP version. Values you replace look like app_… and dn_….
In preview marks a feature that you can design around now but that isn't generally available yet. Its API may still change before it is.