Managed Cloud
A Bexara-hosted environment, subject to the deployment architecture and availability confirmed for your agency.
Security & deployment
Secure, flexible deployment for insurance AI.
The right deployment model depends on your security requirements, infrastructure, data-handling policies and the configurations Bexara supports for your environment.
Deployment models
Three ways to run Bexara.
Private Cloud / Customer Tenant
Deployment in a cloud environment your organization controls, where supported.
On-Premises
Deployment within your organization's own infrastructure, where supported.
Architecture
See where processing and data reside.
Select a deployment model. A sample document travels from a carrier website through orchestration, AI processing and validation to the AMS — and the labeled boundary shows what stays inside your control.
Agency users
Carrier websites
Agency management system
Identity & access
Validation & approval
Audit logs
Integration endpoints
Bexara orchestration
AI processing
Data storage
Bexara AI operations
External model provider
Shared responsibilities
Security controls
Controls that apply to every workflow.
Described where implemented for your deployment. We do not claim certifications or controls that have not been verified.
Access control & identity
Role-based permissions and least-privilege access, with identity-provider integration where implemented.
Tenant isolation
Customer-level separation of data, workflows, credentials and integration access.
Encryption
Encryption in transit and at rest, with key management appropriate to each deployment model.
Secure credential management
Carrier website and AMS credentials kept in secrets management — never in prompts, logs or analytics.
Controlled execution
Each capability can only use the tools, data and actions its workflow permits. Enforced in code.
Audit trails
Records of retrieval, extraction, checks, approvals, corrections and updates.
Human approval gates
Configured actions wait for a reviewer before they run. Unresolved items cannot continue.
Data retention & deletion
Retention periods and deletion handling defined per deployment and agreement.
Model & external-service governance
Which models and external services are used, and what data they receive, is disclosed per deployment.
Controls in action
Follow a document through the control path.
Switch to “Unauthorized action” to see an instruction hidden inside a document blocked by execution policy.
Endorsement_0518.pdfTenant: Agency A · arriving via carrier portal
Simulation- Customer boundary—Waiting
- Identity & permissions—Waiting
- Processing environment—Waiting
- Scoped agent—Waiting
- Validation controls—Waiting
- Execution policy—Waiting
- Audit trail—Waiting
Agent scope for this workflow
Data
- This document
- Account NW-20418 policies
Tools
- Extract fields
- Attach to AMS account
Not permitted
- Other tenants' data
- Send external email
- Edit policy records without approval
Audit trail
- Events appear as the document moves through each control.
Ready
Choose the deployment that fits your requirements.
Tell us about your infrastructure and data-handling policies, and we'll walk through the options that apply to your agency.
Each demonstration is shaped around your agency's workflows, systems and security requirements.