Architecture
Runs inside your environment
Insuronix deploys into your cloud. Policy data stays where it is, bureau content stays under your license, and outputs reach only the people you name.
Single tenant. No data egress. Model weights stay with you.
YOUR ENVIRONMENT
single tenant
Policy admin systemRead only
Bureau contentYour license
State bulletinsPublic record
Outbound to usNone
Deploys to AWS, Azure, GCP, or on-premise Kubernetes
Tenancy
One deployment per carrier. Separate storage, models, logs.
PAS access
Read only, scoped to the fields you approve.
Identity
Your IdP. No separate user directory.
Model weights
Fine-tuned on your book. They stay with you.
HOW IT FITS TOGETHER
Five layers, one environment
Everything inside the dashed boundary runs on infrastructure you control. Feedback from overrides and relevance signals flows back into specialization, which is how the system gets sharper on your book.
01 / DEPLOYMENT
Where the platform runs
Containerized and customized services in infrastructure you already own and monitor.
Single tenant
One deployment per carrier. Separate storage, model weights, logs, and network boundary. Nothing about your book exists in another carrier’s environment.
Ships as Kubernetes
Helm charts and Terraform modules. If your team runs containers today, they can run this.
AWS EKSAzure AKSGCP GKEOn-prem
Your IdP governs access
No separate user directory. When an account is disabled in your directory, access ends at that moment.
What we see
Nothing by default. No usage analytics, no error reports, no model outputs reach us. Support access is time-bound and only when you open a ticket.
02 / DATA
What connects, and what moves
Three input categories, three access models, no copies leaving your account.
| Source | Access | What it reads |
|---|---|---|
| Policy admin system | Read-only API or database view. Credentials you provision and revoke. | Premium by line and state, policy counts, class codes, effective and expiration dates, renewal calendar. No claimant detail, no PII unless you scope it in. |
| Bureau content | Your subscription, pointed at the platform inside your environment. | Circulars, loss cost tables, classification updates, form and rule changes as delivered under your license. Processed where it lands, never redistributed. |
| Public regulatory | Outbound HTTPS to state government sites through your egress rules. | Commissioner bulletins, final orders, filing decisions, hearing notices, independent actuarial reviews. Government records. |
One direction. The platform reads from your systems and writes to the channels you configure. It does not write back to the PAS, change product configuration, or submit filings. Everything it produces is reviewed before anyone acts on it.
03 / AI GOVERNANCE
Auditable at the output, not on trust
Most AI reviews stall on one question. If the system produces an answer, how does anyone check it?
Every output cites its source
A brief that reports a 3.8 percent decrease links to the bulletin that says so. Portfolio figures show the query, the fields, and the data timestamp.
Confidence is visible
Trust scores come from source quality, retrieval relevance, and consistency. Anything below your threshold is held for review instead of going out.
Nothing acts alone
No filing, no binding, no config changes. A human-in-the-loop (HITL) approval gate sits at every point where analysis turns into action, so a person signs off before anything happens. That is a design choice we are keeping.
Provenance on record
Base model, fine-tuning inputs, the reinforcement learning signals from underwriter feedback, update history, and evaluation results. The artifacts your model risk framework asks for, produced by the platform.
Your data trains nothing else. Fine-tuning happens on your instance against your guidelines and your feedback. The weights stay in your environment and no other carrier benefits from your book.
04 / INTEGRATION
Fits the stack you run
A small integration surface means less to secure, monitor, and explain to an auditor.
| Layer | Connects to |
|---|---|
| Policy administration | Your PAS and in-house platforms, over methods such as REST, SOAP, JDBC, or a read replica. |
| Identity | Standard SSO protocols. Group membership drives roles. |
| Delivery | Microsoft 365, Google Workspace, Slack, Teams, Jira, ServiceNow, outbound webhooks. |
| Analytics | Snowflake, Databricks, BigQuery, or a storage bucket if your teams want to build their own reporting. |
| Secrets | AWS KMS, Azure Key Vault, GCP KMS, HashiCorp Vault. Credentials never live outside your KMS. |
05 / SECURITY
Controls that follow from the deployment
Much of a vendor questionnaire exists to establish what happens to data on someone else’s infrastructure. When it never goes there, those sections answer themselves.
Encryption
TLS 1.3 in transit. At rest, your cloud provider’s storage encryption with keys in your KMS. We hold no key that decrypts your data.
Access control
Role and attribute based, mapped to groups in your directory. Regional scoping works the way your group structure already does.
Audit trail
Every query, retrieval, generation, approval, and export logged with user, timestamp, and inputs. Writes to your account, forwards to your SIEM.
Network
Runs in a VPC you define with the egress rules you set. Outbound access is limited to a reviewable list of state government domains.
On certifications. Ask us directly and we will share current attestation status, walk your security team through the control environment, and complete your standard assessment. The useful answer depends on which controls your program cares about.
06 / OWNERSHIP
What you keep if this ends
Worth settling before a contract starts. This is the position, and it is what goes in the agreement.
| Asset | Owner |
|---|---|
| Policy and portfolio data | You. It never left, so there is nothing to return. |
| Fine-tuned model weights | You. Trained on your guidelines and feedback, stored on your infrastructure. |
| Outputs and analysis history | You. Briefs, calculations, filing summaries, the full record. |
| Audit logs | You. Written to your account from day one. |
| Platform code and methodology | Insuronix. The engine, containing nothing specific to your book. |
Exit is a shutdown. You stop the deployment. No extraction project, no migration window, no dependency on us cooperating with a wind-down.
See it running before you review it
Bring your security and infrastructure people to the first call. We will walk the deployment model, the data flows, and the control environment, and answer whatever your assessment is going to ask anyway.