Can we ship?
At the end of a release somebody has to answer that, usually in a meeting, usually from memory. AxonQA answers it in a sentence, backed by conditions you set in advance and evidence every authorised project member can inspect.
The assessment can say “ready, with two things you are accepting”, with each exception linked to its owner and reason.
14-day trialNo card requiredSample project included
1.4 · Checkout hardening
Sample Storefront · Checkout hardening plan
- Environment
- Staging
- Record
- Frozen
Ready to ship, with 2 things you are accepting.
Everything that must hold, holds. The rest were accepted by a person, with a reason.
Judged against the project's bar as it stood when the report was made. Later changes to the bar do not change this record.
10 conditions
Matched to this release
6 of 6
Can never be accepted
4 of 4
2 met, 2 accepted
Written once and never rewritten. This is the real published sample, figures and all.
Open the full recordThe evidence chain
The release exists before the report does
Create it in the project and it becomes selectable wherever the evidence is produced. Automation, API and manual results flow into the same release; the evaluator uses the latest result for each test in the release's readiness environment.
Release 4.2
Shared evidence container
Step 1 of 5
Create the release
A release is created before the decision. It becomes a named place that every relevant testing area can attach results to.
Release
4.2 · Checkout improvements
Readiness environment
Staging
Release 4.2 is open
Now selectable across the project
Choose a step, or move through the release from creation to frozen assessment.
Results from other environments stay visible as supporting evidence. They never silently replace the target-environment result. When you assess, AxonQA freezes the evidence, rules and verdict at that moment; later runs update the live release and belong to the next assessment.
The verdict
Three answers, because there are three real situations
Most releases are not clean and not blocked. They ship with known, deliberate compromises, and the honest tooling says so.
Ready to ship.
Every condition you set is met. Nothing is being waved through.
Ready to ship, with two things you are accepting.
The compromises are named, attributed and reasoned. This is where most releases actually live, and it is the state a badge cannot express.
Not ready to ship.
A must condition failed. A must can never be accepted away, so the assessment names exactly what remains unresolved.
The bar
One project policy, matched to each release
Your team configures the bar centrally. The release's declared scope and attached evidence activate the relevant conditions automatically. A failed must makes the verdict Not Ready; an unmet should can be accepted only by a named person with a reason.
Execution completed
Every planned check must produce a result. Manual work cannot disappear as skipped, blocked or unfinished.
Reads from Manual, automation and API execution
Critical failures and bugs
A high-impact failure cannot hide inside a healthy percentage, and unresolved bugs are judged only against this release's checks.
Reads from Test priority, tags and defect tracking
Coverage and requirement change
Coverage is measured against the acceptance criteria this release touches, with unresolved requirement drift kept visible.
Reads from Release stories and test traceability
Evidence health
Freshness, quarantine and ownership remain explicit while only the latest result in each target-environment browser lane counts.
Reads from Environment, run provenance and ownership
Why it needs one workspace
A verdict stitched together across tools is difficult to trust
The evidence spans execution, requirements, defects, environments and ownership. AxonQA keeps the chain together and current.
A tool that only runs automation has no manual phases to check, so it cannot know whether a person ever worked the exploratory pass. A tool that only manages test cases runs nothing, so it has no pass rate of its own. Neither has your bug severities, your story coverage and your requirement drift sitting in the same place as the run.
Teams often try to rebuild that picture by hand from several tools and people’s memory. The result takes time to assemble, is difficult to reproduce and begins ageing as soon as another run finishes.
Because everything already lives in one project, the live position stays current. When the team is ready to decide, AxonQA freezes that evidence and the bar into a formal assessment that later activity cannot rewrite.
Receipts, not vibes
Every acceptance records the person, the time and the reason. Six months later you can still answer why a release went out with a known bug.
One governed policy
The bar is managed centrally in project settings. Release scope activates the relevant controls without inventing a separate standard at sign-off.
A history that does not move
Every release keeps its frozen assessments, so new evidence can update the live position without rewriting what the team knew before.
Portable, but still protected
Download the frozen record as a PDF or share it through email, Slack or Teams. The assessment link still requires project access.
Understand the verdict, then act on what is blocking it.
The rules-based evaluator computes the readiness verdict. Axon reads the latest assessment and explains the conditions, accepted risks, and outstanding work in plain English. From there it can help run the missing checks, investigate failures, draft tests for coverage gaps, or prepare a bug. It cannot alter a frozen verdict or accept risk for someone. If an authorised user explicitly asks to change the project policy, that remains a separate, permission-checked action.
Who it helps
The same answer, for the three people who need it
The person shipping it
You stop reconstructing the picture from four tabs the night before. The conditions were agreed weeks ago and the answer is already computed.
The person who has to sign it off
You see what is being accepted and by whom before you agree, instead of finding out in the incident review.
Everyone asking on the day
A sentence every authorised project member can read in one place, so the question stops being routed through one person's memory.
Answer it on your own release.
Start a trial, create a release, attach evidence from the environment that matters, and freeze a decision your team can defend.
14-day trial · No card required · Sample project included