Four principles
- Neutral. A-REX Platform is one implementation of an open standard. No company, and no one at A-REX, sees or changes another company's records without that company's consent, and a company can leave with all of its history.
- Evidence before claims. Every fact says who stated it and who stands behind it. Nothing is presented as stronger than its evidence, and the platform never states that a lot or a company complies.
- Business words, no technical burden. People approve with a passkey on their phone or computer, and nobody has to handle anything technical to keep their records.
- Value inside the law. Lots are goods, not financial products. Anything that touches money goes through licensed partners.
People approve, with a second factor
Every change to a company's records starts as a proposal that reads as a sentence. A member with the right to approve it confirms it with two-factor authentication, and the weightiest changes ask for a fresh second factor. The person who prepared a proposal cannot approve it, except a sole approver in a company that allows it. Proposals that wait 72 hours expire.
The assistant, automations, integrations and outside agents can prepare proposals. None of them can approve, publish, send or sign.
Who holds the keys
A company's ledger is administered by its own administration account, which needs several keys to act. The keys are passkeys: digital keys on a phone, a computer or a security key, unlocked with a fingerprint, a face or a PIN.
| Managed custody | Keys on your devices | |
|---|---|---|
| Keys | owner passkey, recovery passkey, an A-REX operations key | owner passkey, recovery passkey |
| Approvals needed | 2 of 3 | 1 of 2 |
| Can A-REX act alone? | never | never (it holds no key) |
| Can the company act alone? | yes, with both passkeys | yes |
Managed custody is offered for traceability records only, and only where the company's country allows it. It is off in the European Union, Argentina, Chile, Bolivia and the State of New York. A company can hand the accounts A-REX keeps for its partners over to its own keys at any time.
What the ledger never holds
The ledger holds no personal data and no documents. Names, tax numbers, contacts, addresses and plot coordinates stay encrypted in the company's directory, with keys kept in a key management service. A certificate's file stays with the company; only its fingerprint is recorded. The reference of a farm or plot is never made from its location.
Each lot has a public record without personal data, so a buyer can check it without an account.
Personal data
A-REX Platform is built for Brazil's LGPD and the European GDPR. A company can erase a party from its directory: the personal fields are removed and the history stays, without anyone's name in it. Plot coordinates are shared with a customer only for EUDR due diligence, after a statement confirmed with a second factor, and the supplier sees every time they are read. Support never sees an assistant conversation unless the person chooses to include it in a problem report.
Companies are kept apart
Every request runs inside one company, under the database's row-level security: another company's record answers as if it did not exist. Credentials belong to one company and one environment, production or sandbox. Each has its own rate limit, and every change, report, download and outside read is recorded with the credential behind it.
Agents in their place
- Agents read and, when allowed, prepare proposals. They never approve.
- Text written by people or by other companies is data, never instructions: lot notes, party names, certificate fields, notices and messages are quoted, not followed.
- The MCP server holds no database access and no keys. Every tool call is an API call with the caller's own credential.
- Every run is capped in steps, time, size and number of proposals.
- Outside agents see only what a company granted, and every read they make is logged.
Anyone can check, without A-REX
The records follow the open A-REX standard. A lot's information can be recomputed from its public record and compared with the fingerprint on the ledger. A sealed report can be checked on the verification page, or with public tools, without an account and without trusting A-REX.
Where we are
A-REX Platform is in alpha. Companies use it in sandboxes and on test ledgers while the production service is prepared. Before production we still have to:
- have the ledger's reference implementation independently audited;
- run a penetration test, and open a bug bounty after the first pilot;
- finish the operational runbooks for key creation and rotation.
We say on this page when each one is done.