Install Allure TestOps

Installation is mostly a deployment-choice problem first: where TestOps will run, which dependencies you will manage, and how much operational control you need. The options below help you choose the installation path and gather the shared prerequisites.

Before you commit to a method, make sure the supporting services are ready or planned: PostgreSQL, RabbitMQ, S3-compatible storage, and the session-storage path your chosen deployment expects.

Choose a deployment method

• Kubernetes for teams that already operate a cluster and want a platform-native scalable deployment model.
• Docker Compose for smaller environments, evaluation setups, or simple self-managed installations.
• Linux packages for DEB- or RPM-based server administration.

Check the shared prerequisites

• Review Architecture and planning before you choose the final topology.
• Review Database guidance if you expect significant scale or want better operational posture.
• Review S3-compatible storage if you plan to externalize artifact storage.
• Confirm which reverse proxy, DNS name, and TLS certificate path will front the instance after installation.

Browser compatibility

Allure TestOps supports current releases of modern browsers such as Chrome, Edge, Safari, Firefox, and Opera. Other browsers may work, but they are not guaranteed.

After installation

Continue with Configuration overview to enable networking, SMTP, and authentication.

If you are evaluating the product rather than operating the platform, continue with Getting Started or Use TestOps.