Starter
For one product team creating its first shared quality view.
- 1 project
- Up to 10 connected repositories
- Standard early-access support
Early-access pricing
Plans are based on projects and connected repositories—not per-seat friction. Bring QA, engineering, and product stakeholders into the same quality view.
For one product team creating its first shared quality view.
For growing teams
For growing QA and engineering teams working across several products.
For larger automation landscapes that need organization-level oversight.
For established organizations with custom capacity and operating needs.
Current early-access list pricing per organization, billed monthly. Applicable taxes are not included. Final usage, retention, storage, onboarding, and support allowances are confirmed before activation.
A complete operating loop
We do not split the essential QaCockpit workflow into disconnected feature bundles. Plans primarily scale capacity, onboarding, and support.
Organization and Project Cockpits
Test Executions and campaign reporting
JUnit result ingestion and missing-scope visibility
Test Catalog and test-health history
Failure Inbox and diagnostic evidence
Protected artifact metadata and authorized access
GitHub Actions and Azure DevOps integration paths
Team access without per-seat pricing during early access
Custom capacity
Projects and repository counts do not always grow in neat steps. We can define an individual capacity pack while keeping the same coherent product experience.
Pricing questions
A unique repository connected through a supported CI/CD provider counts once, even when QaCockpit uses more than one workflow, pipeline, branch, or Test Source from that repository.
No. Current early-access plans are shaped around projects and connected repositories. Team access is included so QA, engineering, and product stakeholders can share the same quality view.
No. Appropriate result-volume, retention, and artifact-storage allowances are agreed during early access while we validate real usage patterns. The selected limits are documented before a customer starts a paid plan.
Yes. If the standard project and repository limits do not match your automation landscape, we can define a custom capacity pack without forcing an unnecessarily large plan.
Ultimate includes tailored onboarding, capacity, support, and roadmap reviews. Product improvements must remain secure, reusable, and aligned with the QaCockpit product direction; the plan is not an open-ended custom software contract.
Not yet. Commercial access is currently arranged through a conversation so scope, data usage, onboarding, and early-access expectations are explicit before activation.
Find the right starting point
Tell us how many products, repositories, frameworks, and result streams you operate today.
Contact us