Deployment

ASP supports single-host private deployment on Linux using the Docker Compose release package.

1. Prerequisites

Operating system

Recommended 64-bit Linux distributions:

Distribution family	Recommended versions
Debian	12, 13
Ubuntu Server	22.04 LTS, 24.04 LTS, 26.04 LTS
Red Hat Enterprise Linux	8, 9, 10
Rocky Linux / AlmaLinux	8, 9, 10
CentOS Stream	9, 10

Docker and network

Before starting, confirm:

• Docker Engine and the Docker Compose plugin are installed.
• The host can access GitHub Releases and GHCR.
• The default HTTPS port 443 is available.
• Redis Stack UI port 8001 and RustFS Console port 9001 are not exposed to untrusted networks.

docker --version
docker compose version

2. Download the release package

• GitHub Releases: https://github.com/FunnyWolf/agentic-soc-platform/releases
• Latest release package: asp-compose.tar.gz

curl -fL -o asp-compose.tar.gz https://github.com/FunnyWolf/agentic-soc-platform/releases/latest/download/asp-compose.tar.gz &&
tar -xzf asp-compose.tar.gz &&
rm asp-compose.tar.gz &&
cd asp-compose

Keep the deployment directory name

Run subsequent commands from the extracted asp-compose/ directory.

Do not rename it. Changing the directory name changes the Docker Compose project name and named volume names, which can prevent services from reading existing data.

3. Prepare a production certificate (optional)

Compose listens on HTTPS only by default. For production, place a certificate issued by an enterprise or public CA at:

certs/asp.crt
certs/asp.key

If these files do not exist, the frontend generates a self-signed certificate on first start. Browser trust warnings are expected.

4. Initialize and start

./scripts/init.sh

init.sh:

1. Creates runtime directories and compose.override.yaml.
2. Creates .env from .env.example.
3. Generates random Django, PostgreSQL, Redis, and RustFS credentials.
4. Pulls images.
5. Runs database migrations.
6. Starts all services.

The random credentials are stored in .env and do not need to be changed manually. Protect this file and do not commit it.

5. Verify the deployment

./scripts/doctor.sh

A successful check confirms the long-running services, PostgreSQL, Redis, Django, custom definitions, and the RustFS/S3 bucket are available.

For failures, see Restart & Operations.

6. Create an administrator

docker compose exec asp-web python manage.py createsuperuser

Use this account with the Platform login method.

7. Access ASP

https://<server>/

When using the generated self-signed certificate, accept the browser certificate warning on first access.

Next Steps

• First Login — Sign in and understand Platform and LDAP accounts.
• Environment Variables — Review all .env deployment settings.
• System Settings — Configure LLM, SIEM, Threat Intelligence, and LDAP.
• Restart & Operations — Check service status and logs.
• Custom Content Deployment — Deploy custom Modules, Playbooks, SIEM YAML, and dependencies.