Skip to content
Products
Encrypted Email Messenger Group Chat
Security
How encryption works What our servers can and cannot see Account security Private.Ki over Tor Private.Ki and VPNs
Company
Pricing About Careers Statement Help center Contact
Language
EnglishEN DeutschDE · soon EspañolES · soon FrançaisFR · soon
Create a free account Sign in
Private.Ki Dedicated

Your own Private.Ki. Nobody else on it.

The complete system — encrypted email, messenger, calls, keys — on a dedicated server that hosts only your organisation. Run by us, or handed over to you entirely. Optionally under your own name.

Nothing shared Your domain Your name on it optional
100%
Yours — server, database, keys and domain
100%
Separate — no other customer on the machine
0
Shared infrastructure — no shared queue, storage or attack surface
Separate, entirely

One organisation per server. Nothing in common with anyone else.

private.ki hosts many accounts on shared infrastructure. Dedicated runs the same software for one organisation only, on a machine that carries nothing and nobody else.

  • Own server, own database, own keys, own domain. Every component of the system exists once, for you.
  • No other customer's data, traffic or accounts on the machine — not in the database, not in the mail queue, not in the logs.
  • No shared mail queue, storage or attack surface. What happens on private.ki does not touch your server, and the reverse.
  • The same end‑to‑end encryption as private.ki. The server — ours or yours — never holds a readable copy of a message or a private key.
  • You choose the country, the data center, or your own premises.
  • You choose who has root. Us, under contract, or only you.

Everything on what our servers can and cannot see holds for a dedicated server, with one difference: there is nobody else's data on it to begin with.

Two ways to run it

Managed by us, or operated by you

Same software, same release, same encryption. The difference is who holds root and who does the work.

Managed by Private.Ki

We run it. You hold the content.

  • We provision, patch, monitor, back up and upgrade the server.
  • Same release cadence as private.ki — you get what we ship, when we ship it.
  • We hold root. You hold the content: it is encrypted on your devices and we cannot read it.
  • Support SLA and incident response in the contract.

Exit: full export and hand‑over of the server at any time.

Self‑operated

You run it. We hold nothing.

  • Deployed on your infrastructure — your cloud account, colocation or on‑premises.
  • We install, document and hand over.
  • You hold root and the keys. We hold nothing — no access, no copy, no backdoor.
  • Optional update subscription and on‑call retainer.

Exit: nothing to hand over — it is already yours.

QuestionPrivate.KiDedicated, managedDedicated, self‑operated
Who holds rootPrivate.KiPrivate.Ki, under contractYou
Who patchesPrivate.KiPrivate.KiYou — we tell you when
Where the data livesOur data centerA server that hosts only you, in the country you chooseYour infrastructure
Your own domainPlanned for Plus and TeamsYesYes
Your own brandingOptionalOptional
Support SLADocumentation and emailIn the contractOptional retainer
Under your own name

Your name on the door. Our system behind it.

A dedicated server can present itself as yours. The encryption, the keys and what the server can see do not change; only the name on it does.

  • Your name, logo and colours on the web app.
  • Your domain for mail and for login.
  • Your onboarding and help texts.
  • Tor mirror under your own onion address.
  • Mobile apps under your own name — on request.
What's included

The whole product, not a cut‑down edition

A dedicated server runs the same software as private.ki. Everything the product does, it does on your server.

Mail
Encrypted email End‑to‑end between your accounts, PGP interoperability with the outside, and your own mail domain — or several.
Messenger
Chats, groups, calls One‑to‑one and group chats, calls, secure notes, attachments and stickers. Encrypted once per member, as on private.ki.
Sign‑in
OPAQUE login, device‑bound sessions The password never reaches the server. PIN and passphrase model identical to private.ki; TOTP and QR device pairing included.
Operations
Operator console Invitation links, reserved usernames and the operator console for your own administrators. No administrator can read mail.
Backups
Backups you control Where they go, how often, how long they are kept — decided by you. They contain ciphertext, like the database.
Deployment
Documented, the same path we use The deployment is written down and handed over. It is the path we run private.ki on ourselves, not a separate edition.
Who it's for

Organisations that need the system to be theirs

Where a shared service is the wrong answer — because of the people you talk to, the rules you work under, or the name on the door.

Law firms Medical practices Journalists' organisations NGOs Family offices Public bodies Companies offering secure communication under their own brand
What we don't promise

Three things a dedicated server does not change

We don't say unhackable We say what the server holds, and we show it. The list is the same as for private.ki: ciphertext, public keys, delivery metadata.
It doesn't make weak passphrases strong Keys are protected by the passphrase on each device. A server of your own does not change that — a passphrase policy does.
If you self‑operate, patching is yours We tell you when there is something to apply. We don't do it silently on a server we don't hold.
How it goes

From a call to go‑live, in five steps

CallRequirements, seats, domain, managed or self‑operated, branding.
OfferA fixed setup price and a monthly fee, in writing.
ProvisioningServer, domain, certificates, mail records, onion address if wanted.
Migration helpMailbox import, and key hand‑over for people who already use PGP.
Go‑liveHand‑over documentation and exit terms in writing.
Setup fee + monthly
On request

Pricing depends on seats, hosting and whether we operate the server. We quote a fixed setup price and a monthly fee before anything is provisioned.

Talk to us
Questions

Before you write to us

Can you read our messages on a managed instance?

No. Messages are encrypted on your devices to your recipients' keys before they leave. The server we operate for you holds ciphertext, public keys and delivery metadata — the same list as on private.ki. What the server can and cannot see →

Can we leave?

Yes. A full export at any time, and the server itself either handed over to you or wiped — your choice. The exit terms are in the contract, in writing, before you start.

Do we need our own IT?

Managed: no. Self‑operated: one administrator who can run a Linux server. We hand over documentation and can stay on call.

Can we have our own mobile apps under our name?

On request. Talk to us about what you have in mind.

More on the shared service? Private.Ki for teams →

Talk to us about a dedicated server.

Tell us the size of your organisation, where the server should live and whether you want to run it yourself. We answer with a fixed price.

[email protected]