Pricing

Agent-first browser QA with simple allowances

Both Plans include the same core AlwaysQA workflow. Choose based on how many Runs you need during each monthly Billing Period.

Choose your allowance

Same workflow. More Runs when you need them.

Starter

$9

For three Billing Periods

For approved testers who want to evaluate AlwaysQA and provide product feedback.

  • Up to 10 active Test Cases
  • 50 Runs per Billing Period
  • On-demand Runs
  • Daily and Weekly schedules
  • Dedicated QA Accounts
  • Image upload workflows
  • Passed, Failed, and Needs Attention Outcomes
  • Structured Evidence and temporary browser replays
Get Started

The Starter Plan is assigned manually and expires after three Billing Periods unless extended.

Basic

$29

/month

For developers, product owners, and small teams that want ongoing browser QA for important workflows.

  • Up to 50 active Test Cases
  • 200 Runs per Billing Period
  • On-demand Runs
  • Daily and Weekly schedules
  • Dedicated QA Accounts
  • Image upload workflows
  • Passed, Failed, and Needs Attention Outcomes
  • Structured Evidence and temporary browser replays
  • No automatic overages
Get started

Basic remains active until it is cancelled, revoked, or ended by the billing provider.

Core workflow

Included in every Plan

Your allowance changes. The product experience does not.

01

Test Cases defined in plain language

Provide the starting URL, describe the workflow, and define the observable Success Condition without scripting every browser action.

02

A fresh browser agent for every Run

Each Run uses a fresh AI-guided agent that chooses how to attempt the workflow in a real browser.

03

On-demand and scheduled Runs

Start a Run whenever you need one, or schedule a Test Case to run Daily or Weekly.

04

Support for authenticated workflows

Add a dedicated QA Account when the browser agent needs to access a signed-in area of your application.

05

Optional image inputs

Attach an image when the workflow requires the browser agent to complete an upload.

06

Clear Outcomes with Evidence

Every finished Run receives Passed, Failed, or Needs Attention, supported by a summary, observations, and an action timeline. A temporary replay may also be available.

FAQ

Pricing FAQ

Common questions about AlwaysQA Plans, allowances, and billing periods.

What is a Billing Period?

A Billing Period is the monthly window in which your Run allowance applies. It begins on the anniversary day of your Plan Assignment and starts again each month.

What counts toward the Test Case Allowance?

Every non-archived Test Case you own counts toward the allowance, regardless of which Project contains it.

Do archived Test Cases count toward the allowance?

No. Archived Test Cases retain their configuration, Run history, and Evidence without consuming the Test Case Allowance. They cannot be edited, scheduled, or run until restored.

When does a Run use my allowance?

A Run uses the allowance when its browser execution begins. A temporary reservation is created while the Run is queued and released if the Run cannot start.

Do scheduled Runs use the Run Allowance?

Yes. On-demand, Daily, and Weekly Runs all use the same allowance during the Billing Period.

What happens when I reach the Run Allowance?

New on-demand Runs are unavailable and scheduled occurrences are skipped until the next Billing Period begins. AlwaysQA does not add automatic overage charges.

What happens when the Starter Plan expires?

The Starter Plan expires after three Billing Periods unless it is extended. To continue creating or changing Test Cases and starting Runs, you will need a new Plan Assignment.

Can I still access my QA data without an active Plan?

Yes. You retain read-only access to your existing Projects, Test Cases, Runs, Outcomes, and Evidence. You cannot create or change QA data or start new Runs without an active Plan Assignment.

Does AlwaysQA replace our existing QA process?

No. AlwaysQA complements developer testing, automated test suites, and manual QA by repeatedly evaluating important browser workflows.

Start small

Start with one important workflow

Define what success looks like and let a fresh browser agent evaluate it repeatedly.

Get Started