Private cloud
Your own VPC
Best fit
Runs inside your cloud account and region. Encryption keys stay under your cloud's key management, network and access are yours, and the data never leaves your perimeter.
Industries
Industries · Financial services
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.
Best fit
Your VPC / self-host
Keys
Your key management
Backups
Portable
In transit
TLS 1.3
The regulatory reality
Regulators don't ask whether you trust your vendors. They ask whether you control them.
Financial supervisors across the EU, the UK and Türkiye increasingly treat collaboration software as outsourcing. The questions in a review are concrete: where does the data live, who can access it, how do you monitor the arrangement — and how would you exit it? With a SaaS-only suite, every one of those answers depends on the vendor's goodwill.
That's the structural weakness of renting your workspace: data location fixed by the provider, administrative access held by the provider, exit reduced to export tickets and migration projects. The arrangement may be contractually tidy and still architecturally out of your hands.
Polybase inverts the model. Run it inside your own VPC or on your own servers: data sits in your account and region, access is enforced on the server under your control, and backups are portable files you can restore anywhere Polybase runs. Answering the audit becomes a matter of describing your own infrastructure.
Deployment
Pick the boundary your supervisor expects.
Three deployment models, one product. Most financial teams start in their own VPC — full data control with familiar cloud operations — and the strictest mandates go self-hosted.
Self-hosted
Your infrastructure
For the strictest mandates
Runs in your own data centre — online or fully air-gapped. You own the data, the keys and the operational story end to end; Polybase cannot access any of it.
EU cloud
Our EU cloud
For less regulated teams
We operate the platform in EU regions and your data stays in the EU — a fast start for teams outside the strictest supervisory perimeter.
TLS 1.3 protects data in transit in every model. In your VPC and self-hosted, encryption at rest runs under your own key management or disk encryption — keys we never see.
Built for supervision
Controls you can show, not just cite.
(01)
Need-to-know access
Role-based access from a fixed permission catalog, enforced in database collection rules and checked for drift in CI. Deal rooms and counterparty channels stay exactly as closed as you set them.
(02)
Traceable conversations
Message edit history is server-side and append-only — the record of a discussion cannot be silently altered. A general audit log panel is on the roadmap.
(03)
An exit plan you can test
Standard, portable database backups restore on any infrastructure running Polybase; files stay on storage you control. Your exit strategy is a restore drill, not a negotiation.
(04)
Keys in your custody
In your VPC, at-rest encryption runs under your cloud's key management; self-hosted, on your own disk encryption. Either way, the keys never pass through us.
(05)
Fail-closed integrations
API access uses per-channel keys with fail-closed scopes — an integration can only reach the channel it was issued for, and nothing else by default.
FAQ
What risk and compliance teams ask.
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, which is what outsourcing frameworks ultimately probe. 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, and self-deployment means your existing infrastructure controls keep applying to the workspace.
Message edit history is kept server-side and append-only. Access roles come from a fixed permission catalog enforced in database rules, so entitlements are reviewable as configuration. A general audit log panel is on the roadmap.
Yes, and you can rehearse it: database backups are standard and portable, uploaded files stay on storage you control, and both restore on any infrastructure running Polybase.
Next step
Show your auditors an architecture, not a promise.
We'll map Polybase against your outsourcing and data-control requirements — deployment model, key custody, access model and exit plan — in one working session.
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
(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 canvases for defense organisations and their suppliers — deployed 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 canvases 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