GoQCheck packages

Who it is for

A team of about five people who already keep tickets, tests, and pipeline checks, and who now also ship by describing an idea to an AI. Studio is the license that keeps that work in one GoQCheck workspace.

The workspace

The license covers the day-to-day quality center. Integrations lean on the tools the company already pays for: Jira, Harness, GitHub, GitLab, Bitbucket, Slack, and Microsoft Teams. The bridges change. The center stays.

• Dashboard for the project and its environments: Development, Staging, QA, Production, and CI
• Jira for stories and defects. Trace maps a story to a Playwright spec. A Zephyr token is optional
• TestLab for the behaviors the team already keeps
• Pipelines that run Playwright, including from a phone after a one-time QR pairing

The review record for AI-written code

On each commit or pull request of a connected repository, GoQCheck stores a record a person can read in minutes. The idea the person stated stays separate from the code, so the review can say whether the product matches what was asked.

The person accepts or corrects the verdict. What stays unaccepted stays out of TestLab and out of Jira. That stored record is part of the Studio fee. The agent that drafts the note is billed on its own line.

• Change note: the screens, APIs, data, and permissions the change touched, stored with the commit
• Verdict against the original idea: done, partial, extra, or missing

Included each month

Above those amounts, a paid plan bills overage: automation $0.08 per minute, load $0.02 per VU-minute, storage $0.15 per GB-month, and conversion $0.50 per job.

• 500 automation minutesWorker time for a team of up to 5 seats while Playwright and the pipelines run tests. A run of 8 minutes uses 8. The month holds about 60 runs of that length.Example. The EduMarket smoke (login, catalog, and checkout) takes 8 minutes. Twice each weekday is about 350 minutes. A few longer regressions still fit.
• 1,000 load VU-minutesOne performance test of 50 virtual users for 20 minutes fills this quota. Two tests of 50 users for 10 minutes fit as well.Example. 50 learners browsing /courses for 20 minutes spends the whole 1,000 VU-minutes in a single test.
• 10 GB of artifact and report storageThe month’s room for the traces, videos, logs, and reports those Studio runs leave behind.Example. If that smoke leaves a Playwright trace with video of about 30 MB, 10 GB holds about 300 saved runs.
• 50 conversion jobsUp to 50 files converted in the month. Each file — Gherkin, Selenium, Tosca, JMeter, LoadRunner, or NeoLoad — is one job.Example. Turning 40 EduMarket Gherkin scenarios into Playwright is 40 jobs. 10 remain for a JMeter plan or a Selenium script.

On its own line

Optional AI uses credits or your own key (BYOK): the generator, the review agent, insights, security, and workflow. Accepted drafts, the performance studio, the conversion catalog, and the company trail are on Scale and Apex-Plus.

Who it is for

A mid-size quality organization, about twenty-five seats, that needs conversion, performance, and a picture of the system, and that wants an accepted AI change to become a real test with a result.

Everything in Studio

The seat guide rises to 25. The workspace, pipelines, Playwright, the change note, and the verdict stay in the fee.

Accepted drafts and the run

From the verdict a person has accepted, GoQCheck holds drafts of the delta only. Accepting a draft creates it in TestLab, and it appears in coverage. Jira receives the story only when Jira is connected.

The accepted unit test and the Playwright flow run on the existing pipeline. The result stays on that change: Passed, or Failed with the report still attached and the change still open. Performance and security run when the change touches that area, or on a scheduled pass.

• TestLab behavior
• Unit test
• Playwright flow
• Architecture adjustment
• Observability signal

Performance, conversion, and the picture of the system

Eleven deterministic conversion agents turn an existing suite into the format the pipeline runs. The output is a reviewable file, and a person accepts it before it becomes the record.

• Performance and load, including JMeter
• Gherkin → Playwright
• Text → Gherkin
• Tosca → Playwright and Tosca → Gherkin
• Playwright → JMeter, LoadRunner, and NeoLoad
• JMeter → LoadRunner and JMeter → NeoLoad
• Selenium Java → Playwright and Selenium C# → Playwright
• Observability, and the architecture view of the services a change now calls

Included each month

Above those amounts, a paid plan bills overage: automation $0.08 per minute, load $0.02 per VU-minute, storage $0.15 per GB-month, and conversion $0.50 per job.

• 2,500 automation minutesWorker time for up to 25 seats, including runs of the drafts a person has accepted. The month holds about 300 runs of 8 minutes.Example. The accepted EduMarket checkout flow runs on each commit (8 minutes) and the smoke runs twice a day (16 minutes). Over 22 weekdays that is about 530 minutes. The rest of the 2,500 is left for regression.
• 10,000 load VU-minutesOne performance test of 200 virtual users for 50 minutes, or ten tests of 50 users for 20 minutes.Example. 200 learners on /courses for 20 minutes is 4,000 VU-minutes. Two tests of that size fit, and 2,000 VU-minutes remain.
• 50 GB of artifact and report storageFive times the Studio room, for the larger team, the accepted-draft runs, and the performance reports.Example. Those load reports plus the traces from the accepted runs. At about 30 MB per trace, 50 GB holds more than 1,500 traces.
• 200 conversion jobsAbout 200 conversions in the month across the eleven agents, enough to move a suite that already exists.Example. 80 Selenium Java classes for checkout, 40 Gherkin features, and 20 JMeter plans are 140 jobs. 60 remain for Tosca or LoadRunner.

On its own line

Agent and LLM usage stays outside the fee. The company trail from idea to result, the architecture pack, 100 seats, and the priority identity path are on Apex-Plus.

Who it is for

An organization that wants every seat that reviews, accepts, and audits AI-written work on one license, with the architecture picture and the history from the sentence that started a change to the result that closed it.

Everything in Scale

The workspace, the change note, the verdict, accepted drafts, pipeline runs, performance, the eleven conversion agents, and observability.

The trail from idea to result

A director opens the project and sees one chain: the idea, the code, what the person accepted, what was refused as extra, and the Passed or Failed result. The history answers what the product does now, which idea started it, and what failed. It serves an audit, someone joining the team, and a demo.

The same GoQCheck session on a phone can accept a verdict. The person shipping in a few hours is often away from a desk, and the acceptance still has to happen before anything enters TestLab or Jira.

Architecture pack, seats, and identity

Apex-Plus is the license Sales quotes for a full organization. Contact Sales to start it.

• Architecture packThe map of the system under test: services, the APIs they call, and the data they use, drawn per environment (QA, Staging, Production). When a change adds a call, the map stores that call with the change. Remote access (SSH or RDP) and each service’s health sit on the same picture.Example. EduMarket checkout starts calling membership. Architecture shows that new line, from the cart service to membership, on the environment where it runs. Nobody has to draw the diagram by hand.
• 100 seatsOne hundred people with access on the same organization license. Studio goes to 5 seats and Scale to 25. Apex-Plus holds the people who review, accept, and audit.Example. Engineering, QA, the directors who open the trail, and the person who accepts a verdict from the phone. Up to 100 accounts in the same EduMarket workspace.
• Priority path for MFA and SSOMFA is the second step at sign-in: a code by email or authenticator. An admin can require it for the whole organization. SSO is sign-in with the company’s own identity. On Apex-Plus, Sales opens that connection on a priority path.Example. Miravida’s 100 accounts sign in with the company directory and confirm a code. Selatrop opens that path with priority for the Apex-Plus license.

Included each month

Above those amounts, a paid plan bills overage: automation $0.08 per minute, load $0.02 per VU-minute, storage $0.15 per GB-month, and conversion $0.50 per job.

• 10,000 automation minutesWorker time for 100 seats on the full platform. The month holds about 1,250 runs of 8 minutes.Example. EduMarket on every commit (8 minutes) plus a 40-minute nightly regression. Over 22 days that is about 1,050 minutes. The 10,000 covers several products at that pace.
• 50,000 load VU-minutesOne performance test of 500 virtual users for 100 minutes, or five tests of 200 users for 50 minutes.Example. 500 learners on checkout for 30 minutes is 15,000 VU-minutes. Three tests of that size fit, and 5,000 VU-minutes remain.
• 200 GB of artifact and report storageThe month’s archive for the whole organization: traces, videos, logs, and the report on each result.Example. At about 30 MB per run, 200 GB holds more than 6,000 traces with video for the month.
• 1,000 conversion jobsUp to 1,000 conversions in the month, for several suites or several repositories.Example. Four products, each with a Tosca or Selenium suite of about 200 cases, are 800 jobs. 200 remain for JMeter and NeoLoad.

On its own line

Agent and LLM usage, as credits or BYOK. A private or dedicated tenant, and an on-prem deployment, are quoted with Sales.

Who it is for

A company that commits to evaluating GoQCheck with a Selatrop sponsor. The license is complimentary for twelve months. Sales, or the sponsor, opens it with a private access code.

What the year includes

The Scale platform: the workspace, the change note and the verdict, accepted drafts and runs, performance and load, the eleven conversion agents, observability, and the architecture view. The seat guide follows Scale, up to 25 seats.

Hard caps each month

When a cap is reached, that usage stops. Pilot does not bill overage.

• 2,500 automation minutesThe same worker time as Scale, for the evaluation year. At this cap the runs stop. Pilot does not bill the excess.Example. The EduMarket smoke twice a day plus checkout on each commit fits, as on Scale. The run that crosses 2,500 minutes stops.
• 10,000 load VU-minutesThe same performance room as Scale: one test of 200 virtual users for 50 minutes, or ten tests of 50 users for 20 minutes. At this cap the load test stops.Example. Two tests of 200 learners on /courses for 20 minutes are 8,000 VU-minutes. A third test that asks for another 4,000 stops when it reaches 10,000.
• 50 GB of artifact and report storageThe same artifact room as Scale. At 50 GB, new traces, videos, logs, and reports stop being stored for the month.Example. The trace that crosses 50 GB is the one that no longer gets stored that month.
• 200 conversion jobsThe same conversion room as Scale, about 200 files across the eleven agents. The next file waits until the next month.Example. Job 201, an EduMarket .jmx, waits until the next month.

On its own line

Agent and LLM usage stays on credits or BYOK during the evaluation as well.

A 15-day self-serve trial at miravida.goqcheck.com/signup is the other way to start, before a Pilot is arranged. After the year, the organization moves to Studio, Scale, or Apex-Plus.