Public paid beta: 100 signup credits included · shared pool or local Docker runner

Learn more
Paid public beta

Qalizer is in a paid public beta. Paid credit packs are available. Features, limits and the interface can still change, runs can be queued or delayed, and AI-generated content is advisory — every single limitation is listed in the capability summary below. Signup credits are granted when your account is created.

Paid public beta prepaid credits

Automate your web QA.
Crawl, generate, run and report — with AI in the loop.

Qalizer crawls your site, generates and records browser scenarios, and runs API, liveness, visual, console/network, load and monkey tests — on the shared server pool or on your own runner — with reports and CI artifacts on a pay-per-action credit model.

  • 100 Signup credits granted at signup
  • 8 Test families modular orchestration
  • Own runner Docker scenarios runs inside your local VPC
  • Pay per action No subscription prepaid credit model
qalizer · run monitor executing shared pool · de

$ qalizer run --url https://your-site.dev --mode deterministic --set checkout

crawlDOM tree & sitemapschedulesharedpassed12s
generateauto scenariosmanualshared8 drafted31s
recordscenario set · checkoutextensionlocal6 steps2m 04s
runrun all · setcisharedrunning14s
runvisual regressionmanualshared1 diff9s
runapi checks · openapicisharedpassed4s
reporthtml · json · junitci gatesharedjunit red1s
8 test families 5 ways to start a run artifacts kept 180 days 100 signup credits granted
Why it exists

Why teams rely on autonomous regression

Manual passes only cover what someone remembered to click. A recorded or generated scenario can be re-run on every release instead.

Regressions reach users unnoticed

Manual passes only cover what someone remembered to click. A broken flow, a shifted layout or a failing request can ship without anyone noticing.

Manual regression takes hours

Re-clicking the same flows before every release costs the same hours each time. Recorded and generated scenarios can be re-run instead.

One workflow, one place

Crawl → generate → record → run → report. Browser scenarios run on a schedule or from CI; the dedicated test families are started individually.

Eight test families

What Qalizer actually runs

Every capability, how it can be started and where it runs is listed in the capability summary below. Anything not listed there is not supported.

01

DOM Tree & Sitemap Crawling

Discover pages with FastCrawl, DeterministicPass or DeepCrawl modes and build a DOM tree and sitemap with complexity-based pricing. How much of the site is reached depends on the mode, depth and page limit you set.

crawldomsitemap
02

Auto Test — AI-Generated Tests

From crawled pages, AI proposes positive, negative and edge-case scenarios. Classification (auth, forms, purchase, navigation) steers generation. Generated scenarios are proposals: review them before you schedule a run.

ai-synthadvisory
03

Scenario Recorder

Record browser flows with the Qalizer Chrome extension or the in-app recorder, review the captured steps, then promote, schedule and run them. Replay can heal a broken selector; healing is best-effort, not a promise that every change is repaired.

recordheal*
Get the Chrome extension
04

Scenario Sets & Scheduling

Group browser scenarios into sets and run them together as “Run All”, with optional AI verification and completion emails. Sets can be scheduled and triggered from CI; the dedicated test families cannot join a set.

setsscheduledrun all
05

Data Injection

Auto-generate or CSV-upload test data and inject it into form fields, replacing recorded values with fresh values per row. Run it against an environment where writing test data is allowed.

csvforms
06

Gremlins Chaos Testing

Monkey testing with configurable intensity and duration. Random interaction can find crashes a scripted test misses — and it can also create, change or delete data in the target, so use it only where side effects are acceptable.

chaosside effects
07

Visual Regression

Baseline screenshots and pixel diffs, with dynamic-content masking to reduce false positives. Differences caused by animation, fonts or videos can still be flagged, so review each diff.

pixel diffbaseline
08

Liveness Monitoring

HTTP health checks on pages and endpoints, run on demand or on a schedule, with status and latency recorded per check. A check needs a reachable target with credentials the environment accepts.

httplatencyuptime
09

Load Testing

Generate concurrent load with a configurable concurrency and duration and read latency/throughput results. Capacity is bounded by the shared pool, so run it against an environment that can absorb the load.

concurrencythroughput
10

API Testing

Discover endpoints from OpenAPI/Swagger or define them by hand, then check status, latency and response shape. API checks run individually or in “Run All”, and in CI only after promotion to a browser scenario.

openapipromoted only
11

Console & Network Log Capture

Capture console messages and network failures per page and surface JavaScript exceptions and failing requests that a passing scenario can hide.

consolenetwork
12

Bug Reports

Failed runs create an issue with the failed step and its screenshots, plus an AI-generated summary that is advisory and may be incomplete.

issuesai-summary
13

Reports — HTML + JSON

HTML, PDF, JSON and JUnit run reports with steps, screenshots and logs. Completed artifacts are kept for 180 days after the run finishes, so export what you need.

htmljsonjunitpdf
14

CI/CD Integration

API tokens and CI runs with exit codes for pipelines. The JUnit document is the gate: a run is green only if it parses and contains no failure, error or skipped element.

tokensexit codesgate
15

Requirements & Traceability

Upload requirement documents and let AI analyse them, then trace generated tests back to requirements. AI matching is advisory — review the coverage list before relying on it.

traceadvisory
16

Local Runner

Run browser scenarios on your own machine with a Docker-based runner, for apps only your network can reach. Execution happens on your hardware; the selected results and artifacts are uploaded to and retained on Qalizer.

dockerown network
17

Real-Time Notifications & Queue

In-app notifications and a live execution queue show when a run finishes or fails while you are on the page. Email notifications are sent for completed runs, and scheduling can also include them.

live queueemail
18

Credit-Based Pricing

Pay per action — crawl, run or test. Every account receives 100 signup credits when it is created. No subscriptions and no per-seat minimums; top up when you need more.

prepaidno subscription
From URL to report

How the beta workflow works

Five steps, each one visible in the product. Your results stay reviewable at every stage.

  1. Create an account

    Register with an email address. The 100 signup credits are granted at signup, before you create anything — no credit card needed to start.

    /register
  2. Add a monitor

    Enter the URL of a site you own or are authorised to test, then choose FastCrawl, DeterministicPass or DeepCrawl. The crawl maps the DOM tree and sitemap within the depth and page limits you set.

    crawl
  3. Generate or record tests

    Let AI propose positive, negative and edge-case scenarios from the crawl, or record flows yourself. Review and adjust them before anything runs on a schedule.

    ai · recorder
  4. Run it your way

    Run one scenario, “Run All” over a scenario set, a schedule, or CI — on the shared server pool or your own runner. API, liveness, visual, console/network, load, gremlins and data-injection tests are started individually.

    5 entry points
  5. Read the evidence

    Open the report with every step, screenshot and capture. Artifacts are kept for 180 days after the run finishes, so download anything you need to keep.

    html · json · junit
Usage-based, prepaid

Credits you buy and spend. No subscription.

Every action has a credit cost that is shown before you start it — from a single API check to a full crawl. A new account receives 100 signup credits at signup; further credits are bought in prepaid packs. Prices can change during the beta.

How Credits Work

Each action, from a crawl to a single API check, has a fixed credit cost that the product shows before it runs. Your balance and usage history are visible at any time.

Per action shown before start
  • Fixed credit cost per crawl, run or test
  • Balance and usage history, always visible
  • No subscriptions and no per-seat minimums
View Credit Costs
FAQ

Your Questions, Answered.

No. You provide a URL, crawl it, and either let AI propose scenarios or record flows with the Chrome extension or the in-app recorder. Reviewing the generated steps and selectors is still recommended, because AI output can be wrong.
After a crawl, a configured AI provider analyses page structure, forms, navigation and classified page types, and proposes positive, negative and edge-case scenarios. The result is advisory: review it before you schedule runs. Which provider answers depends on configuration and availability — the Privacy Policy lists the providers in use.
Yes, through CI tokens and CI runs. A run produces JSON, HTML, PDF and JUnit artifacts, and the JUnit document is the gate: the run is green only when it parses and contains no failure, error or skipped element. Failed or unproven runs fail the CI job. API checks reach CI only after promotion to a browser scenario; the other test families are not exposed through the CI API.
Scenario failures (a step that no longer works), visual differences against a baseline, JavaScript console errors and failing network requests, API status/latency deviations, and load results under the concurrency you configure. No automated test finds every defect, and reports describe the tested moment, not a guarantee.
There is no free plan. Every new account receives 100 signup credits when it is created, and further usage is paid through prepaid credit packs. Credits are usage units, not cash; see the Terms for the restoration policy when our own execution fails.
Browser scenarios run either on the shared runner pool on our server in Germany or on the local runner you start on your own machine. In both cases the selected results and artifacts are uploaded to Qalizer and kept for 180 days, so your Reports page and CI artifacts work the same way. API, liveness, visual, console/network, load, gremlins and data-injection tests run on the shared server pool.
🚀 Get started

Start with 100 signup credits

Register, point Qalizer at a site you are authorised to test, and see what the crawl finds. The beta is a paid service with documented limits — nothing here is a promise of a defect-free release.