Industries

Industries · Insurance

Claims data that stays in your custody.

Chat, documents, tasks and calls for insurers and brokers — underwriting, claims and field agents in one workspace, with customer data under your control.
Best fit
Your VPC
Customer data
Your account & region
In transit
TLS 1.3
Access control
Role-based (RBAC)
The confidentiality question

A claims file is a person's life in documents.

A claims file holds accident reports, medical details, bank information, addresses and photographs — a customer's private life, assembled in one folder. Under GDPR and Türkiye's KVKK, much of it is sensitive personal data, and customers hand it over because a claim leaves them no choice. That asymmetry is why regulators, and customers themselves, expect insurers to treat it with unusual care.

Yet a claim is coordination-heavy by nature. It moves between underwriting, claims handlers, field agents and external experts — and when that movement happens over email threads, consumer messengers and personal phones, the sensitive documents move with it. Who saw what, and when, becomes unanswerable. Meanwhile supervisors increasingly review collaboration software the way they review any outsourcing arrangement: where is the data, who can access it, how do you exit?

Polybase puts the whole path in one workspace you run yourself. Deployed in your own VPC, channels follow your portfolios and cases, documents sit next to the discussion that decides them, and access is need-to-know — enforced at the database layer, reviewable as configuration. Polybase is designed around GDPR and KVKK principles, and your data never leaves your perimeter.

Deployment

Run it inside your own perimeter.

Three deployment models, one product. Most insurers choose their own VPC — full data control with cloud operations their IT already runs; the strictest mandates go self-hosted.

Best fit
Private cloud

Your own VPC

Best fit

Runs inside your cloud account and region using our Docker images. Claims conversations and documents stay inside your perimeter; encryption keys sit in your cloud KMS.

Self-hosted

Your infrastructure

For the strictest mandates

Runs in your own data centre — online or fully air-gapped. Data, keys and operations are yours end to end; Polybase cannot access any of it.

EU cloud

Our EU cloud

For less sensitive teams

We operate the platform in EU regions and your data stays in the EU — a fast start for teams whose work doesn't require self-custody.

TLS 1.3 protects data in transit in every model. In your VPC and self-hosted, at-rest encryption runs on your KMS or disk encryption — keys we never see.

Built for insurers

Controls an audit-minded industry expects.

(01)

Need-to-know, case by case

Role-based access from a fixed permission catalog, enforced in database collection rules and checked for drift in CI. A claims channel is open to the people on the case — and no one else.

(02)

A record that holds up

Message edit history is server-side and append-only — what was said about a claim cannot be quietly rewritten. A general audit log panel is on the roadmap.

(03)

Keys in your custody

In your VPC, at-rest encryption runs on your cloud KMS; self-hosted, on your own disk encryption. The keys never pass through us.

(04)

Backups and exit you control

Portable, SQLite-based database backups restore on any infrastructure running our images; uploaded files live on your volumes and back up with your standard snapshots.

(05)

Fail-closed integrations

API access uses per-channel keys with fail-closed scopes — a connection to your core systems reaches the channel it was issued for, and nothing else by default.

FAQ

What insurers ask us.

Polybase runs in any modern browser and installs as a PWA, with web push notifications. Desktop apps (macOS, Windows, Linux) and mobile apps (iOS, Android) are available.

Deployed in your VPC or self-hosted, Polybase is software you operate rather than a service you depend on — data location, access and exit stay under your control. We support your due diligence with architecture documentation and answers to security questionnaires.

Not certified yet — SOC 2 and ISO 27001 are on our roadmap. We answer security questionnaires and architecture questions today. Polybase is designed around GDPR and KVKK principles.

Yes. Channel membership is explicit, and roles come from a fixed permission catalog enforced in database collection rules — reviewable as configuration and checked for drift in CI. The workspace is invite-only; SSO/SAML, SCIM and 2FA are on the roadmap.

Next step

Bring claims coordination inside your perimeter.

We'll walk through your deployment model, access design and data flows — from underwriting to field claims — and show where Polybase fits, module by module.

Industries
(01)

A workspace the state actually owns.

Chat, documents, tasks and calls for public institutions — running in your data centre, under your jurisdiction, operated by your own people.

Read the industry page
(02)

Collaboration that stands up in an audit.

Chat, documents, tasks and calls for banks, insurers and fintechs — with data control you can demonstrate, not just reference in a contract.

Read the industry page
(03)

Patient data that never leaves the building.

Chat, documents, tasks and calls for clinics, hospitals and health-tech teams — self-hosted, so conversations about care stay inside your infrastructure.

Read the industry page
(04)

Built for networks that never touch the internet.

Chat, documents, tasks and boards for defense organisations and their suppliers — deployed with Docker Compose on fully isolated infrastructure.

Read the industry page
(05)

ChatOps, docs and tasks — right next to your code.

Chat, documents, tasks and calls for engineering and product teams — with GitHub automation, Slack-compatible bot endpoints and a self-hosting path your infra team will respect.

Read the industry page
(06)

One workspace, every client in its own lane.

Chat, tasks, docs, whiteboards and calls for creative, digital and marketing agencies — with a clean, permissioned space per client instead of a tool zoo per account.

Read the industry page
(07)

One line from HQ to the shop floor.

Chat, task boards, docs and calls for retail and e-commerce operations — campaign rollouts, store channels and shift handovers in one workspace that runs in the browser on any device.

Read the industry page
(09)

Client confidences, kept by architecture.

Chat, documents, tasks and calls for law firms and in-house legal teams — organised by matter, walled by need-to-know, and hosted on your own servers.

Read the industry page
(10)

Your clients' books, in your custody.

Chat, documents, tasks and calls for accounting and tax firms — one channel per client, every deadline on one board, and financial data on your own servers.

Read the industry page
(11)

Every shipment gets one thread — not a phone chain.

Chat, tasks, docs and calls for logistics teams — dispatchers, warehouses and drivers coordinating across sites and time zones, in the browser on any device.

Read the industry page
(12)

Coordination for plants that keep the internet out.

Chat, documents, tasks and boards for manufacturers — shift handovers, maintenance queues and supplier threads, self-hosted next to the machines they concern.

Read the industry page
(13)

A campus workspace your institution owns.

Chat, documents, tasks and calendars for schools and universities — a space per course or department, run on infrastructure your institution already operates.

Read the industry page