Requirements

Manifest Self-Hosted runs on a single Linux host. That same host is also where you run the manifest-installer CLI to drive installation and upgrades — there is no separate installation client. The sections below describe the host and network requirements.

Host Requirements

Supported Operating Systems

Debian 12
RHEL 9
Ubuntu 24.04

Only x86_64 architectures are supported at this time.

Resource Requirements

	Minimum	Recommended
Compute	16 vCPU	48 vCPU
Memory	64 GB	192 GB
Storage	300 GB	3 TB

See Configuration Reference → Storage Configuration for the recommended volume layout.

Required Software

None. A fresh, supported Linux host with sudo access is enough: manifest-installer deploy installs the OS prerequisite packages itself, and k3s embeds containerd as its container runtime. Docker, Ansible, Python, and the AWS CLI are not required.

Network Environment Requirements

DNS

You will need to configure DNS records pointing to your host's IP address. This includes records for the main application, API, authentication service, and object storage buckets. Review the DNS Configuration guide to understand the required DNS records and plan your DNS setup.

Inbound Ports

The Manifest deployment uses the following ports on the host. deploy opens them in the host's own firewall; your network must allow them from wherever users and administrators connect:

TCP 80 (HTTP)
TCP 443 (HTTPS)
TCP 6443 (Kubernetes API)
TCP 31999 (Zarf in-cluster registry)

Outbound Access

If your environment restricts outbound traffic, you must allow access to the external services required for installation and runtime operations. Review the Firewall Configuration guide for the complete list of domains that must be accessible. If the host cannot reach the internet at all, use the Air-Gapped Deployments workflow instead.

Next Steps

Once you have verified that your environment meets these requirements, proceed to gather the required credentials.