Unattributed
Period record with no posted identity
- Entity_id
- empty — unattributed
- Invoice / amount
- not shown — Toll is not an invoice
- Waste class
- not published — Toll does not classify waste
Toll / engineering economics
Know what your engineering systems cost — and why.
Toll is the engineering economics product. Adopt it for utilization evidence, FOCUS-shaped ingest, and a Toll-owned economic file. It does not own delivery, infrastructure state, or governed intent. FOCUS is an input. It is not Toll.
Demonstrated: utilization sample, identity storeIllustrative: model cut
Talk to OpsDevCodeExplore capabilities
Evidence-first · independently adoptable · no invoice authority
02 / Problem
Why a bill is not a decision
A cloud bill does not explain an engineering decision.
Cost data arrives in provider vocabulary: accounts, SKUs, and tags. Engineering systems carry a different vocabulary: services, owners, resources, and changes. Existing FinOps dashboards and invoice exports keep those worlds apart, or they collapse the gap by treating a tag as ownership.
Toll exists because that gap is an engineering problem, not a reporting problem. It makes the connection legible without turning economic evidence into an invoice, a warehouse, or a savings claim.
01What cost evidence is present, and in what standardized form?
02What durable economic state can be trusted later?
03What engineering context can explain it — and what remains a measured gap?
03 / Record
Missing and conflicting evidence
An economic record can exist without a settled owner.
These cards are illustrative lab compositions. The demonstrated product behavior is the gap: empty identity stays unattributed; a conflicting tag and posted identity stay ambiguous. Invoice totals are deliberately absent. Spend share is not computed here.
Ambiguous
Posted identity conflicts with source tag
- Tag
- team=payments
- Posted identity
- entity_id=svc-platform
- Invoice / amount
- not shown — Toll is not an invoice
Identity stored
Posted identity sits beside the record
- Entity_id
- stored as posted — no invented owner
- Spend share
- not computed here — hosted spend attribution is in development
- Savings
- not shown — Toll does not publish savings figures
04 / Model
Engineering economics
Standardize the evidence before drawing a conclusion.
Toll is an engineering economics layer, not a dashboard. The model is ingest a shaped record, persist it as Toll-owned state, then connect posted engineering context. Attribution is a model of that evidence. It is not a forced owner.
01 / ingest
Standardize economics
Receive cost evidence in a defined FOCUS-shaped form rather than treating an invoice as an engineering model.
02 / persist
Keep durable state
Hold the economic record and source evidence in Toll persistence so later reasoning has a stable basis.
03 / connect
Bring engineering context
Relate resource and engineering identity without inventing ownership when evidence is incomplete.
05 / FOCUS
Input, not the product
FOCUS is an input, not Toll’s boundary.
The FinOps Open Cost and Usage Specification gives the economics record a portable shape. Toll owns retaining that evidence and making confidence visible. A FOCUS pipeline is how records enter. It is not what Toll is. The ingest → persist → connect cut is stated once in the model above.
- Cloud-bill records enter in a standardized economic form.
- Toll persists the record with source and period evidence.
- Engineering identity is supplied as context, never guessed from a missing tag.
06 / Ownership
Domain authority
Toll owns the economic record. It does not own the rest of the system.
Repave, Overpass, Dispatch, and Toll are distinct products. Toll can be adopted for economics without taking the rest of the family. They may exchange evidence later; they are not one store, one policy engine, or one required pipeline.
Toll owns
Engineering economics
- Standardized economic input and FOCUS ingest
- Durable economic state and source evidence
- Posted engineering identity stored beside that record
- The attribution question: what evidence supports a binding
Toll does not own
Deliberate non-ownership
- Invoices, billing-write keys, or payment authority
- A cost warehouse or FinOps dashboard as the product
- Repository lifecycle and delivery evidence — Repave
- Infrastructure state and relationships — Overpass
- Governed intent, proposal, or authorization — Dispatch
- Policy Runtime, Relay, or OPA — those are not Toll features
07 / Capabilities
What Toll can state
Name what it does, what it takes, and what it leaves.
These are Toll capabilities at the confidence they have earned. None are Faster, Smarter, or AI-powered placeholders. Spend attribution and waste findings remain in development and are not listed as current capabilities.
available
Utilization evidence
Does. Evaluate a bounded set of caller-supplied utilization observations from an identified measurement source.
Input / state. A posted source document plus period, tenant, and resource observations. Toll does not scrape a live cluster to invent the sample.
Outcome. A deterministic utilization digest and per-resource sample evidence. No waste class, rightsizing, or savings claim.
production validation
FOCUS ingest
Does. Accept cloud-bill records in a FOCUS-shaped form so provider vocabulary becomes a portable economic input.
Input / state. A FOCUS export (period, resource, source). The FinOps Open Cost and Usage Specification is the shape of the input, not Toll itself.
Outcome. Normalized economic rows Toll can persist. Ingest is data acquisition in production validation, not a public product API.
production validation
Durable economic state
Does. Hold the economic record with source and period evidence in Toll-owned persistence.
Input / state. Ingested FOCUS rows plus the source file identity Toll already accepted. Independent of Repave tables and credentials.
Outcome. A durable Toll economic record later reasoning can cite. Not an invoice ledger and not a warehouse product.
available
Engineering identity
Does. Store posted engineering identity beside economic records so attribution has evidence instead of a guessed tag.
Input / state. An attribution-identity snapshot (entity, resource, tenant) posted to Toll. Empty entity remains unattributed.
Outcome. Identity and source evidence sit next to the economic record. Missing or conflicting evidence stays a visible gap.
08 / Scenario
A period that moved
A service owner can ask why a period cost more — without inventing an owner.
Grounded in product truth: Toll can hold a FOCUS-period record and posted identity. It does not compute spend share on this host, and it will not fill a missing tag.
Demonstrated
“What economic evidence do we have for this resource in this period?”
A FOCUS export for the period enters Toll. Toll persists the record with source and period evidence. If engineering identity was posted, it sits beside the record. If it was not, the record stays unattributed. The answer is the evidence, not a guessed team name.
Illustrative direction
“How much of that movement should we attribute to last week’s change?”
Change-linked economic evidence is planned. Hosted spend attribution is in development. This page does not present either as a Toll-hosted action or as a savings figure.
09 / Attribution
Evidence, not a forced answer
Attribution is a model of evidence, not a forced answer.
When cost records and engineering identity meet, Toll preserves what supports the connection. A tag can be useful evidence; it is not ownership by itself. Hosted spend attribution remains in development and is not computed on this page.
—Attributed — supplied identity and economic evidence agree.
—Unattributed — the record has no supported engineering binding.
—Ambiguous — evidence conflicts or is insufficient; Toll keeps uncertainty visible.
10 / Policy
Policy direction
Attributed spend is decision context, not a live brake.
Policy can treat Toll facts as economic context: who the spend belongs to, whether a threshold is in view, and what evidence should travel with a lifecycle decision. Budgets and approvals near a cost boundary are the intended constraint model. Toll does not enforce spend in real time, does not invoice, and does not claim autonomous remediation.
01 / context
Attributed spend
When identity and FOCUS evidence agree, that binding can travel into a DecisionContext. Incomplete attribution stays visible.
02 / constraint
Budgets and thresholds
A governed constraint can require an approval or extra evidence. That is an obligation, not a silent block invented by this page.
03 / evidence
Attached to lifecycle
Economic evidence can sit beside a Repave decision record. Toll still owns the economics store; it does not become the policy engine.
11 / Persistence
Independence
Toll keeps its own economic file.
Durable state lives in Toll-owned sqlite. Engineering identity arrives as a posted contract. Toll does not query the Repave database, import a sibling runtime, or treat a shared warehouse as its system of record.
That independence is the product boundary: economics can sit beside delivery and infrastructure context without becoming them.
12 / Maturity
Capability maturity
State each capability at the confidence it has earned.
These statements come from Toll’s product-owned maturity source. Available is distinct from production validation, in development, and planned. Work that is not hosted on this Toll surface is not labeled available here.
available
Utilization evidence
A bounded utilization sample runs in Toll from an identified measurement source. It does not collect live metrics or classify waste.
production validation
FOCUS ingest
Implemented in Toll as standardized economic input; production delivery is being validated conservatively. FOCUS is not the product.
production validation
Durable economic state
FOCUS persistence is implemented in Toll-owned sqlite; production operation carries the same conservative status.
available
Engineering identity
Posted engineering identity and source evidence can be stored beside economic records. Toll does not invent an owner from a missing tag.
in development
Spend attribution
Hosted spend attribution is in development on Toll. This host does not compute spend share or publish a binding.
in development
Waste and savings evidence
Evidence-backed findings are in development. Toll does not publish savings percentages.
planned
Change-linked economic evidence
A future connection between engineering change and economic evidence is planned. It is not available on this host.
13 / Family
OpsDevCode ecosystem
Independent products. Connected engineering context.
Each product owns a different governed reading of an engineering organization. They are related surfaces, not a bundled runtime, a required sequence, or an evaluation funnel. Convergence is independent and is not a fifth product here.
Repave
Governed software delivery.
repave.opsdevco.deOverpass
Infrastructure state and relationships.
overpass.opsdevco.de
Toll
Engineering economics.
Dispatch
Governed intent and action.
dispatch.opsdevco.de14 / Direction
Product direction
Where Toll is going — separately from what it can state today.
From a cloud bill to economic evidence, Toll will extend the connection between durable economics and engineering context without becoming an invoice system or a savings engine.
Talk / evaluate
Talk about Toll as an economics product — not a platform signup.
This host is a product identity page. It is not a deploy console. Toll can be evaluated on its own economic record without adopting delivery or infrastructure products.