Installations

Install TestingOps On-Premise on your own infrastructure

TestingOps On-Premise runs inside your network: your test cases, evidence, defects and knowledge never leave your servers. Three installation paths are supported.

Path	Best for	Guide
Docker Compose	A dedicated Linux server or VM — the pilot and most installations	Docker installation
Helm	A Kubernetes cluster you already operate	Helm installation
Kubernetes manifests / OpenShift	Clusters where Helm is not allowed	Kubernetes · OpenShift

What you receive from the TestingOps team

Registry credentials for the TestingOps image registry.
The installation kit — testingops-configs.zip (Docker) or the Helm chart / manifests.
A license file (license.txt). Without it the product starts in community mode; it never blocks the start.

Requirements

	Minimum	Recommended
CPU	4 vCPU	8 vCPU
Memory	8 GB	16 GB
Disk	100 GB (evidence, videos and screenshots grow)	SSD, 250 GB
OS	Linux x86_64 or arm64 with Docker Engine 24+ and Compose v2	Ubuntu 22.04 / 24.04
Network	Outbound HTTPS to the registry and to the model provider(s)	Fixed address or DNS name for the UI
Database	Bundled PostgreSQL 17 (pgvector)	Your own PostgreSQL 15+ with the pgvector extension

Optional: a corporate HTTPS proxy and its root CA, an S3-compatible object store for evidence (storage), an SMTP relay for invitations and password resets.

Where runs are executed

Test runs are executed by RunningOps, either the cloud service or an instance installed in your network. TestingOps On-Premise talks to it over HTTPS; nothing else of your test estate leaves the installation. Without an execution engine the product works in manual-execution mode.

Versions and support

Releases are monthly (2026.10.0). Each release is supported for 12 months; an installation may be at most two releases behind to receive support. Upgrades are forward-only (schema migrations); always take a backup first — upgrade.sh does it for you.