Private AI intranet Built for the way insurance teams work

Every model.
One context.
Your private AI.

The sovereign, model-agnostic workspace where insurers, MGAs and brokers learn, collaborate, share and get work done. Put today's best AI models to work across your firm's knowledge—without giving up control of your data.

Private by designModel-agnosticGoverned team knowledge
One context for
UnderwritingClaimsActuarialPortfolio managementBroker teams
The model landscape

The best model today won't be the best model forever.

Reasoning gets sharper. Context windows grow. New specialists arrive. Don't marry your insurance operation to a single model: keep your firm's knowledge in one governed home and let the models change around it.

Reasoning Connect complex evidenceLong context Read the full fileVision & OCR Understand scansClassification Sort at scale
A changing field of models
Model AReasoning
Model BLong context
Your modelPrivate / on-prem
One governed PolicyDock context
Firm knowledge stays useful as models evolve
◈
Claims historyUnderwriting filesPortfolio dataTeam memory
The model harness

The right intelligence for this task.

PolicyDock routes each request to a suitable model under your governance and cost rules. Ask a complex coverage question, analyze a long claims file, read a scanned loss run or classify a batch of submissions—each job gets an appropriate path.

  • Override the selected model for an individual query when you need to.
  • Bring your own private or on-prem model into the same workflow.
  • Keep routing, sensitive-data handling and spend controls in one control plane.
Model routing PolicyDock control plane / illustrative
Incoming queryReview this scanned loss run and flag large-loss patterns.
ReasoningCoverage analysis
Long contextFull claims files
OCR + visionSelected for scan
ClassificationSubmission triage
Private modelSensitive data
Manual overridePer query
Governance control plane
Access rulesData boundariesCost controlsAudit trail
Route approved ↗
Firm feed / Property teamQuestions worth keeping ↗
MRMorgan R. · Underwriting · Today

Which coastal accounts drove the latest loss movement?

Three accounts account for most of the change. The answer links the Q2 loss run with the portfolio exposure notes.

Q2 loss run · p.14Property podReuse answer ↗
AKAvery K. · Claims · Yesterday

Summarize open large-loss development by cause.

Saved prompt and cited answer, available to the claims reviewers with access to this pod.

Claims podEditor accessReuse prompt ↗
SLSam L. · Actuarial · This week

What assumptions changed in the reserve review?

Reserve podViewer accessView cited answer ↗
Collaborative AI

A firm that learns together.

AI work shouldn't disappear into individual chat histories. Memory follows each user and each knowledge pod. A firm feed surfaces questions, cited answers and useful prompts so the next team can build on what has already been asked.

Shared memoryPreserve individual context and pod-level understanding across work sessions.
Reusable answersFind prior queries and prompts instead of spending time recreating the same analysis.
Governed sharingAdmin, Editor and Viewer roles decide who contributes, edits and reads in each pod.
The platform / four connected layers

From what your firm knows to what your firm does next.

A private workspace is only useful when the knowledge inside it moves. Organize it, interrogate it, watch it change and put it to work—without losing the permissions or evidence behind it.

01 / Knowledge pods

Give every body of knowledge a home.

Build focused pods around a portfolio, account, line of business or claim. Each pod holds its own sources, conversations and memory, with independent permissions. Query across pods when your role allows and follow citations back to the underlying evidence.

  • Keep property renewals, claims reviews and reserve work distinct.
  • Ask cross-pod questions when coverage and claims context overlap.
  • Trace answers to a loss run row, policy clause or report page.
  • Give each team the access its work actually requires.
Knowledge pods 3 accessible to your team
▤Property renewalsSubmissions · wordings · exposure
▤Claims developmentLoss runs · adjuster notes
▤Reserve reviewTriangles · actuarial reports
⌘Cross-pod questionPermissions applied
Answer across Property + Claims
Loss movement is concentrated in the coastal segment; the renewal exposure notes provide additional context.↗ Loss run · row 82   ↗ Exposure review · p. 6
02 / Automated BI

Turn documents into a living view.

Extract structure from unstructured files, shape it into tables and build live charts from the results. Drag knowledge pods onto a canvas to compose a dashboard, then tailor what each viewer sees according to their access.

  • Structure loss runs and claims bordereaux without re-keying every field.
  • Track frequency, severity and exposure by segment in live charts.
  • Combine permitted pods on a portfolio review canvas.
  • Show underwriters and executives the views relevant to their roles.
Portfolio canvas Viewer: Underwriting team
+ Property pod+ Claims podDrag pods to canvas ↗
Structured claims table
Coastal · Property12 claims
Inland · Property7 claims
Commercial · Auto9 claims
SourceLoss run ↗
Large-loss trend
Updated from permitted pod sources
03 / Signals

Know when the conditions change.

Define conditions against your data and let signals surface the moment those conditions are met. Keep watch on the movements that matter while your team is busy with the next submission, renewal or claim.

  • Flag a rise in large-loss frequency in a property segment.
  • Watch for claims crossing a reserve or development threshold.
  • Spot changes in an exposure mix before a portfolio meeting.
  • Send each signal with the underlying context for review.
Signals / active conditions Portfolio watch
When this condition is metCoastal property large-loss frequency rises above the team's threshold
↗
Signal triggered / Review coastal property

Latest loss-run data meets the condition. Open the cited source and compare against exposure changes.

Also watchingOpen claim reserve development · Renewal concentration
04 / Automations

Make repeatable work actually repeatable.

Run queries on a schedule or trigger them when new data arrives. Chain steps into a governed workflow, then deliver a report or alert with an audit trail of what ran, what it used and who received it.

  • Refresh a monthly portfolio review from current pod data.
  • Summarize new loss-run uploads for underwriting and claims.
  • Chain extraction, analysis and reporting into one workflow.
  • Keep an auditable record of outputs and recipients.
Automation / Monthly portfolio brief Scheduled + auditable
1 Schedule or new-file trigger First business day
2 Query Property + Claims pods Permissions checked
3 Analyze movements and cite sources Model routed
4 Send report and alert Audit recorded
Last run / Portfolio review ready4 source files · 2 permitted recipients · audit trail available
Connectors / open by design

Meet your knowledge where it lives.

Import documents directly, or use API and MCP pathways to connect PolicyDock with the tools and data flows your organization already uses. These open extension points make room for the sources and workflows specific to your environment.

Shared drivesDocument repositoriesEmail attachmentsSpreadsheetsData warehousesInternal applications

Bring context into one governed workspace

↥
Document importPDFs, scans, spreadsheets and working files
01
{ }
APIsBuild controlled data exchange with your systems
02
◇
MCPConnect model workflows to authorized tools and context
03
Smart OCR / batch processing

Paper in. Queryable knowledge out.

A folder of messy scans shouldn't mean a week of manual re-entry. Smart OCR reads batches of loss runs and claim documents, extracts structured fields and places the results in a cited knowledge pod.

01 / INPUT

Messy source scans

PROPERTY LOSS RUN / SCANNED COPY

Claim no.   00418

Date of loss   04 / 17

Cause   Wind / water

Paid   $84,320

Reserve   $26,500

02 / EXTRACT

Fields made usable

Claim ID00418
CauseWind / water
Paid$84,320
Reserve$26,500
SourceScan · p. 3 ↗
03 / ORGANIZE

A cited knowledge pod

Property claims / Q2

Scanned documents and extracted records, organized for questions, tables and downstream workflows.

↗ Open source page 3
Ask: Which wind claims have the highest open reserve?Cited answer ready for review

Process in batchesMove beyond one document at a time when the inbox fills up.

Preserve provenanceEvery extracted field stays connected to its source scan.

Make it operationalUse structured results in pods, dashboards and automations.

Coming soon / Productivity suite

Go from answer to finished deliverable.

A forthcoming suite will orchestrate models and reusable templates around your company's knowledge to produce the work that follows the analysis: presentations, spreadsheets, reports and collateral. Start from a trusted pod, not a blank page.

  • Reusable templates keep recurring output consistent.
  • Orchestrated models handle research, structure and drafting.
  • Company context and source references travel with the deliverable.
Ask about the roadmap
Board deckQuarterly risk and portfolio review
Excel / financial modelReserve scenario and loss development
BaseScenario A
StressScenario B
SourceReserve pod ↗
Broker collateralProperty program overview
Board reportClaims, underwriting and exposure
Privacy / three pillars

Your intelligence belongs to you.

Insurance knowledge carries sensitive customer, commercial and operational detail. Keep AI useful without moving that knowledge into public-model workflows.

01 /

No public models

Keep proprietary submissions, claims data and internal analysis out of public AI services. Model access runs within your private AI environment.

02 /

Dedicated deployment

Run in a managed private cloud or an on-prem environment aligned with your infrastructure and data-residency needs.

03 /

Isolation and audit

Pod and user boundaries govern who sees what; activity and automated work retain a reviewable audit trail.

Deployment / your infrastructure, your rules

Private AI on your terms.

Different insurers have different requirements for control, operations and residency. Choose the deployment model that fits your environment.

◫
Managed private cloud

A dedicated private environment with managed operations, while keeping your firm's AI workspace separate from public services.

  • Dedicated environment for underwriting, claims and portfolio work
  • Governed access to pods and models
  • Operational support without maintaining the underlying stack yourself
Discuss private cloud
⌘
On-prem, under your roof

Keep deployment within your own infrastructure for teams with stricter internal hosting and data-boundary requirements.

  • Keep sensitive claims and policy knowledge in your environment
  • Bring privately hosted models into governed workflows
  • Align operations with your internal IT and security controls
Discuss on-prem
Frequently asked

Good questions.
Clear answers.

Want to get specific about your documents or deployment needs? Let's talk.

Ask us directly
How does PolicyDock choose a model?

The harness routes a task according to its needs and your governance and cost rules. Users can override the model for an individual query; private and on-prem models can be included in the available choices.

What happens when better models arrive?

Your firm's context lives in PolicyDock rather than in one model's chat history. New models can join the harness without requiring your teams to rebuild their knowledge pods.

Can everyone see every shared answer?

No. Pods have independent access controls, with Admin, Editor and Viewer roles. The firm feed and cross-pod questions respect those boundaries.

What data formats can we bring in?

Import working documents including PDFs, scanned files and spreadsheets. API and MCP pathways also support controlled connections to other workplace data flows.

Can different people see different dashboards?

Yes. Automated BI turns permitted pod data into tables and charts, with dashboard views shaped by each viewer's access.

How is sensitive information protected?

PolicyDock is designed around private models, dedicated deployment, pod and user isolation, governed sharing and auditability.

Where can PolicyDock be deployed?

Choose a managed private cloud environment or an on-prem deployment under your organization's roof. We can discuss the infrastructure and operating requirements that matter to your team.

Make every model work for your firm

One private context.
Much more possible.

See how PolicyDock brings insurance knowledge, people and AI together.

Book a demo