Skip to main content

System Requirements

Hardware, software, and network requirements for Scriptix On-Prem.

Hardware

Minimum (small teams, up to 20 users)

ComponentSpecification
CPU8 cores (x86_64)
RAM16 GB
Storage100 GB SSD
Network1 Gbps (internal)
ComponentSpecification
CPU16 cores (x86_64)
RAM32 GB
Storage500 GB SSD
Network1 Gbps (internal)

Large Deployments (100+ users)

Contact Scriptix for sizing guidance. Key factors:

  • Number of concurrent transcription jobs
  • Average file duration and volume
  • Retention requirements

CPU Architecture

Scriptix On-Prem runs on x86_64 (amd64) processors only. ARM-based servers (e.g., AWS Graviton, Apple Silicon) are not supported for the ASR inference engine.

Storage Considerations

  • Database: ~1 GB base + grows with transcript data
  • Object storage (MinIO): stores uploaded audio/video files, generated documents, and waveform data. Size depends on your retention policy.
  • Model cache: ~15 GB for ASR models (downloaded automatically on first startup by the model-init container into a persistent volume)
  • Temporary uploads: depends on concurrent upload volume

Plan for at least 3x your expected audio/video storage to account for processing artifacts and document exports.

Software

RequirementVersion
Operating SystemUbuntu 22.04+, Debian 12+, RHEL 9+, or any Linux with Docker support
Docker Engine24.0+
Docker Composev2.20+ (included with Docker Engine)

Install Docker

Ubuntu / Debian:

curl -fsSL https://get.docker.com | sh
sudo systemctl enable docker
sudo systemctl start docker
sudo usermod -aG docker $USER
# Log out and back in for group membership to take effect

RHEL / Rocky / AlmaLinux:

sudo dnf install -y docker-ce docker-ce-cli containerd.io docker-compose-plugin
sudo systemctl enable docker
sudo systemctl start docker
sudo usermod -aG docker $USER

Verify:

docker --version   # Should be 24.0+
docker compose version # Should be v2.20+

Network

Ports

The following ports need to be accessible to end users:

PortService
80Web UI
8000API (if accessed directly or via reverse proxy)

Additional ports are used internally between services. Consult your system administrator or the Scriptix team for details on internal port configuration.

Reverse Proxy

For production, put a reverse proxy (nginx, Caddy, Traefik) in front of the API and UI:

  • app.example.com → UI (port 80)
  • api.example.com → API (port 8000)

TLS termination should happen at the reverse proxy level.

Air-Gapped Deployments

Scriptix On-Prem can run completely offline. No internet access is required after the initial image load, provided you use:

  • Offline licensing (license.json + public key)
  • Model cache volume populated (run model-init once with internet, then go offline)

The only features that require internet:

  • Translation (uses DeepL API) — optional, disabled by default
  • Online licensing — alternative to offline licensing
  • Image updates — pulling new versions from the registry

Persistence and Reboots

All data is stored in Docker named volumes that survive container restarts and host reboots.

To ensure services restart automatically after a server reboot:

# Linux: enable Docker daemon on boot
sudo systemctl enable docker

All Scriptix services are configured with restart: unless-stopped — they will come back automatically when Docker starts.