Self-hosted
Your infrastructure
Best fit
Runs on the firm's own servers via Docker Compose — online or fully air-gapped. Client communication, matter files and backups stay in your custody; Polybase cannot access any of it.
Industries
Industries · Legal
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.
Best fit
Self-hosted
Matter files
Your infrastructure
Access
Per-channel (RBAC)
In transit
TLS 1.3
The confidentiality question
Confidentiality isn't a feature of legal work. It is the work.
Clients tell their lawyers what they tell no one else — and the confidentiality duties your bar rules impose make no distinction between a filing cabinet and a chat thread. The discussion about a matter is as sensitive as the matter file itself. Every additional party that can technically read it is a question you may one day have to answer.
A rented SaaS workspace adds exactly that party: the provider holds administrative access, decides where the data lives, and sits in the processing chain of every confidential conversation. Inside the firm, the picture is no better when matter separation is improvised — ad-hoc groups, forwarded email, shared drives with permissions nobody remembers setting.
Polybase is built for the opposite arrangement. Self-hosted on the firm's own servers, each matter gets its own channel — or its own Polyspace room — with explicit membership and role-based access enforced at the database layer, so walls between teams are configuration you can review, not habits you hope hold. Documents live next to the discussion, with version history. And because you operate the workspace, we cannot read any of it.
Deployment
Host it where your duties point.
Three deployment models, one product. For most firms the answer is self-hosting: the fewer parties who could technically access client communication, the simpler your confidentiality story becomes.
Private cloud
Your own VPC
Strong alternative
Runs inside your cloud account and region using our Docker images. You control network, storage, keys and access — with less hardware to operate.
EU cloud
Our EU cloud
For less sensitive work
We operate the platform in EU regions and your data stays in the EU. A pragmatic option for teams whose work doesn't call for self-custody.
TLS 1.3 protects data in transit in every model. Self-hosted, we recommend disk-level encryption (LUKS or your KMS) — keys that are exclusively yours.
Built for firms
Walls, records and custody — by design.
(01)
Walls you can enforce
Channel membership is explicit and roles come from a fixed permission catalog enforced in database collection rules. A wall between two teams is configuration you can audit — and CI checks it for drift.
(02)
Files that stay inside
Protected file fields and signed share tokens keep matter documents behind the workspace's access rules; the workspace itself is invite-only.
(03)
An append-only record
Message edit history is kept server-side and append-only — what was said in a matter channel cannot be silently rewritten. A general audit log panel is on the roadmap.
(04)
Your servers, your keys
Self-hosted, the encryption keys are exclusively yours — we recommend disk-level encryption (LUKS or your KMS). Polybase has no path to your data.
(05)
Archives you can hold
Portable, SQLite-based database backups restore on any infrastructure running our images; files live on your volumes and back up with your standard snapshots.
FAQ
What firms ask before they commit.
Yes. Each matter lives in its own channel — or Polyspace room — with explicit membership, and role-based access is enforced in database collection rules. Who can see what is reviewable as configuration, not tribal knowledge.
It removes a party from the equation: client communication runs on infrastructure the firm operates, and Polybase has no access to it. How the confidentiality duties your bar rules impose apply to your practice is your call — our part is an architecture with no third party in the middle.
Yes. Docs is a block editor with conflict-free co-editing (per-block locking and presence), version history, comments and full-text search. Built-in viewers open PDF, DOCX, XLSX and PPTX with OCR text extraction, and you can import DOCX and export PDF or Markdown.
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, and self-hosting keeps client data under the firm's control.
Next step
Put the workspace behind your own walls.
We'll walk through your matter structure, access model and hosting constraints, and show how a self-hosted Polybase maps to them — 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
(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
(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