Local / Desktop reference architectureUnderwriting support
A Local / Desktop reference architecture for underwriting support in Insurance. Triggered by new application submitted for underwriting, Padiso orchestrates 3 specialist agents on Claude Code + Ollama, on your machines, reaching policy admin system and your tools through the Model Context Protocol, with budgets, approvals and an audit trail throughout.
Local / DesktopRuntime: Claude Code + Ollama, on your machinesTrigger
New application submitted for underwriting
Insurance
Orchestration
Padiso Orchestrator
goals · tasks · heartbeat
Governance
budgets · approvals · audit
Runtime & agents
Agent runtime
Claude Code + Ollama, on your machines
Claims agent
agent
Underwriting agent
agent
Servicing agent
agent
Integrations · MCP
MCP gateway
Your systems
Policy admin system
Rating engine
Third-party data
How the data flows
Trigger: New application submitted for underwriting
- 1
Underwriting agent collects the required inputs and third-party data
- 2
It assembles a complete file and applies the rating rules
- 3
Clear cases are prepared for bind; edge cases route to an underwriter
- 4
Underwriter approves before issuance
Agent team
- Claims agent
- Underwriting agent
- Servicing agent
Integrations
Reached through the Model Context Protocol, scoped and governed.
Runtime & data
Claude Code + Ollama, on your machines
Policy admin system
Rating engine
Third-party data
Security & operational considerations
- Rating rules versioned and auditable
- Human sign-off before bind
- PII access-scoped
Local / Desktop deployment
Self-hosted: agents and models run on your machines, so regulated data and credentials never leave your network. Best when data residency is non-negotiable.
Run this blueprint anywhere
More Insurance blueprints
Run your business on agents.
Start free, or talk to us about putting an agent workforce to work across your operations.