Skip to content

Deployment

QualityMax offers a hosted product experience and is validating a Sovereign deployment model with private-preview design partners. Choose a deployment approach based on where application access, test execution, artifacts, and model requests are allowed to run.

The hosted service is the standard way to evaluate QualityMax. Your team signs in to the web application, creates projects and test cases, and uses the available execution paths for its automation workflows. Confirm that the target environment and test data are appropriate for an external service before connecting them.

Sovereign is intended for organizations that need the QualityMax control plane and test artifacts to remain in infrastructure they operate. The current private-preview design covers customer-managed networking and TLS, local database and artifact storage, and an optional model gateway chosen by the customer. Exact components and operational responsibilities are agreed during the design-partner process; this page is not a completed installation recipe or a statement of compliance certification.

Before an evaluation, document:

  • the network paths from QualityMax runners to applications under test;
  • identity, access-control, and administrator requirements;
  • database, object-storage, backup, and retention ownership;
  • approved model providers and outbound connectivity rules;
  • artifact sensitivity and test-data handling requirements;
  • monitoring, upgrades, incident response, and support responsibilities.

QualityMax and the customer then validate the proposed architecture against those constraints before installation. Availability and supported topology can change during the private preview, so request a current deployment review rather than relying on a generic configuration.

For the product model used across deployments, see core concepts. Teams evaluating repository workflows can also start with the team evaluator guide.