Self-Hosted Requirements¶

This document details the requirements for running Huitzo on your own infrastructure.

Hardware Requirements¶

Minimum Specifications¶

Recommended Specifications¶

Resource Allocation by Service¶

Scaling Guidelines¶

Software Requirements¶

Docker Environment¶

Database Services¶

PostgreSQL and Redis are required but do not need to be containers. Options:

Requirements: - PostgreSQL 14+ (17 recommended) - Redis 6+ (8 recommended)

See Deployment Guide - External Services for connection configuration.

Operating System Support¶

Architecture Support¶

Network Requirements¶

Outbound Connectivity¶

The following endpoints require outbound access:

*License validation has a 7-day offline grace period.

Inbound Access¶

Internal Network¶

All services communicate on a Docker bridge network:

Firewall Rules¶

# Required: Allow HTTPS outbound for license validation
iptables -A OUTPUT -p tcp --dport 443 -j ACCEPT

# Optional: Allow HTTPS inbound (if not using reverse proxy)
iptables -A INPUT -p tcp --dport 443 -j ACCEPT

# Internal Docker network (usually auto-configured)
iptables -A INPUT -i docker0 -j ACCEPT

Storage Requirements¶

Database Storage¶

PostgreSQL storage grows with usage:

File Storage¶

User uploads and pack files require persistent storage. Choose based on your deployment scenario:

Local filesystem (default):

Object storage requirements:

Decision guide:

Network requirements for object storage:

See File Storage Backends for detailed configuration and Deployment Guide for setup instructions.

Backup Storage¶

Plan for backup storage: - Daily PostgreSQL backups: 2x database size - Weekly full backups: 3x total data volume - Retention: 30 days recommended

Security Requirements¶

TLS/SSL¶

Authentication¶

Data Protection¶

Environment Checklist¶

Pre-Deployment Checklist¶

• Hardware meets minimum requirements
• Docker 28.0+ installed (29.x recommended)
• Docker Compose v2.28+ installed
• PostgreSQL 14+ available (container or external service)
• Redis 6+ available (container or external service)
• Outbound connectivity to api.keygen.sh
• Valid Huitzo license key
• SSL certificate for production
• Backup storage configured

Security Checklist¶

• TLS 1.2+ enabled
• Strong database password (20+ characters)
• Secret key generated (openssl rand -hex 32)
• Firewall rules configured
• Reverse proxy configured (nginx/traefik)

Operations Checklist¶

• Monitoring configured
• Backup schedule configured
• Log rotation configured
• Health check alerts configured

Capacity Planning¶

Resource Lifecycle: Pack count does not affect memory requirements. Packs are stateless functions, not persistent processes. Worker count determines throughput. See Resource Lifecycle Management for details.

Estimating Requirements¶

Use this formula to estimate resources:

CPU cores = 4 + (concurrent_users / 25)
RAM GB = 8 + (concurrent_users / 10)
Storage GB = 50 + (users * 5) + (commands_per_month * 0.001)

Example Configurations¶

Small (Startup/Team): - 4 vCPU, 8 GB RAM, 50 GB SSD - 1-10 concurrent users - All-in-one Docker Compose (app + worker + postgres + redis)

Medium (Department/SMB): - 8 vCPU, 16 GB RAM, 200 GB NVMe - 10-50 concurrent users - Docker Compose (app + worker) + external managed PostgreSQL/Redis - Example: AWS RDS + ElastiCache, Azure Database + Cache

Large (Enterprise): - 16+ vCPU, 32+ GB RAM, 500+ GB NVMe - 50+ concurrent users - Docker/Kubernetes (app + workers) + managed PostgreSQL + managed Redis - High availability database configuration - Contact [email protected] for enterprise deployment options

Related Documentation¶

• Deployment Guide – Step-by-step deployment
• Operations Guide – Day-2 operations
• Observability – Monitoring and metrics
• Configuration – Environment variables
• Resource Lifecycle – Pack loading, scaling decision points