All use cases

Use case · 04

Choose where the workspace runs.

Run Polybase in our EU cloud, inside your VPC or on your own infrastructure. For isolated deployments, pair calls with a self-hosted Jitsi stack.
Hosting
Self-host or managed
Region
EU available
Encryption
TLS 1.3 in transit
Compliance
GDPR principles
Manifesto

The strongest data policy is the one you can host yourself.

Modern collaboration too often means pushing your most sensitive decisions through someone else's datacenter. Polybase reverses that default: you decide where it runs, who can see it, and how long it lives — without losing AI or productivity features.

Cloud · Self-hosted

Two deployment modes. One product.

Polybase Cloud
  • EU region available
    Managed cloud with EU hosting on request.
  • Encrypted in transit
    TLS 1.3 between your team and Polybase; cloud disks are encrypted at the provider level.
  • Sensible defaults
    Standard auth and API tokens (SSO/SAML on roadmap).
  • GDPR principles by design
    Designed around the spirit of GDPR; formal certifications on the roadmap.
Self-hosted
  • Run in your VPC
    Deploy Polybase into AWS, GCP, Azure or a private cloud using our Docker images.
  • Offline / air-gapped
    Self-hosted installs can run on isolated networks with no outbound calls.
  • Bring your own AI
    Plug in OpenAI-compatible providers (OpenAI, Azure, local Ollama / LocalAI) or Google Gemini.
  • Same workspace
    No feature-reduction tier. Self-hosted Polybase has the same features as the managed cloud.
Why it matters

Sovereignty without compromise.

(01)

You pick where it runs

Managed cloud or your own infrastructure. Your data, your environment.

(02)

Self-host friendly

Open Docker images and clear configuration so your ops team stays in control.

(03)

Same product everywhere

Self-hosted Polybase ships the same features as the managed cloud.

Trust

What we focus on.

GDPR
By design
Built around the spirit of GDPR; formal certifications on the roadmap.
Self-host
Available
Run Polybase on your own infrastructure if you need to.
EU
Hosting available
Managed cloud can be hosted in the EU.
TLS 1.3
In transit
Encrypted in transit. At rest: provider-level disk encryption in our cloud; LUKS or cloud KMS recommended for self-host.
How it works

From signature to running workspace.

  1. 01

    Choose your deployment

    Managed cloud or self-hosted on your infrastructure. Both run the same product.

  2. 02

    Connect your team

    Standard email and password auth today, with SSO/SAML on the roadmap.

  3. 03

    Configure storage and backups

    Self-host gives you full control over data location, backups and retention.

  4. 04

    Operate with confidence

    Role-based access and admin controls keep the workspace tidy; a general audit log panel is on the roadmap.

FAQ

About sovereignty and deployment.

Yes. Self-hosted installs can run on isolated networks without outbound calls. AI features depend on the provider you connect.

Yes. You can connect OpenAI-compatible providers (OpenAI, Azure, Ollama, LocalAI) or Google Gemini.

Not yet. SOC 2 and ISO 27001 are on our roadmap. Today we operate around GDPR principles and offer self-hosting for teams that need stricter controls.

Next step

Sovereignty shouldn't cost you productivity.

We'll run a 30-minute deployment workshop with your Security and IT leads and propose the exact shape of a Polybase rollout that satisfies your regulators.

Book a sovereignty call See download options
More use cases
(01)

Replace separate tools without changing

Bring chat, calls, tasks, documents and boards into one workspace while keeping the working habits your team already understands.

Read
(02)

Keep context

Keep messages, tasks, documents and decisions beside the work they belong to, so the reason behind an action stays visible.

Read
(03)

Bring new teammates into one workspace

Give new teammates one place to find the conversations, documents and decisions they need, with a single account to set up.

Read