Self-Hosted

Self-Hosted is for teams that need to run Allure TestOps in their own infrastructure because of security, operational, or deployment requirements. Platform teams usually move through the same sequence: plan the environment, install the product, configure shared services, and upgrade safely.

Before you choose an installation method, confirm where the required platform components will live: PostgreSQL for primary data, RabbitMQ for background processing, S3-compatible storage for artifacts, and Redis for user sessions. Those decisions affect the topology, scaling model, and operational ownership of the whole installation.

1. Plan the environment

• Architecture and planning

2. Install Allure TestOps

• Choose deployment method
• Kubernetes
• Docker Compose
• Linux packages
• Database
• S3-compatible storage

3. Configure the instance

• Configuration overview
• Network and HTTPS
• SMTP
• Authentication overview
• Backup and restore

4. Upgrade safely

• Upgrade overview
• Upgrade to 5.x
• Upgrade archive

After the platform is running

• Use Getting Started when the next job is onboarding users and proving the product workflow.
• Use Use TestOps for day-to-day testing work inside projects.
• Use Troubleshooting when the platform is installed but not behaving as expected.