Self-hosted
Air-gapped, your infrastructure
Best fit
Docker Compose on fully isolated networks. No outbound connection required, no telemetry, no dependency on us. You manage updates, backups and access end to end.
Industries
Industries · Defense
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.
Deployment
Air-gapped
Outbound connections
None required
Telemetry
None
Video calls
Self-hosted LiveKit
The isolation requirement
In a restricted environment, the first question isn't features. It's whether the system runs with the cable unplugged.
Defense organisations and their supply chains work in environments where outbound connectivity is not a risk to be managed but a condition to be excluded. Vendor trust is beside the point: if a tool needs to reach its maker to function, it doesn't belong on the network.
That single requirement disqualifies most modern collaboration suites. They are services, not software — built to be reached, updated and measured from outside. An 'on-premises' label with a licence server and telemetry endpoints is not isolation.
Polybase ships as Docker images you deploy with Docker Compose on your own isolated infrastructure. It runs fully offline; calls use a self-hosted LiveKit server inside the same network. No telemetry, no outbound calls required — and updates arrive as images you bring in through your own controlled process.
Deployment
One product, deployed inside the wire.
The same three deployment models exist across Polybase — but this page is about the far end of the spectrum: fully air-gapped self-hosting.
Private cloud
Your own VPC
For less restricted programmes
Runs inside your cloud account and region with your keys in your KMS — a fit for supplier collaboration outside classified boundaries.
EU cloud
Our EU cloud
For unclassified work only
We operate the platform in EU regions. Suitable for open, unclassified coordination — not for restricted environments.
TLS 1.3 protects data in transit in every model. Air-gapped, the keys, the disks and the entire operational story are exclusively yours.
Built for isolation
What survives inside the perimeter.
(01)
Fully offline operation
Runs with zero outbound connectivity and no telemetry. Every module — chat, docs, tasks, boards — works with the network sealed; calls use a self-hosted LiveKit server.
(02)
Invite-only, role-based access
The workspace is invite-only, with roles from a fixed permission catalog enforced at the database layer and guests scoped to single channels.
(03)
An append-only record
Message edit history is kept server-side and append-only — what was written stays traceable. A general audit log panel is on the roadmap.
(04)
Backups under your process
Portable, SQLite-based database backups plus files on your volumes — captured, stored and restored entirely by your own procedures, on your schedule.
(05)
Your keys, your hardware
Everything runs on infrastructure you own, under disk encryption you control (we recommend LUKS). We hold no keys and no copies — there is nothing on our side to compromise.
FAQ
What defense IT asks us.
Yes. Polybase deploys with Docker Compose on isolated infrastructure and runs fully offline; calls use a self-hosted LiveKit server inside the same network. No outbound connection is required at any point.
Updates ship as Docker images. You bring them across your own controlled transfer process — a checked medium, a data diode, whatever your doctrine prescribes — and you decide when to apply them. Nothing updates itself.
No. Polybase requires no telemetry and no outbound calls to run. On an air-gapped deployment there is no traffic to us because there is no route to us.
Accreditation of a deployed system is your process, on your infrastructure — and self-hosted isolation is designed to support exactly that kind of review. For our own organisation: not certified yet — SOC 2 and ISO 27001 are on our roadmap, and we answer security questionnaires and architecture questions today.
Next step
Collaboration inside the wire.
We'll walk through an air-gapped deployment end to end — image delivery, LiveKit configuration, backup procedure and access model — against your environment's constraints.
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
(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