TensorCost TensorCost
Security

Read-only to start, and nothing in your request path until you say so.

The short version for a reviewer who has ten minutes: we hold no cloud keys, the audit log is hash-chained so you can re-derive it yourself, row-level security is FORCE'd so it applies to our own services too, and we are not SOC 2 certified. That last one is a real gap and it is stated here rather than buried.

How access works

Four things a security reviewer usually asks in the first call.

We store no cloud keys

Cross-account access is a short-lived AssumeRole with a per-tenant external ID. There is no long-lived credential of yours sitting in our database to leak, rotate or subpoena. Azure infra-cost onboarding does not take a client secret either.

An audit log you can re-derive

Every privileged action is written to a hash-chained, tamper-evident log. A reviewer can recompute the chain with sha256sum and check it themselves rather than taking our word for it. Note the scope precisely: the chain is on the audit log, not on the savings ledger, and it is a report — never a billing input.

Row-level security, FORCE'd

Postgres RLS with a tenant-isolation policy on every tenant-scoped table, and FORCE'd so it applies even to the table owner — our own services get no exemption. New tenant-scoped tables ship the policy in the same migration that creates them, not a later one.

Nothing in the request path on day one

A replay needs billing-API access and an IAM role. No production access, no code changes, nothing between your application and a model provider. The proxy and live routing are opt-in later, default-off, and cannot arm until a policy has earned shadow proof on your own traffic.

Compliance

Where we actually stand

A public trust portal is live. CAIQ and SIG-Lite are available under NDA.

SOC 2 is on the roadmap. No auditor is engaged and there is no date to give you. If a certificate is a hard gate for your procurement this quarter, we are not the right vendor yet and we would rather you heard it here than in week six of a security review.

No penetration test report exists yet either. Both of these are consequences of being early rather than of a decision that they do not matter, and both are things a paying customer can reasonably make a condition.

See what the last 30 days would have saved.

Connect your first inference source. First snapshot in 48 hours. Written findings report inside two weeks. No card required. No commitment.