Self-Hosted Requirements

definity is delivered as SaaS. This section is for customers who agreed on the self-hosted model with definity. For how that model compares with SaaS, see Deployment Models.

In the self-hosted model, the definity server runs inside your network and stays connected to the definity control plane over one outbound-only path. That connection is required: it is how the server gets fleet-tuned models, analysis and updates.

Installation options

• Kubernetes (Helm)
• Docker Compose

Database

• PostgreSQL 15 or later.
• Either a managed PostgreSQL in your network or VPC (Cloud SQL, RDS, etc.), or the Postgres pod the Helm chart can create, which needs persistent storage.

⚠️ Important

You are responsible for the database's sizing, backup and availability.

Network

• Agents must reach the definity server on your internal network.
• The server must reach the definity control plane at connect.definity.run, outbound over TCP 443 (TLS 1.2+), directly, through your egress proxy or over Private Link. No inbound connection into your network is needed. See Control Plane Connection.
• An SMTP relay for alert emails.