Guides/Deployment

The private environment

The managed dedicated AWS account each firm runs in: single-tenant isolation, keys the firm holds, in-account inference, and the Telemetry Ledger that shows every byte Proxara receives.

Updated July 2026

Every firm running Proxara gets its own environment. Not a tenant inside a shared system, but a dedicated cloud account of its own, with its own network, its own keys, and its own record. Proxara provisions it and runs it, so the firm's IT team sets up nothing and maintains nothing.

This page covers the managed model, which is the default. A firm that would rather run the software in its own cloud can, and that path is On-premise and private deployment.

The firm's AWS accountKMS · firm-held

VPC · 3 AZEKSRDS Multi-AZS3 Object LockRedisBedrock in-region

Prompt content stays inside this boundary.

Ops role · revocable

ProxaraOperates · never owns keys

One account per firm. The data, the keys, and the record stay inside it.

What is inside

Piece	What it means
A dedicated AWS account	Single-tenant. No other customer's data shares the network, the database, or the keys.
Keys the firm holds	AWS KMS keys created in the firm's own account. Proxara has use-only rights and no right to delete or disable them. The firm can revoke access at any time.
The interception certificate	A per-tenant certificate authority, scoped by name constraints that exclude sign-in, banking, healthcare, and government in the certificate itself.
The audit vault	The signed, hash-chained record, archived to object storage in compliance-lock mode, which even Proxara's own role cannot delete.
In-account inference	Classification runs on Amazon Bedrock inside the firm's account. Prompts are not sent out of the account to be classified.

The firm gets read-only access to all of it. Proxara holds the operational access needed to deploy and maintain the environment, gated behind multi-factor authentication, with every action logged. At the end of a contract the firm can take ownership of the whole account, or Proxara deletes it and certifies the deletion.

What leaves the environment

To keep the environment healthy, a thin stream of operational telemetry crosses back to Proxara: whether the services are up, how many devices are covered, latency and error counts. It is content-free by construction. Before any frame leaves, it passes a schema check and a content tripwire, so only template ids, category codes, and numbers can cross. Free text cannot. No prompt, no file, no name, no personal data.

The firm does not have to take that on faith. Every frame is written to a Telemetry Ledger inside the console before it is sent, with its hash and its full payload. The firm can open any row and read the exact bytes that crossed. Nothing reaches Proxara that is not on that page.

Environment telemetry

Telemetry Ledger

Every byte Proxara receives from this environment. Each frame is written here at send time, before it leaves, with its hash, its full payload, and whether Proxara acknowledged it. Nothing crosses that is not on this page.

1,204 frames, newest first · 1,203 acknowledged

L0just now3f2a9c1b4d7e…Recorded

L14 min agoa17c4e90f2b8…Acked

L222 min ago9d4f13c7ea56…Acked

L023 min ago5e8b0a2f6c14…Acked

recorded 2026-07-04 14:22:05 UTCsent 2026-07-04 14:22:06 UTCframe 48213sha256 3f2a9c1b4d7e8a05c6f1b2d3e4a5f6079b8c1d2e3f4a5b6c7d8e9f0a1b2c3d4e5

{
  "contract_version": 1,
  "enclave_id": "acme-prod",
  "ts": "2026-07-04T14:22:05Z",
  "manifest_id": "px.2026.07.stable",
  "ring": "ring1",
  "services": [
    { "name": "api", "status": "up", "restarts": 0 },
    { "name": "classifier", "status": "up", "restarts": 0 },
    { "name": "shipper", "status": "up", "restarts": 1 }
  ],
  "steward": { "alive": true, "budget_pct": 82.4 },
  "agent_versions": { "1.11.6": 213, "1.11.5": 4 },
  "slo": { "protection_pct": 99.97, "api_avail_pct": 100.0, "slo_basis": "health_columns_only" },
  "cost": { "mtd_usd": 214.6, "bedrock_mtd_usd": 38.2 },
  "resources": { "cpu_pct": 22.5, "db_storage_pct": 41.0, "quota_flags": [] }
}

Open any row, read the bytes

Every frame that leaves is written down and readable, before it goes.

Why it is built this way

Isolation is the product, not a tier. A single dedicated account means a mistake in one firm's environment cannot reach another's, the firm's own keys gate the data, and the record sits somewhere neither the firm's operators nor Proxara can quietly alter. It is also what lets a pilot become production without moving anything. The pilot runs in the same kind of environment it would run in for real, so converting is a change of state, not a migration.

The full control list is in the Security Overview, and the processing terms are in the Data Processing Addendum.