Skip to main content

​
Hardware

These are minimum requirements for a single-node production deployment. Sizing depends on query volume and the number of connectors enabled.
ResourceMinimumRecommended
CPU4 cores8+ cores
RAM8 GB16 GB
Disk50 GB SSD100 GB SSD
Network100 Mbps1 Gbps
For high-availability deployments running multiple replicas behind a load balancer, each node should meet the recommended specifications independently.

​
Software

DependencyMinimum versionNotes
Docker Engine24.0Required for Docker Compose deployments
Docker Compose2.20
The engine runs as a set of Linux containers. No additional runtime dependencies need to be installed on the host.

​
Operating system

Any Linux distribution supported by Docker Engine 24.0 or later. Tested on:
  • Ubuntu 22.04 LTS
  • RHEL 9
  • Debian 12

​
Network

​
Inbound

The engine exposes a single HTTPS port (default 443) for API traffic. Your load balancer or reverse proxy should terminate TLS and forward requests to the engine on port 8000 internally.

​
Outbound (egress)

The engine requires outbound HTTPS access to:
  • Intelligence connectors: each connector requires access to specific external hostnames. See Connector Reference for the full egress list per connector.
  • Intrace license server: license.intrace.ai:443 for periodic license validation. The engine checks in at startup and then on a configurable interval. If the license server is unreachable at startup, the engine will not start.

​
DNS

The deployment host must be able to resolve public DNS for all connector hostnames. Internal DNS resolvers must not block or intercept the required domains.

​
TLS

You must supply a valid TLS certificate for the engine’s hostname. Self-signed certificates are supported for internal deployments but are not recommended in environments where the API is accessed by external systems. The engine does not terminate TLS itself. Bring your own reverse proxy (nginx, Caddy, HAProxy, or your existing API gateway).

​
Next step

Installation