Trust

PlannedChecked 16 November 2026

In short

  • Suppliers planned: none signed.
  • Controls in the code today, each with its test.
  • Controls we do not have, and what we keep.

Petrova is not live. There are no customers and no real suppliers, and no money moves. This page says what is planned, what is in the code today, and what we keep. If it sounds better than status, status is right.

Suppliers planned

No contract is signed with anyone on this list. A name here is a plan, not a partner.

SupplierWhat forToday
Anthropic APIModel callsPlanned. No direct upstream exists in the code.
Your own AWS (Bedrock)Model calls, on your accountCode tested against an emulator only.
DIEM keys (Venice-style)Cheaper model callsCode tested on fixtures only. Nothing signed.
ResellersCheaper model callsCode tested on fixtures only. Nothing signed.
x402 and MPP tool sellersPaid tools27,755 listings searchable. No real tool has been paid; the payers were rehearsed on local forks only.
Robinhood Chain (USDG), Base (USDC), Tempo (USDC.e)Money in, and paying toolsBuilt and rehearsed on local forks with the real token contracts. No real money.
Bankr, on BaseMaking the coinPlanned. Not launched.

We have not chosen the companies that will host the service, and we will list them here when we do. See supply.

Controls in the code today

Each of these runs on test fixtures. None has been checked by an outside party.

ControlHowTest
Real model spending cannot be switched onThis build refuses LIVE_SPEND=true at start-up. Real tool spending (PETROVA_LIVE_TOOLS) is off by default and refused at start-up without a fresh readiness report for that commit, the founder's approval and caps under $1 a call and $50 a daylive-spend.test.ts, "even with every condition met, this build refuses LIVE_SPEND=true"
Prompts and answers are not storedA marker string goes through every path, then every column is scannedprivacy.test.ts, "a canary prompt sent through every path appears in no text column afterwards, and no plain body hash is stored"
Keys are stored only as a hash, and each key has scopesSHA-256 plus a short prefix; tenant checks on each routefoundation.test.ts, "API keys enforce tenant isolation, scopes, revocation and pause state"
A charge is never above the holdThe excess is booked to Petrovasettlement.test.ts, "the quote is a ceiling: overspend is absorbed, never charged"
Records cannot be rewrittenSettlements and journals are append-onlysettlement.test.ts, "settlements and journals are append-only"

Controls we do not have

  • No SOC 2, ISO or other certificate. We have not started one.
  • No outside security review of the service.
  • The contracts are not audited and not deployed.
  • No rate limiter, and no status page.
  • No account deletion. See the gaps on what we keep.

What we keep

The short version:

  • Not kept: your prompts and answers from model calls.
  • Kept: your account, key hashes, every charge, receipts with token counts, and the agent and session ids your client sends.
  • Kept until you delete them: memories and repo memory you asked for.

The full table, field by field, is on what we keep.

This website

No analytics and no trackers. Fonts load from Google Fonts. The sandbox dashboard and the try-it box keep their data in your browser only.

Last checked against the code: 16 November 2026. Something wrong? The source of this page is in the repository, so a fix is one edit.