App-layer tenant isolation
Every record is double-scoped — checked against your organization on the way in and on the way out. One org can never read, query, or export another org’s data.
Every agent and human action is signed and hash-chained, double-scoped to your org, and kept for seven years. Audit-grade by construction — continuous, not point-in-time.
An AI-run company generates consequential actions every second — agents provisioning, sharing, spending, and deciding alongside your people. Point-in-time attestations can’t keep up with that.
Plantel Compliance is built so the evidence is a byproduct of how the platform runs. Isolation is enforced on every read and write. Integrity is enforced by a hash chain. Retention is enforced by an append-only store. You don’t have to trust the dashboard — you can verify the record.
Every record is double-scoped — checked against your organization on the way in and on the way out. One org can never read, query, or export another org’s data.
Each entry carries a SHA-256 hash of itself and of the entry before it. Change or delete one row and every later hash breaks — tampering is detectable, not silent.
The audit log has no UPDATE and no DELETE path. Entries are written by internal services only, never edited from an admin console. The record is the record.
Audit history is retained for seven years by default, with per-org extension for regulated industries. Nothing is purged while a legal hold is in place.
Isolation is enforced at the application layer and double-scoped: every query is bound to your organization when it’s requested and re-checked against your organization before any row is returned. Audit entries, evidence, and reports are all scoped the same way.
The result is a hard tenant boundary — one org cannot see, search, or export another org’s log. It’s a property we test for, not a setting you toggle.
The audit log is the spine of the platform — and it’s tamper-evident by design.
Each entry stores a hash of its own content plus the hash of the entry before it. Modify or remove any single entry and every subsequent hash no longer matches — so the break is detectable.
There is no UPDATE and no DELETE path on the log. Entries are written by internal services, never edited through an admin API. What happened stays exactly as it happened.
Every entry records who acted — human, agent, system, or admin — alongside the action, resource, time, and context. Agent and human activity sit in the same chain.
The audit log covers the consequential surface of an AI-run company — across people, agents, and infrastructure.
Because the audit log captures activity as it happens, evidence isn’t something you scramble to assemble before an audit — it’s already there. Plantel Compliance turns that continuous record into the policy, evidence, and reporting your auditors expect.
See the platformThe platform is designed to produce the evidence behind six framework programs. These are the controls Plantel Compliance is built to support and evidence — not certifications it claims on your behalf.
Plantel Compliance is a single add-on to Plantel Business — $99.95/mo for unlimited frameworks. No per-framework upsell, no point-in-time surprise bill.
See pricingContinuous, audit-grade compliance for an AI-run company.