Connectable source types
17
Distinct source kinds the product accepts today. Counts kinds, not connections and not vendors.
Stats
Four numbers we can defend.
Each one is read straight out of the database and labelled with exactly what it counts. Where a flattering number existed but no honest label did, the tile is gone rather than reworded.
Measured
What each number counts.
An em dash means the aggregation returned nothing — usually because the database was unreachable when this page was built. It never means zero, and it is never filled in with an estimate.
Records processed · 90d
9.0k
Items received from connected sources and processed in the last 90 days, across every workspace.
Workspaces active · 30d
1
Workspaces that processed at least one record in the last 30 days. Not accounts, not people, not paying customers.
Model tokens per record · 90d
429
Mean input plus output tokens for the classification pass, over records where that pass recorded them. Excludes synthesis, embeddings and rule evaluation.
recomputed hourly · counts are approximate under concurrency
Not on this page
What we do not publish.
The numbers a page like this usually leads with are the ones we have no way to stand behind. Naming them is more useful than leaving a gap for you to fill in.
User and customer counts
We have signups and workspaces, not a defensible count of people using the product. A workspace is not a person.
Uptime and latency
Neither is captured anywhere in the request path, so any figure would be invented rather than measured.
Stored context volume
Most of what is stored is source activity, not durable context items. A total would describe the wrong thing.
Certifications
We hold none, and this page will not imply one by listing a category and leaving it blank.
Capabilities get the same treatment as figures — the itemised version is the capability ledger, and the roadmap carries what is not built.