Analytics that matter.
The read side of the platform pack: the door where a business reads itself — events in by automatic instrumentation, answers out to the person who must act — behind a front door that serves today, with every gate to the rest stated in the open.
Every other function of a small business has become a metered call — compute, state, models, money-in. Measurement has not. To see what the business did, the standard offer is still a toolchain with a department hiding inside it: engineers to instrument, pipelines to keep alive, a warehouse to model, dashboards someone builds and then quietly stops maintaining. The product-analytics wave shortened the pipeline and kept the assumption — an engineer wires the events, an analyst reads the charts. For a business run by a lean team, that assumption is a tax; for a business run by agents, it is a contradiction. A business that runs itself but cannot read itself is not autonomous — it is unsupervised.
The tax lands hardest exactly where the estate's premise lives: on businesses too small to staff anything. The write side of their stack is already automatic; the read side — the layer where outcomes become visible in time to change decisions — is the one still priced like headcount. That is the gap this door is filed against.
Every sibling door in the platform pack sells to the holder of a unit: functions.do the unit of work, workflows.do the sequence, database.do the unit of state, llm.do the unit of inference, payments.do the revenue to collect — and platform.do to the agent-native business composing them all. Everything those doors run emits events. This door is where the events become answers: not another runtime, but the pack's read side — measurement as a service, keyed to the estate's registry coordinate for it (noun Analytics, verb analyze, category business/metrics).
The boundary is a rule, not a vibe: arrive holding something to run, store, route, or charge — a sibling door serves you. Arrive holding a question about what it all did — what happened, what is changing, what should change — this door serves you. One ICP, one motion: the decision-owner without a data team, bought as a business subscription, not integrated as a developer project.
The door's verbs, in the grammar the apex itself uses:
The live apex advertises exactly this capability set — automatic instrumentation, custom dashboards, AI-powered insights, SQL analysis, real-time tracking — and this record treats that as the door's stated ambition, not its demonstrated product: today the apex's calls to action lead to the platform's shared docs, not to a signup that shows you your own events. The apex also headlines speed and scale phrasing; this record adopts no performance or scale figure until benchmarks publish with their method and window. Capability claims post behind this gate.
Concreteness over adjectives: each door below was checked cold on 2026-07-30 and carries its own state and its own evidence URL — never one URL evidencing several domains. Serving is a liveness fact, not a tenancy claim: nothing here asserts external customers, instrumented tenants, or a usage roll. Those publish behind their own gates.
analytics.do serves. The front door is live under the platform's
masthead — "Track Everything in Real-Time | AI-Powered Analytics
Platform" — and sells this layer in its own words: automatic
instrumentation, custom dashboards, AI-powered insights "without data
engineering teams", with an FAQ covering auto-tracked metrics, query
scale, anomaly detection, privacy, and SQL analysis.
The gateway routes this service as a named door today: GET https://apis.do/analytics returns a machine-readable JSON record — no
login, no signup — naming the service analytics, its domain
analytics.do, its description "Real-time Analytics", its category
events, and its status available.
docs.platform.do serves — the platform's shared documentation surface,
which is where every docs link on this door's apex points today. Shared
docs are stated as shared: no analytics-specific docs surface is claimed
here.
platform.do serves — the operator's front door, whose own record files
this pack under the same claim discipline this record follows.
The ambers, worn in the open — each the exact distance between what serves and what this door intends to be. One of them runs the unusual direction: the estate's own books lag the live door.
The domain's own machine door answers the wrong thing today: the
gateway's service record points its also link at analytics.do/api,
which returns an HTML page wearing the sibling gateway's masthead
("APIs.do — Connect Any API…") — even to a caller asking for JSON — and
the record's linked events collection at apis.do/analytics/events
answers 404. A machine that follows the estate's own pointers to this
service finds a page addressed to humans about a different door. The
claim flips when the catalog serves at the address the gateway already
advertises.
analytics.do/llms.txt answers 500 today — the machine index errors
rather than serving or cleanly not existing. Stated at face value; the
claim flips when the index serves.
The estate's domain registry still files analytics.do at status planned — priority P1, tier pro — filed before the door lit and not yet updated to match the live surface. The record reports the books at face value in both directions: the door is posted above with its evidence, and the filing is reported here as it stands until the registry flips.
Primary motion is B2B — a deliberate departure from the pack's B2D
default, and the motion boundary with every sibling door: the buyer is
the business's decision-owner, who evaluates at the apex in business
language and converts at the first question answered about their own
business, not a developer who converts at the first deploy. The write
path being automatic is what makes the motion possible — instrumentation
that needed an engineer would silently turn this back into a developer
door. Secondary is B2A: a metric an agent can read is a decision an
agent can make, and the first step already serves — the gateway returns
this service's record, status available, to a machine with no login.
The rest of the machine motion is exactly as far along as the bindings
slide says: the domain's own machine doors answer the wrong thing today,
and nothing about that motion is claimed in present tense until they
answer the right one.
Layer-1 economics at the read grain: the collection and query substrate is a fixed cost run once for everyone; each additional business read is a subscription on it, so blended margin improves with occupancy while the pro tier prices the answers, not the plumbing.
The registry files this door at tier pro — a paid product, and the pack's clearest business-priced door: the buyer pays for answers, not for compute hours. That is the only pricing fact this record asserts. No regulatory floor exists anywhere in this function — nothing in reading a metric reserves a step for a statutory person — so the implementation mix migrates all the way to Code, and the marginal cost of one more business reading itself approaches the substrate's floor.
Subscription at pro tier is the filed model; the plan and its price bind when they post at the door's own surface — not before, and never as prose in a deck. No figure is published or implied until then.
Instrumented-tenant counts, event volumes, query volumes, and the internal-versus-external split are gated. Each figure publishes with its window and base or it does not publish — a discipline this door has to hold more visibly than any sibling, because publishing measured figures is the product.
every brand the estate launches is built to run on the stack this door reads — demand designed in before any sale happens; whether and how much flows is a measured claim behind the stack#1 §A5 gate, like the usage roll itself
the door that owns the write path automatically owns the read path honestly: measurement built into the substrate needs no wiring project, and a competitor without the substrate must start by asking the buyer to staff exactly the function this door deletes
runtime choices are made once; readings are looked at every day — the read side is the pack’s retention surface, the door a decision-owner returns to after every other door has faded into plumbing
when the catalog gate on the bindings slide flips, the same readings serve humans and agents alike — and a metric an agent can read is a decision an agent can make without a meeting
The front door is analytics.do — it serves today.
If this was forwarded to you: analytics.do is the read side of the startups.studio estate's platform pack — the door where a business running on agents, functions, workflows, and metered services reads itself, sold at pro tier to the decision-owner who answers for the outcome, not to the engineer who wires the pipeline. What is live is posted with a URL checked cold: the front door, the gateway's service record, the platform and its shared docs. What is not is pending with the gate that flips it — including the six ambers this deck wears openly: the self-serve demonstration loop, the machine catalog, the machine index, the registry filing that still lags this live door, posted pricing, and the gated usage roll. Judge it by what is posted, and by how plainly it labels what is not.