Deployment Center/Installation

Choose an installation type

Choose whether X2 will run on one machine or across a cluster. Each path keeps its relevant installation and networking choices together.

01

Single machine installation

Install X2 on one machine

Use one server for development, evaluation, edge workloads, or a production environment that does not require node-level high availability. No join link or load balancer is required.

Run directly

Terminal quick start

Download X2 and start it in the foreground with one command.

Open quick start →
Run persistently

Install the X2 service

Configure durable storage and register the native operating-system service.

Choose a platform →
Optional

Add encryption

Connect X2 KMS, Vault, or another KMI provider before storing protected data.

Review encryption →

Install the service

Select the operating system of the X2 server.

02

Cluster deployment

Build a multi-node X2 cluster

Use multiple servers for distributed capacity and node-level resilience. Initialize the first node, enroll each additional node with a short-lived join link, then place a load balancer in front of the public endpoints.

Start cluster

Install the first node

Create the cluster identity, bootstrap administrator, and initial consensus member.

Choose a platform →
Expand cluster

Install additional nodes

Create a join link in the Admin UI and configure the new server from it.

Open cluster guide →
Publish service

Add a load balancer

Configure health-aware NGINX or HAProxy routing after the nodes are ready.

Open load-balancer guide →

Install the first cluster node

The same platform guide can later switch to “additional node” mode.

Shared planning for both modes

Prepare object and metadata paths, synchronized time, administrator access, and a deliberate encryption decision. Cluster deployments also require stable private node addresses and open mesh connectivity.

Choose an encryption provider Review production operations