Quickstart: On-Premise Stack Deployment

Comprehensive guide to deploying a self-hosted DEZ Platform node on your infrastructure using the automated one-command installer.

System Requirements

1. Obtain Your Deployment Token

1. Sign in to your Client Portal.
2. Navigate to Deployments and click Create Deployment.
3. Set your server hostname or domain and copy the generated Deployment Token (dep_tok_...).

2. Run the One-Command Installer

Execute the following command on your target server with root or sudo privileges:

curl -fsSL https://deznot.com/install.sh | sh -s -- --token=YOUR_DEPLOYMENT_TOKEN

Advanced Installer Flags:

# Custom installation directory (default: /opt/dez-platform)
curl -fsSL https://deznot.com/install.sh | sh -s -- --token=dep_tok_... --dir=/srv/dez-platform

# Headless / CI/CD unattended mode
curl -fsSL https://deznot.com/install.sh | sh -s -- --token=dep_tok_... --yes

3. What the Installer Does Automatically

1. Environment Detection: Automatically detects whether docker compose or podman compose is installed.
2. Registry Authentication: Authenticates against the secure private image registry with a temporary read-only token.
3. Cryptographic Secrets Generation: Generates high-entropy encryption keys for database security, sessions, and JWT tokens.
4. Configuration Assembly: Builds a hardened .env file and tailored docker-compose.yml based on your subscription tier.
5. Microservice Launch: Pulls and starts the platform services:
   • back_client — Core API and WebSockets server.
   • nexus_agent — Licensing and telemetry daemon.
   • omnistream_gateway — High-performance real-time gateway (WebSocket / QUIC).
   • auth_proxy — Authentication and security gateway.
   • admin_frontend — Web management dashboard.
   • caddy / nginx — Reverse proxy with automated SSL/TLS certificates.

4. Verification & Health Monitoring

Once the installation completes, verify your running containers:

cd /opt/dez-platform
docker compose ps

Check the nexus_agent licensing connection:

docker compose logs nexus_agent --tail=50

Once connected, your deployment in Client Portal will immediately transition to Active (Healthy) status.