Self-hosted
Your infrastructure
Best fit
Runs on your own servers via Docker Compose — inside the same perimeter as your clinical systems. Patient conversations, files and backups stay in your custody, under your keys.
Industries
Industries · Healthcare
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.
Best fit
Self-hosted
Patient data
Your infrastructure
AI models
Bring your own
In transit
TLS 1.3
The sensitivity question
The most sensitive data deserves the most conservative architecture.
Health data is a special category under GDPR — and under Türkiye's KVKK — with stricter processing rules than almost anything else an organisation handles. And the stakes are personal: a leaked roadmap embarrasses a company; a leaked diagnosis follows a human being.
Yet care runs on conversation — handovers, case discussions, shared files, questions between shifts. Every third-party SaaS in that pathway adds another processor, another transfer, another agreement to defend. The safest data flow is the one that never happens.
That is the argument for self-hosting: the collaboration layer runs inside your infrastructure, where patient data already lives and where your existing safeguards, contracts and access policies apply. Polybase is designed around GDPR and KVKK principles — and deployed on your servers, we cannot access your data at all.
Deployment
Keep care conversations where care happens.
Three deployment models, one product. For clinical teams the answer is usually self-hosting — patient data simply never leaves your perimeter.
Private cloud
Your own VPC
Strong alternative
Runs inside your cloud account and region with keys in your cloud KMS — for health-tech teams already operating regulated workloads in the cloud.
EU cloud
Our EU cloud
For non-clinical teams
We operate the platform in EU regions and your data stays in the EU — suitable for administrative and operations teams working away from patient data.
TLS 1.3 protects data in transit in every model. Self-hosted, at-rest encryption runs on your own disks (we recommend LUKS or your KMS) — keys we never hold.
Built for care teams
Confidentiality as an architecture, not a policy.
(01)
Need-to-know by default
Role-based access enforced at the database layer, channel by channel — a ward, a case team or a study group sees exactly what it should and nothing more.
(02)
Files that stay protected
Protected file fields and signed share tokens keep documents from leaking past the room they belong to — no anonymous public links by accident.
(03)
A record you can stand behind
Message edit history is server-side and append-only, so clinical discussions keep an honest trail. A general audit log panel is on the roadmap.
(04)
Your walls, your keys
Self-hosted, patient conversations and files live on your servers under your encryption keys. There is no Polybase-side copy and no path for us to reach them.
(05)
AI that stays in-house
Bring your own model keys — including self-hosted models via Ollama or LocalAI — so assistant queries never have to leave your network. Your content is not used to train foundation models.
FAQ
What healthcare teams ask us.
We don't make a HIPAA-compliance claim. What we offer is architectural: self-hosting keeps patient data inside your infrastructure, where your existing controls, agreements and review processes apply. We answer the architecture questions in your assessment directly.
Self-hosted: on your servers, full stop. The database, uploaded files and backups all stay on infrastructure you operate — Polybase runs where you install it and we hold no copy and no keys.
Yes. Access is role-based and enforced per channel at the database layer, guests are scoped to the channel they're invited to, and protected file fields with signed share tokens keep documents inside the room.
Only what the asking user can already see — the assistant respects the same permissions as a human teammate. You bring your own model keys, including fully self-hosted models, so queries can stay inside your network; your content is not used to train foundation models.
Next step
Keep the conversation inside the clinic.
We'll walk through a self-hosted deployment for your environment — network, storage, access roles and backup routine — and answer your security review's questions directly.
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
(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
(08)
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.
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