Industries

Industries · Accounting

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.
Best fit
Self-hosted
Client data
Your infrastructure
Backups
Portable (SQLite)
In transit
TLS 1.3
The trust question

A firm that keeps everyone's numbers has everything to lose.

An accounting practice holds a complete financial portrait of every client: payroll, bank statements, tax filings, ownership structures. Much of it is personal data under GDPR and KVKK; all of it is confidential by the standards of your profession. Clients rarely ask where it's stored — they assume the answer is 'with you'.

Then there's the calendar. Closing periods and tax season compress a year of coordination into a few weeks — and when that coordination runs on email threads and consumer messengers, deadlines live in inboxes, client documents drift into the wrong chats, and separation between clients is whatever people remember to maintain.

Polybase gives the practice one workspace it runs itself. Each client engagement gets its own channel — documents, tasks and discussion in one place, membership explicit. Deadlines become tasks with due dates, statuses and List, Board and Timeline views. And self-hosted, everything stays on your infrastructure, with portable backups you can hold in your hand.

Deployment

Keep the books in the building.

Three deployment models, one product. For accounting and tax firms we recommend self-hosting: client financial data stays on hardware you own, and backups stay in your hands.

Best fit
Self-hosted

Your infrastructure

Best fit

Runs via Docker Compose on your own hardware — online or fully air-gapped. Client data, files and backups stay in the practice's custody; Polybase cannot access any of it.

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

A fast start

We operate the platform in EU regions and your data stays in the EU. A pragmatic way to begin — and portable backups mean you can move to self-hosting later.

TLS 1.3 protects data in transit in every model. Self-hosted, we recommend disk-level encryption (LUKS or your KMS); in our cloud, disks are encrypted at the provider level.

Built for practices

Separation, records and backups — the fundamentals.

(01)

A separate room for every client

Each engagement is a channel with explicit membership; roles come from a fixed permission catalog enforced in database collection rules. The team on a client sees that client — and nothing else by default.

(02)

A record you can stand behind

Message edit history is server-side and append-only — what was agreed about a filing cannot be quietly rewritten. A general audit log panel is on the roadmap.

(03)

Backups you can pick up

Portable, SQLite-based database backups restore on any infrastructure running our images; uploaded files live on your volumes and back up with your standard snapshots.

(04)

Keys that stay in the practice

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)

Files behind access rules

Protected file fields and signed share tokens keep client documents behind the workspace's permissions; the workspace itself is invite-only.

FAQ

What practices ask us.

Yes. Self-hosting is a Docker Compose deployment, and deployment help is available on request — or start in our EU cloud and move later: backups are portable SQLite files that restore anywhere our images run. Support replies within 24 hours on weekdays.

Deadlines become tasks with due dates, assignees, statuses and workflows, viewed as List, Board or Timeline. Channel calendars carry meetings with ICS invites and reminders, and Flows automates recurring reminders on a schedule.

Core is €10 per user per month — Chat, Tasks, Drive (5 GB per user), Calls and Flows. Add-ons per user per month: Boards €5, Email €3, Polyspace €5, Tables €10, AI €5 with fair-use limits. Self-hosted and enterprise pricing is custom — talk to us.

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 practice's control.

Next step

Give every client a room and every deadline a place.

We'll walk through your client structure, deadline calendar and hosting preference, and show how Polybase fits the practice — 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
(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
(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