EU cloud
Our EU cloud
Best fit
We operate the platform in EU regions and your data stays in the EU. The fastest start for a startup: sign up, invite the team, point your bots and webhooks at it.
Industries
Industries · Technology
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.
Best fit
EU cloud
Growth path
Your own VPC
Integrations
GitHub · MCP · API
Core plan
€10 /user/mo
The IP question
Your roadmap discussions are intellectual property. Your workspace should treat them that way.
Long before it lands in the repo, your product exists as conversation: architecture debates, incident timelines, roadmap trade-offs, the reasoning behind every decision. That history is intellectual property — and in a rented suite it accumulates on someone else's servers, under someone else's terms.
Polybase puts the conversation next to the work. The GitHub connector links pull requests, branches and commits to tasks and moves statuses automatically as review progresses. Slackbot-compatible API endpoints mean the bots your team already runs can post straight into channels. A message becomes a task in one click, and threads get followed and resolved instead of scrolled past.
And you never outgrow it. Start in our EU cloud; when a bigger customer or your own compliance story demands more, move the same product into your VPC or onto your own servers — backups are portable SQLite files, so the move is a restore, not a migration. AI runs on your own keys, and your content is not used to train foundation models.
Deployment
Start fast. Own it when it matters.
Three deployment models, one product. Most software teams start in our EU cloud and treat their own VPC as the growth path — same images, same data, different boundary.
Private cloud
Your own VPC
Growth path
The same Docker images inside your cloud account and region. When enterprise customers start asking where their data lives, the answer becomes: in our account, under our keys.
Self-hosted
Your infrastructure
For infra-minded teams
Docker Compose on your own servers — online or fully air-gapped. If your team already runs its own stack, the workspace is one more service you control end to end.
TLS 1.3 protects data in transit in every model — and because database backups are portable SQLite files, moving from cloud to VPC to self-hosted is a restore drill, not a migration project.
Built for builders
ChatOps without the tab sprawl.
(01)
Bring your bots
Slackbot-compatible API endpoints let the bot integrations you already run post straight into Polybase channels — authenticated with per-channel API keys whose scopes fail closed.
(02)
Code moves the board
The GitHub connector (HMAC-signed webhooks) links PRs, branches and commits to tasks, moves statuses automatically and comments the task link back on the PR. Flows automates the rest — triggers, conditions, actions.
(03)
AI on your keys
Bring your own model — Anthropic, OpenAI, Gemini or any OpenAI-compatible endpoint, including self-hosted Ollama. Per-model token budgets, editable prompts, and your content is not used to train foundation models.
(04)
Roadmaps on need-to-know
Role-based access from a fixed permission catalog, enforced in database collection rules and drift-tested in CI. Unreleased work stays in the channels you scope it to — and the workspace is invite-only.
(05)
No lock-in, by design
Portable, SQLite-based database backups restore on any infrastructure running our images. The exit — or the upgrade to self-hosting — is a path you can test, not a promise you have to trust.
FAQ
What engineering teams ask us.
Yes. Polybase exposes Slackbot-compatible API endpoints, so existing bot integrations can post into channels once you swap the endpoint and use a per-channel API key with fail-closed scopes. For moving workspace history there are no guided importers yet — we provide migration assistance during onboarding, and automated importers are on the roadmap.
The GitHub connector receives HMAC-signed webhooks and links PRs, branches and commits to tasks. Statuses move automatically as work progresses, and the PR gets a linkback comment pointing at its task. It is one-directional automation around GitHub — we don't claim bi-directional sync with other trackers.
Yes. Poly works with your own keys for Anthropic, OpenAI, Gemini or any OpenAI-compatible endpoint — including self-hosted Ollama or LocalAI. You set per-model token budgets and can edit the prompts. There is also an MCP server with per-channel scoped API keys, so Claude, Cursor or ChatGPT can work with your workspace.
Today sign-in is email/password with magic-link, and workspaces are invite-only with role-based access. SSO/SAML, SCIM provisioning and 2FA are on the roadmap. Desktop and mobile apps are available alongside the web app and installable PWA.
Next step
See it running next to your repo.
We'll connect a GitHub repo, point a bot at a channel and walk your team through the path from EU cloud to your own VPC — in one 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
(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
(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