Self-hosting

Run it yourself. Keep every key.

Every component in vitonomi — the vault daemon, the hub server, and the SMTP relay — is an open-source AGPL-3.0 binary you can run on your own hardware.

Why self-host

Keep the keys. Keep the infrastructure. Keep the code.

  • No dependence on vitonomi

    If vitonomi disappears, self-hosters lose nothing. The vault, hub, and relay binaries, the data format, and your keys all stay in your hands.

  • Your hardware, your rules

    Run vaults on a Raspberry Pi, a NAS, or a VPS. Run the hub on the same box or a separate one. You choose the topology.

  • Bring your own relay

    Host vitonomi-mx on your own domain for email aliases with zero vitonomi exposure. Or skip the relay entirely and use only credential storage.

Three steps

From clone to first vault in minutes.

  1. Install the vault

    Clone the repo, build with npm install, and start the vault daemon. It listens on libp2p and dials the hub for coordination.

  2. Run a hub (or use ours)

    Start the hub server alongside your vault for full independence, or point your vault at hub.vitonomi.com for a zero-config start. Same binary either way.

  3. Create your cluster

    Initialise a cluster, invite family members, and set per-user quotas. Each member generates their own encryption keys on their own device.

What you get

Exactly what hosted users get. Built from the same code.

  • The same web UI, CLI, and vault daemon as hosted users — same repository, same release.
  • No subscription, no margin, no vendor lock-in.
  • A one-page audit trail: the data format is documented and versioned.
  • A working recovery path from a BIP-39-style seed phrase.
  • Cluster support — invite family members, each with their own keys.

Prefer a hosted hub with managed infrastructure? Open vitonomi.app and get started in a minute.