Prua

Security

Retailer traffic. Isolated tenants. No guessed fields.

Mid-market IT needs a URL, not a paragraph in a footer. These are the controls that sit under Tesco, Peppol and Xero traffic.

Talk to the Live team →

Credentials never sit in plaintext

API keys, OAuth tokens and SFTP passwords are encrypted with AES-256-GCM. Every decrypt writes an audit row. Dual-key decrypt supports rotation without downtime.

Tenant isolation is a session, not a WHERE clause

Each request binds a tenant-scoped database session. A missing tenant predicate is rejected at the session layer, not by hoping every query remembered the filter.

Mappings you can inspect — and they never guess

Live mappings are deterministic JSONata. $eval() is banned at the AST. Execution runs in an isolated worker with a hard timeout and an output cap. If a field cannot be resolved, the run stops and tells you.

Inbound replay protection

Public webhook receivers accept a signed nonce. Used nonces are stored and cleaned on a schedule so a replayed Tesco PO does not create a second order.

SSO and identity

Session cookies are HttpOnly. Bearer tokens are accepted for API and MCP clients. SSO is supported for mid-market IT. Partner portals are a separate auth surface.

What we do not claim

We do not list SOC 2, ISO 27001, or penetration-test badges we do not hold. When a report is complete, it goes here. Until then the controls above are the honest list.