RRP Central

Trust is part of the product

Evidence deserves a system you can explain.

RRP Central is designed around tenant boundaries, original documents, and a history that ordinary edits cannot rewrite.

01

Preserve the original

Server uploads store original bytes in configured R2 storage, with upload metadata and a server-generated SHA-256 hash. A local save is not confirmation that an original reached the server; check upload and export results.

02

Keep history visible

Recorded mutations append audit events, and exports include saved record history and ruleset information. A hash or audit entry does not independently verify that the underlying statement is true or that a signer is who they claim to be.

03

Keep the trail append-only

Database triggers reject ordinary updates and deletes in the audit table. Mutation requests use idempotency keys to handle retries. These controls are not an independent immutable archive and do not prevent a privileged database administrator from changing the schema.

04

Be honest about the boundary

RRP Central keeps your records and shows how they were made. It does not replace your own legal review or the agency that runs your program.

Implemented controls and limits

Controls in the current code. Operations still matter.

Tenant isolationRole-based accessHashed passwords and link tokensEncrypted in transitRetention dates and hold preferenceAudit exportsRate-limited sign-inServer-side file fingerprints

See the workflow yourself

Build one complete record.

Start free trial