Seiton logoSeiton
How it worksFree toolsLabsPricingFAQLive demo
Log inGet my first briefing

Documentation

Seiton documentation

Seiton reads the tools your SaaS already runs on, scores what it finds across 8 dimensions, and sends you one briefing at 08:30 local. This is how every part of that works.

What it is

A chief-of-staff layer over the stack you already pay for. You connect billing, analytics, search and error tracking; Seiton syncs them on a schedule, turns the differences into signals, and tells you the two or three things that actually deserve your morning.
  • Read-only. The single object Seiton ever creates in a connected tool is one webhook endpoint at a billing provider, and disconnecting deletes it again.
  • Missing is not zero. A source that has never synced shows as insufficient data, never as a confident 0.
  • One number per fact. Two tools reporting visitors do not get summed — one owns the field, the other is context. See Metrics & ownership.

How a briefing is produced

  1. 1Connect. Each category — billing, SEO, reliability, analytics, hosting, database — holds at most one primary source. Billing is the only one worth connecting first.
  2. 2Sync. A cron job pulls every connected source every 6 hours; billing webhooks push the urgent events in between.
  3. 3Snapshot. Results are written to one daily snapshot per project, each field tagged with the source that owns it.
  4. 4Score. The engine compares today against the baseline, raises signals, and computes 8 dimension scores plus a weighted composite.
  5. 5Decide. Today picks the few items worth acting on and attaches the page that answers each one.
  6. 6Deliver. At 08:30 local the same content goes out by email, Slack, Discord or webhook.
The Seiton project overview with Today, Live Pulse, Reliability and key metrics
The project overview. Today is the decision, Live Pulse is the diagnosis, key metrics are the evidence.

The words used everywhere

TermMeaning
ProjectOne product: a domain, its connected sources, its briefing and its team.
SourceA connected provider — Stripe, Search Console, Sentry, PostHog. Each category slot holds one primary.
SnapshotThe day's metrics for a project. Each field records which source wrote it.
SignalA detected change with a severity — churn moved, errors spiked, rankings dropped.
DimensionOne of the 8 scored areas: revenue, retention, growth, SEO, reliability, infrastructure, product, profitability.
ConfidenceHow fresh the sources behind the score are. It never changes the score itself.
TodayThe short list of items the briefing leads with, each one with an action link.

Start here

Quickstart

Add a site, connect billing, install the snippet, read the first briefing. 14 days, no card.

Dashboard tour

What each page shows and which question it answers.

Integrations

Every provider, what it powers, and exactly how to connect it.

Daily briefing

Delivery time, channels, recipients, and sending one on demand.

Reference and trust

Developer reference lives on its own pages: REST API, CLI and MCP server. They share one token type, one envelope and one rate limit — start here if you want an agent reading your metrics.

What is read, what is stored, and how to revoke it is on the Security page, with the Privacy policy and the DPA.

Want to look before you connect anything?

The live demo is this same dashboard running on sample data — every screenshot in these docs is captured from it.

Next

Quickstart

Something here wrong or missing? hello@seiton.online