Security and trust

Built for finance. Controlled by finance.

Rever reads your systems and never writes to them, hands approved journal entries back as a file your team loads, preserves evidence before it transforms anything, and never trains on customer data. Ask for the security pack during your demo.

  • Annually audited

    SOC 2 Type II

  • Certified

    ISO/IEC 27001:2022

  • At rest and in transit

    Encrypted

  • Self-host or private cloud available

    Your perimeter

01Commitments

What we commit to, in every deployment

01

Rever never writes to your systems

It reads your ERP, bank and payment records through their APIs, works on its own copy and hands approved journal entries back as an import file your team loads. A payment hold is recorded in Rever and your team is told on Slack and email.

02

No training on customer data

Your records are never used to train models. What the agents learn about your business stays within your tenancy.

03

Evidence preserved before transformation

Original records are kept as received. Calculations and source references stay connected to every finding and workpaper.

04

Human action captured as governed decisions

Every approval, question and send-back is a recorded decision in the Inbox, with what happened next.

05

Agent management in your hands

Materiality, approval paths and agent responsibilities are set by your team, entity by entity.

06

No human-readable PII in model context

Personal data in connected records is handled without human-readable exposure in model prompts and is not stored in model context.

07

Tenant isolation and guardrails

Customer partitioning at every layer, with instruction-based and model-based guardrails around every agent.

08

Model flexibility

Rever is not tied to a single model provider. Routing follows your hosting and data-residency requirements.

02Controls

Agents prepare. Your team approves.

Rever can reconcile, verify, investigate and draft. Nothing writes to your systems, and nothing leaves the company until a person with the authority approves it.

  • Read-only API connections; no write access requested
  • Approved journal entries leave as an import file your team loads; nothing posts from Rever
  • Approval thresholds and dual approval for material amounts, set by you
  • Suspicious vendor-bank changes and payment patterns flagged by Sentinel
  • Independent procedure testing by Auditor; system health by Steward
  • SSO, SAML and SCIM available for enterprise access control
Deployment

Where Rever runs

Self-host

Inside your own environment

The full platform in your perimeter, with the same read-only connection rules and controls.

Private cloud

Dedicated and region-pinned

Single-tenant deployment in the agreed region, with model routing and processing locations specified in your Order Form.

Managed cloud

Rever's own cloud

Tenant-isolated and region-pinned, with Rever operating the platform.

Self-host · Private cloud · Managed cloud · Same read-only rules in every option

03FAQ

Questions your security team will ask

The SOC 2 Type II report, the ISO/IEC 27001:2022 certificate, the architecture and the data-processing terms are available on request.

Does Rever post entries into our ERP?

No. Rever never writes to your systems. When your team approves a journal entry in the Inbox, Rever hands it back as an import file your team loads, a .qbo file for QuickBooks today. A payment hold is recorded in Rever and your team is told on Slack and email; other corrections are prepared with their evidence for your team to action. Your ERP stays the system of record.

Will Rever change our source data?

No. Rever reads your ERP, bank and payment records through their APIs, keeps a working copy inside Rever (the shadow ledger) and does every check, reconciliation and calculation there, during the zero-day scan and after it. Your ERP stays the system of record.

How does Rever connect to our systems?

Through read-only connections to your ERP, banks and documents, or to a common database you already maintain. Each connection is a direct, deterministic integration rather than an MCP server or an agent holding credentials, so the agents can only read what the connection provides and your source data stays unchanged. The connections read; they never write. Approved journal entries come back to you as an import file your team loads.

Where is Rever hosted?

Rever supports self-hosting in your own environment and private cloud deployment, alongside our managed cloud. Connections and data handling follow the same read-only rules in every option.

Is our financial data used to train AI models?

No. Customer data is not used for training. What the agents learn about your business, from your policies, contracts and confirmed answers, stays within your tenancy.

Bring your security team

We will walk through the report, the certificate, the architecture and the controls, on a call.