Self-hosted
Your infrastructure
Best fit
Docker Compose on servers your institution already runs. Student data stays inside your network under your keys — and the existing IT budget carries the hosting.
Industries
Industries · Education
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.
Best fit
Self-hosted
Student data
Your infrastructure
Low-ops alternative
EU cloud
Core plan
€10 /user/mo
The campus question
Student data deserves more care than a free consumer app ever promises.
Education runs on coordination — faculty meetings, department planning, course questions, thesis supervision — and much of it has drifted into consumer chat apps and sprawling mailing lists. That's a problem, because conversations about students are conversations full of personal data, and data-protection law such as GDPR sets the bar for exactly that kind of data high.
Polybase gives the institution structure instead: a channel per course, seminar or department — with its chat, docs, tasks, calendar and files in one place. Meetings go out as ICS invites with RSVP; external examiners and guest lecturers join as guests scoped to a single channel; and everything works in the browser on any device, with nothing for students to install.
And it fits how education budgets actually work. Self-hosted, Polybase runs with Docker Compose on servers your institution already operates — the data-protection story and the cost story point the same way. Core is €10 per user per month, with modules added only where you need them. No ops team? Our EU cloud runs the same product, with your data staying in the EU.
Deployment
Run it on the servers you already have.
Three deployment models, one product. Budget-conscious institutions usually self-host — and our EU cloud is the low-ops alternative when nobody should be running servers.
EU cloud
Our EU cloud
Low-ops alternative
We operate the platform in EU regions and your data stays in the EU. The same product with nothing to host — for institutions without an infrastructure team.
Private cloud
Your own VPC
For cloud-first campuses
Runs inside your institution's cloud account and region using our Docker images — your network, your storage, your keys.
TLS 1.3 protects data in transit in every model. Self-hosted, we recommend disk-level encryption (LUKS or your KMS) — and backups are portable SQLite files your IT office can restore anywhere our images run.
Built for the campus
What a semester actually needs.
(01)
Spaces that mirror the timetable
A channel per course, seminar or department — invite-only and role-based. External examiners and guest lecturers join as guests scoped to a single channel: they see their course, not the campus.
(02)
Student data under your keys
Self-hosted, conversations about students stay on infrastructure your institution controls, under disk encryption you manage. Polybase is designed around GDPR principles — and on your servers, we cannot access any of it.
(03)
The calm alternative to consumer apps
Invite-only signup, role-based access enforced at the database layer, TLS 1.3 in transit. The institution's communication runs under the institution's rules.
(04)
Backups your IT office already understands
Portable, SQLite-based database backups; uploaded files live on your volumes and back up with your standard snapshots. Restoring is a drill, not a surprise.
(05)
AI on the institution's terms
The AI assistant is bring-your-own-model — including self-hosted models via Ollama or LocalAI — with per-model token budgets. Your content is not used to train foundation models.
FAQ
What schools and universities ask us.
Yes — that's the model we recommend for education. Polybase deploys with Docker Compose on your existing infrastructure, and database backups are portable SQLite files your IT office can restore anywhere our images run. If you'd rather host nothing, our EU cloud runs the same product with data staying in the EU.
Polybase is designed around GDPR and KVKK principles, and the strongest guarantee is architectural: self-hosted, conversations about students never leave infrastructure your institution controls. Access is invite-only and role-based, enforced at the database layer, with TLS 1.3 in transit.
Today sign-in is email/password with magic-link, and the workspace is invite-only with role-based access. SSO/SAML, SCIM provisioning and 2FA are on the roadmap.
Core is €10 per user per month — Chat, Tasks, Drive (5 GB per user), Calls and Flows included. Add-ons such as Boards, Email and Tables are priced per module, so a department only pays for what it uses. For self-hosted and campus-wide deployments, talk to us.
Next step
Give every course a home.
We'll sketch your campus in Polybase — departments, courses, committees — and walk through the self-hosted setup your IT office would run, 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
(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