Six products. One login. One ledger.
Each one stands alone and each one is better with the others, because they share the same identity, the same inventory of your estate and the same record of what everything cost. Start with the one that hurts most.
Conductor
The AI layer, and the cost of it.
An OpenAI-compatible endpoint your apps, IDEs and agents point at by changing one setting. Trivial input is answered before a model is involved. What your estate actually looks like goes into the model's context as reference data. A tenant that registers its own models is served from those and nothing else, and every request lands on the ledger whether or not a model was called.
Routing by tier
The smallest model that finishes each kind of work, a larger one for the work that needs it, and a fallback used rarely rather than constantly.
Memory from the estate
Facts read from your cloud every hour, attached as reference and labelled as data, never as instruction.
Approval gate
Anything that changes production or moves money proposes first and waits for a named person. That tier cannot be set to approve itself.
The ledger
What each request cost, which model answered, and what was avoided, beside the provider's own invoice.
Passage
Remote access with single sign-on.
One identity for every cloud console, server, database and internal tool you run, on whichever clouds you run them. People connect by clicking, not by passing keys around. A certificate is issued for the session and the session is recorded, so “who ran that” has an answer that does not depend on anyone's memory.
Single sign-on everywhere
Your identity provider in front of SSH, databases, Kubernetes, cloud consoles and the AI tools. Joiners get what their role needs; leavers lose it the same hour.
Access by role, with a time limit
Standing access is the exception. Elevated access is requested, approved and expires on its own.
Session recording
Terminal and database sessions recorded and searchable, which is the evidence an assessor asks for and the thing that ends arguments.
Nothing listening on your side
Outbound connections only, mutual TLS between components, secrets held in a vault. No inbound firewall rule, no allowlist to keep current.
Tally
The AI and cloud cost calculator. The version below runs on published list prices so you can get a feel for the shape of your bill. The full product reads your own traffic and your own account, and shows the provider's figure beside ours.
Illustrative. Assumes a quarter of non-trivial requests are short answers a small model handles at equal quality, and 15% of traffic is development work. Your review replaces every assumption here with a measurement from your own logs, and the number can go down as well as up.
Attest
Compliance, as a running service.
Most companies pass an assessment the way students pass an exam: a hard fortnight, then forgetting. Attest keeps the evidence current all year, because the controls are read from the estate itself rather than from a spreadsheet somebody maintains. When the assessor arrives, the folder already exists.
PCI DSS and ISO/IEC 27001
Gap assessment, remediation plan, policies written for your estate rather than downloaded, and a named engineer in the room with the assessor.
Evidence collected continuously
Access reviews, key ages, open ports, encryption at rest, patch state, each item citing the requirement it satisfies, refreshed every hour from the account.
Findings that name the fix
Not “forty issues”, but each one with the evidence it rests on, the requirement it sits under, and the change that closes it.
Honest about coverage
Every report lists what we could not read and the permission that would include it, so a gap is somebody's next ten minutes rather than a false all-clear.
Renew
Certificates and keys, on a schedule.
Every estate has a certificate nobody remembers issuing and a key nobody has rotated since the person who made it left. Renew finds them, tells you when they expire, and rotates them on a schedule you set, with the change proposed and shown before it is made.
Inventory, by days to expiry
TLS certificates, mutual-TLS client certificates, signing keys, access keys and API tokens, across clouds and load balancers, ordered by what expires first.
Rotation before expiry
Renewal and rollout as a proposed change with a diff, approved by a person, with a rollback that is ready before anything is applied.
The awkward ones too
Partner and scheme keys that live on SFTP and in signing bureaus, where rotation is a procedure rather than a click. Documented once, then followed every time.
Watch
Quota and spend alerts.
Cloud bills and model quotas both fail quietly. Watch reads them every hour, projects where the month is heading, and tells a named person at 80% of a quota or a budget, before a report fails or an invoice surprises anyone.
Across providers
Cloud spend and model-provider quotas in one place, with the provider's own stated figure leading and our attribution beside it.
Projection, not just a total
What this month is tracking to against last month, stated as a projection with the reasons it might be wrong written next to it.
Alerts that reach someone
Email and chat, to the person who can act, with the number and the thing to do about it.
Not sure where to start?
The review tells you which of these would pay for itself first, from your own numbers.