Self-hosted
Your infrastructure
Best fit
Docker Compose on your own servers — in the plant or in your data centre, online or fully offline inside a closed network. Production data, keys and backups never leave your custody.
Industries
Industries · Manufacturing
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.
Best fit
Self-hosted
Production data
Your infrastructure
Telemetry
None
In transit
TLS 1.3
The OT/IT reality
The plant network is separated for a reason. Your collaboration tool shouldn't fight that.
Manufacturing runs on a discipline most industries never need: the separation of OT and IT. Production networks are segmented, internet access is the exception, and every new system must justify the connections it wants to open. A collaboration suite that only exists as someone else's cloud fails that test before the evaluation starts.
So the coordination that actually runs a plant — shift handovers, downtime notes, maintenance queues, quality issues, supplier questions — falls back to paper, whiteboards and private messenger groups on personal phones. The knowledge that keeps the line running lives everywhere except in a system the plant controls.
Polybase is built the other way round. It deploys with Docker Compose on your own servers — inside the plant network if that's where it belongs. It runs fully offline; calls use a self-hosted LiveKit server. Shift channels, handover docs and supplier threads live next to the production they describe, and nothing about the plant leaves the plant.
Deployment
Run it where the production data lives.
Three deployment models, one product. Most manufacturers self-host — so the collaboration layer follows the same rules as the rest of the plant.
Private cloud
Your own VPC
For corporate functions
Runs inside your cloud account and region using our Docker images — a fit for engineering, procurement and corporate teams outside the plant perimeter.
EU cloud
Our EU cloud
For office teams
We operate the platform in EU regions and your data stays in the EU — a quick start for teams without an infrastructure mandate.
TLS 1.3 protects data in transit in every model. Self-hosted, we recommend disk-level encryption (LUKS or your KMS) — keys that stay on the plant floor, not with us.
Built for the plant
What survives three shifts and an audit.
(01)
Runs inside the closed network
No telemetry, no outbound calls required. Polybase runs fully offline; calls use a self-hosted LiveKit server inside the same network. Updates arrive as Docker images through your own controlled process.
(02)
Handovers that leave a trace
Shift notes live in docs with version history and comments; message edit history is server-side and append-only. What the night shift knew, the morning shift can read — and nobody can quietly rewrite it.
(03)
Suppliers see their channel, not your plant
The workspace is invite-only, with roles from a fixed permission catalog enforced at the database layer. Supplier contacts join as guests scoped to a single channel.
(04)
Your servers, your keys
Everything runs on hardware you control, under disk encryption you manage — we recommend LUKS or your KMS. Polybase has no path to your production data.
(05)
Backups in your maintenance plan
Portable, SQLite-based database backups plus files on your volumes — captured and restored by your own procedures, on the same schedule as the rest of the plant.
FAQ
What manufacturing IT asks us.
Yes. Polybase deploys with Docker Compose on your own infrastructure and runs fully offline; calls use a self-hosted LiveKit server inside the same network. No telemetry, no outbound calls required — updates come in as images through your controlled process.
A channel per line or shift carries the running conversation; handover notes live in docs with version history and comments; open issues move across Kanban boards with statuses, assignees and due dates. The next shift starts from the state of the line, not from memory.
Yes. The workspace is invite-only and access is role-based, enforced at the database layer. Supplier contacts join as guests scoped to a single channel — they see the discussion you invited them to, and nothing else.
Not certified yet — SOC 2 and ISO 27001 are on our roadmap. We answer security questionnaires and architecture questions today, and self-hosting means your existing plant and IT controls keep applying to the workspace.
Next step
Bring coordination inside the fence.
We'll walk through a plant deployment end to end — network placement, offline operation, backup procedure and the shift-handover setup — against your OT/IT 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
(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
(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