Built for banks.
Designed to their standard.
BookRunner is currently operating in a private pilot with select investment banks. Full security documentation, penetration test reports, and compliance questionnaire responses are available to prospective partners on request.
Private pilot. BookRunner is not open to the public. Access is by invitation only, scoped to named institutions and their authorised personnel. If you are reviewing this page as part of a vendor assessment, contact us directly for the full security pack.
Encryption & transport
All data in transit is encrypted via TLS 1.3. All data at rest is encrypted with AES-256. Encryption is applied at the infrastructure layer — not the application layer — meaning it cannot be bypassed by application code.
Keys are managed via the hosting provider's key management service with automatic rotation. No key material is stored in application configuration or source code.
Tenant isolation
Each bank is a fully isolated tenant. Data isolation is enforced at the database layer via row-level security — not the application layer. A misconfigured API route cannot expose one tenant's data to another, because the database itself enforces the boundary.
Tenant investor databases are private by default. No data is shared between tenants under any circumstances. Data sovereignty is guaranteed by design, not by policy.
Access control
Token-based authentication throughout. No passwords. Every session is scoped to a named user within a named tenant. Session tokens expire and rotate automatically.
Conversation go-live requires dual-control authorization — a banker initiates, a second authorised user confirms. No conversation reaches an investor without an explicit human authorization event on record.
Audit & compliance
Every inbound message, every AI response, every banker intervention, every go-live authorization is logged immutably with actor, timestamp, and system prompt version. Logs are append-only and cannot be modified after the fact.
Conversations are scanned for compliance triggers in real time. Escalations are routed to the supervising banker immediately. Nothing is sent to an investor that has not passed through the compliance filter configured for that tenant's jurisdiction.
Infrastructure & hosting
BookRunner is hosted on infrastructure with in-region data residency options. No investor data is processed outside the configured region without explicit tenant consent. Infrastructure providers are SOC 2 Type II certified.
The platform is built API-first on documented, versioned interfaces. No proprietary lock-in. Tenants can request a full data export at any time in standard formats.
Security documentation
BookRunner is currently in a private pilot. Full security documentation — including penetration test reports, architecture diagrams, vendor assessment questionnaire responses, and data processing agreements — is available to prospective partners under NDA.
To request the full security pack:
legal@bookrunner.app