Industries

Industries · Agencies

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.
Best fit
EU cloud
Client separation
Channel-level RBAC
Client email
Channel inboxes
Core plan
€10 /user/mo
The trust question

Client confidentiality is not a clause in your MSA. It's part of the pitch.

Agency work is other people's secrets: embargoed launches, unreleased creative, media budgets, strategy decks. When a prospect's procurement team asks where their data would live and who could see it, "a Slack here, a Trello there, a Drive folder somewhere" is not a reassuring answer — and it is how much of the industry actually runs, multiplied by every account.

Polybase collapses the per-client tool zoo into one workspace. Each client gets a channel with its own chat, tasks in List, Board and Timeline views, docs, whiteboards, drive, calendar — and its own email inbox, so client mail lands next to the work it belongs to. Role-based access keeps each channel exactly as closed as you configure it, and your team only sees the clients they work on.

That structure becomes a selling point. You can tell a client precisely who has access to their channel, show that message edit history is kept append-only on the server, and answer data-protection questions with an architecture rather than assurances. And when an engagement ends, handover is clean: docs export to PDF and Markdown, and your archive lives in portable backups, not in a dozen scattered accounts.

Deployment

Run it where your clients are comfortable.

Three deployment models, one product. Most agencies choose our EU cloud — nothing to operate, data in the EU — and move up the ladder when a client mandate asks for more.

Best fit
EU cloud

Our EU cloud

Best fit

We operate the platform in EU regions and your data stays in the EU. Every workspace runs as its own single-tenant instance — and there are no servers to run for a team built for client work.

Private cloud

Your own VPC

For strict client mandates

The same Docker images in your own cloud account and region — for agencies whose clients require data to sit in infrastructure the agency controls.

Self-hosted

Your infrastructure

For full custody

Docker Compose on your own servers. The strongest confidentiality story an agency can tell: client conversations never leave hardware you own.

TLS 1.3 protects data in transit in every model, and each workspace is a single-tenant instance. Backups are portable SQLite files — your agency's history is never trapped in anyone's cloud, including ours.

Built for client work

Separation your clients can be shown.

(01)

A clean room per client

Channels are permissioned with role-based access from a fixed catalog, enforced in database collection rules. People see the clients they work on and nothing else — and the workspace itself is invite-only.

(02)

Client email inside the channel

Each client channel can have its own inbox: mail arrives next to the tasks and files it concerns, with rules, labels, snooze, scheduled send and undo-send. Connect existing Gmail, Microsoft 365 or any IMAP/SMTP account.

(03)

Who approved what, on record

Message edit history is server-side and append-only, docs and whiteboards keep version history, and task workflows support status approvals — so sign-off is a record, not a memory.

(04)

Poly handles the busywork

The AI assistant drafts, summarises and searches across the workspace, and a daily brief keeps account leads current. It runs on your own model keys, and your content is not used to train foundation models.

(05)

Clean offboarding

When an engagement ends, work leaves cleanly: docs export to PDF and Markdown, files live on your volumes, and portable SQLite backups mean the archive belongs to you.

FAQ

What agencies ask us.

Give each client a channel and scope membership to the account team. Roles come from a fixed permission catalog enforced in database collection rules — access is configuration you can review, not tribal knowledge. Per-channel API keys with fail-closed scopes keep integrations inside their lane too.

Meetings support external guests with ICS invites and RSVP, so clients join calls without needing workspace accounts. Files can be shared through signed share tokens. For closer collaboration, invite a client contact into their own channel — they see that channel and nothing else.

There are no guided importers yet — we provide migration assistance during onboarding, and automated importers are on the roadmap. Docs import DOCX, whiteboards import draw.io files and tables import CSV, so the assets that matter most move early.

Core is €10 per user per month — chat, tasks, drive (5 GB per user), calls and workflow automation. Add what you use: Boards €5, Email €3, Polyspace €5, Tables €10 and AI €5 per user per month. Book a demo and we'll map it to your team.

Next step

Make confidentiality part of the pitch.

Bring your client list — we'll sketch your channel structure, permissions and inboxes in a live workspace, and show what your next procurement questionnaire could say.

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
(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