Pia for business

Your company already uses AI. Now take control of it.

Company data is already flowing into consumer chatbots — invisible, unpoliced, unlogged. Pia replaces shadow AI with a better assistant where you set the rules — from the server down to the individual request.

Made in Germany
Open-source client
No usage data collected Self-hostable
Deployment

Two ways to run Pia.

Both keep the same promise: control over your data stays with you — either because you run the server yourself, or because, with end-to-end encryption, it receives the content you sync only encrypted.

Self-host it

Run the Pia server on your own hardware, in your own network. It comes in two editions on the same image: the free Community Edition — local authentication built in, five users — and the licensed Enterprise Edition, which adds SSO, your own groups, knowledge bases and negotiated seats. Both editions are coming soon. The server is source-available: customers can request the full source for review.

See what each edition includes
  • ✓ Your hardware, your network, your rules
  • ✓ You choose the AI providers — including local models via Ollama
  • ✓ Free with the Community Edition — coming soon, no payment details

Or use Pia Cloud

The same server, operated by us. With end-to-end encryption, your devices encrypt the content you sync before it reaches us, and our server holds the key only in encrypted form; what sync itself needs, such as timestamps and order, stays readable. Our server processes prompts to a Pia Cloud model the moment they arrive and does not store them; one of our model providers keeps them for 30 days to detect abuse. Bring your own AI provider and the prompts never touch our server at all.

  • ✓ No infrastructure to run
  • ✓ End-to-end encryption (optional)
  • ✓ Start free, upgrade when you need to — coming soon

Free will be per person; Pro, the paid plan, from five users up. Both are coming soon.

Control

Control, not a ban.

Banning AI only takes away your view of it. Pia hands you the controls instead: who uses which model, what gets checked before the answer, and what you can trace afterwards.

Who may do what: the group decides.

Every rule hangs on a group and applies to everyone in it: token budgets per hour, day and week, quotas, permitted plugins, knowledge bases. A new hire gets the right rules with the group — not with a ticket. And a spent budget is a stop with a reset time, not a surprise on the invoice.

Which model answers: you set it.

A default model per group, one per mode — text optimization routed differently from the assistant — and one per type for assistant personas, say a code model for developer personas. In front of the assistant sit the guardrails: you decide which check rules apply, which model classifies the requests, and which protected model answers when a rule hits.

What you see afterwards: the record, not the conversation.

An audit log with sign-in anomaly detection, every guardrail verdict, token usage by user, group and model, every device with its status — and one click to revoke a lost one. What the requests contained is in none of them: the token log knows timestamp, model and token count, the guardrail log only a hash of the judged content.

And the console itself is divided: admin roles grant view and manage rights per area — the audit log for data protection, the token board for finance, the groups for IT. Only an owner can hand out rights.

The admin plane in detail
For the people using it

An assistant that doesn’t need a mandate.

The rules ride along in the background — up front is an assistant that wins on its own merits. Here’s what a rollout actually gives your team.

Company knowledge with citations

Server-side knowledge bases scoped to groups: your documents in, cited answers out. Feed them from your own pipelines over a REST ingestion API.

Meetings & transcription

Teams meetings transcribed live with speakers told apart, plus on-device transcription of the room — behind a spoken consent gate. Summaries land where your people can keep them.

Agentic work

Tools are permissions, schedules deliver answers as chats, and every capability can be revoked. Employees can hand bigger jobs to your Pia server to run in the background — behind an explicit consent screen that states exactly what leaves the device, with caps and a job list.

Managed personas

Author a persona once — its voice, its knowledge bases, its tools — and publish it to a group. Everyone gets the same reviewed assistant, and every answer shows which persona wrote it.

Talk to us about your rollout.

Deployment, licensing, security reviews — email us and a person answers, in German or English.