Running release
ReadingThe build serving production right now, signed.
Trust Center
ALEETH exists to put autonomous AI under institutional control. It would be a contradiction to run our own platform any other way. The live record below is read from production as the page loads.
AT REST
AES-256
database, including secrets
PROVENANCE
Ed25519
append-only, anchored
ISOLATION
Per-tenant
customer tokens, API-authorized
AUDIT
Append-only
database-trigger enforced
The Live Record
The build ICA is running, the transparency log ICA seals receipts into, and authenticated-route coverage for ALEETH's own platform routes, as ICA publishes it. Your browser reads each one from ICA directly. The build and transparency-log figures link to their raw records.
Running release
ReadingThe build serving production right now, signed.
Transparency log
ReadingReceipts are sealed into Merkle trees. On a schedule, ICA time-stamps its latest anchored root with an RFC 3161 service. The inclusion proof for a receipt you hold can be checked offline.
Authenticated-route coverage
ReadingThe share of ALEETH's own platform API routes with side effects that require authentication or another recognized control (tool gateway, shared secret or credential), from a static scan of ICA's code checked in CI, as ICA publishes it. It does not measure policy enforcement or approval decisions on customer agent actions.
Reading the live record.
ALEETH Brain
ALEETH runs its own Brain on ICA. The charter, the kill switch, and the decision counts are read from ICA in this browser. This page does not say the Brain decides on its own unless that read says so.
Sealed charter
ReadingThe authority boundary the Brain works inside, sealed as a signed record.
Kill switch
ReadingA person holds the switch. A halted Brain decides nothing until that person resumes it.
Decisions
ReadingCounts only. No decision content, and no decision receipt, leaves ICA.
Reading the Brain's record.
Platform Controls
01.
ICA writes control events to an Ed25519-signed, hash-chained ledger. Database triggers refuse updates and deletes on the ledger tables. On a recurring cadence the ledger's Merkle root is anchored outside ICA through OpenTimestamps, so an edit or deletion made after anchoring contradicts the anchored record.
02.
Connections to aleeth.com and to ICA use TLS, and plain HTTP is redirected to HTTPS. ICA reaches its database over HTTPS, and the database is encrypted at rest with AES-256. Anthropic and OpenAI Admin API keys that a customer connects through the provider-connection API, and single sign-on client secrets, are encrypted with AES-256-GCM before they are stored, and the write is refused if the encryption key is missing. That API returns only a masked fingerprint of a stored key, never the key.
03.
Every request is authorized against the tenant it targets in the API layer. A customer token scoped to one tenant receives a 403 when it reaches for another tenant's data, and ICA's own test harness checks this. ALEETH operator accounts can act across tenants. Row-level security policies at the database provide defense in depth for direct client access.
04.
Customer tokens are scoped to a single tenant by signed claim.
05.
State transitions record the actor, the before and after state, source address, and timestamp to an append-only audit log enforced by a database trigger, which the application cannot rewrite.
06.
An internal sentinel probes platform health and integrity on a fixed cadence and writes any incident to an append-only log, with alerting. We hold our own platform to the same continuous-evidence standard we require of the systems we govern.
Agent Governance
Securing the platform is the floor. These govern the agents themselves: their purpose traces to the business, and their fairness is measured.
Strategy & Vision
Every governed agent traces to a business objective, a named owner, and a risk tier, rolled up across the estate with an honest coverage posture. Uncharted agents are counted, never shown as passing.
Ethical Principles
Bias measured on the EEOC four-fifths rule and the NYC Local Law 144 metrics. Advisory by design, it flags for human review and never silently moves an agent's standing.
Data · Residency · Subprocessors
Primary data residency is the United States. Subprocessors are listed below by category. We do not sell customer data, and ICA does not train language models on customer evidence. ICA's detection tuning model learns from past findings, including their tenant and actor, and whether each was confirmed or dismissed; it proposes rule changes and never applies them.
Responsible Disclosure
We welcome good-faith security research. If you report a vulnerability in good faith and within the scope below, we will not pursue legal action, we will acknowledge your report, and we will keep you updated through remediation.
DO report promptly, give us reasonable time to remediate before public disclosure, and act in good faith.
DO NOT access, modify, or exfiltrate another customer's data, degrade or interrupt service, or run automated scanning that disrupts availability.
SCOPE aleeth.com and its public verification surfaces (the public credential verifier and trust pages). Operator and customer consoles, and social engineering of staff or customers, are out of scope.
In progress
What is not held
Next · Provenance
Every statement on this page about signed, append-only, anchored records is verifiable. The live receipt chain and the public-ledger anchor are open to any browser, with no account and no permission required.
See the live proof →