DEPLOYMENT

Choose where the server runs.

Self-hosting is the primary deployment model. 127Vaults Cloud is the managed option for customers who do not want to operate their own server.

SELF-HOSTED

Your infrastructure.

You deploy and operate the 127Vaults server on infrastructure you control. Your server stores synchronized encrypted vault data; 127Vaults does not provide hosting or storage under a self-hosted license.

  • You manage the server and its availability
  • Clients are designed for offline access to synchronized vaults
  • Personal and Commercial licenses are planned
View self-hosted pricing
127VAULTS CLOUD

Infrastructure we run.

127Vaults plans to operate the server infrastructure. Customers pay per user for the convenience of managed hosting. Cloud does not change the intended client-side vault encryption model.

  • No customer-operated 127Vaults server
  • Offline-capable desktop and CLI clients are still part of the design
  • 127Vaults manages server operations and updates
View Cloud pricing
PRIVATE NETWORKING

Keep the server private.

The current test installer accepts a loopback or literal private IPv4 endpoint and does not support a public proxy or custom domain. A future supported remote-access design will need an independently verified private-network setup. Do not expose the test server directly to the public Internet.

The server primarily coordinates encrypted synchronization. A temporary outage should not block access to vault contents already synchronized to an authorized device.

SELF-HOSTED SETUP

What you will install.

The planned server distribution is an operator-led bundle with container images for 127Vaults and PostgreSQL, a Compose configuration, an operator command, and file hashes. The web client is served by that server. Desktop, CLI, and browser extension are separate client installs.

You provide a compatible container engine, private network endpoint, certificate trust for each device, persistent storage, and protected backup keys. Initial setup creates server identity and a one-time vault-owner enrollment code. Updates and restores need the matching server identity and a verified backup.

Public installers and downloads are not available yet. The current bundle is for supervised tests with fictitious data.

Check release availability
SELF-HOSTED JOURNEY

From interest to your own server.

01

Request access

Choose Personal or Commercial and leave a contact email. A request does not create an account or charge you.

02

Review terms and release

When available, confirm the license, receive an approved signed download, and prepare a private endpoint, storage, and backups.

03

Install and enroll

Start the server, trust its certificate, and use the local one-time code to create the vault owner. The public customer identity and vault identity are separate.

Paid checkout, public downloads, and license delivery are not open yet. The current installer is limited to supervised testing with fictitious data.

Request self-hosted access
COMPARE PLANS

One product. Two ways to run it.

Compare self-hosted licensing with managed Cloud.

View pricing