AegisRunner

// AI test automation for web + native mobile

AI does the testing. You review the results.

No code to write. No sessions to record.Start with a website URL or mobile build. AI agents create and run your tests, so you can focus on reviewing what they find.

Testing a private app? Connect your sign-in details or use local setup for localhost.

Scan Your App Free

Free website scan.
No signup or credit card.

Start an AI-Guided Demo ↗

Live walkthrough on Google Meet.
No booking needed.

Web testing, from setup to evidence

Configure a website, review discovered pages, and find your next testing step.

Explore this workflow →
Web + Mobile
WCAG Accessibility
Localhost & Authenticated Apps
CI/CD
Playwright / Appium Export

// how it works

From your app to tests you can run.

  1. Add your URL or APK/IPA
  2. AI explores your app
  3. Review generated tests
  4. Run tests and inspect evidence

// local development to release

Run tests from local development to release.

  1. Localhost

    Start where you build

    Connect to localhost or a private environment using the command-line tool (CLI) or a framework integration.

  2. Pull request

    Check code changes

    Run tests when a pull request is opened so reviewers can inspect results alongside the code change.

  3. CI/CD

    Repeat checks in CI/CD

    Run the same test suite in your continuous integration and delivery (CI/CD) pipeline.

  4. Release

    Review before release

    Review failures, findings, and coverage before choosing what is ready to ship.

// One workflow across app and browser

Place an order on mobile. Verify it on the web.

Run a connected journey on a real device and in the browser, then review the actions and evidence together.

AEGISRUNNER
illustrative cross-surface journeys…0 / 7

Cross-surface test coverage

AegisRunner runs a single automated test across a customer's mobile app (Android and iOS) and the web (admin console and customer portal), with checks on the destination surface. These are illustrative journeys:

  • customer places an order in the app → admin sees it in the dashboard
  • admin ships the order on the web → customer sees the update in the app
  • admin resolves a request → customer sees it on the web portal
  • customer submits a request on the web → admin sees it in the queue
  • order placed in the app → shows in the customer's web account
  • customer updates their web account → reflected in the app
  • the same customer journey on both phones → compare results
  • customer orders on iPhone → admin sees it in the dashboard
  • order placed on iPhone → shows in the customer's web account

// engineering confidence

Know when it’s safe to ship.

See what failed, where it happened, and the evidence to investigate it. A generated test is not a passing result. See how it works →

Understand the failures

Issues grouped by page

Review functional failures, broken links, visual defects, and audit findings alongside the page evidence.

Keep the coverage

Tests you can rerun

Repeat login, checkout, and multi-step checks after changes. Inspect the actions and expected results in each test.

Catch more than regressions

Audits in the same run

Inspect accessibility, SEO, security headers, performance, and API findings alongside functional results.

Accessibility reports (WCAG 2.2 A/AA)

Download a printable report showing which public and signed-in pages were checked, which accessibility issues were found, and what still needs manual review. Automated checks do not certify compliance. Explore WCAG reports →

// developer ownership

Playwright / Appium export. Your code, your workflow.

Export supported web suites as Playwright TypeScript and native mobile suites as Appium/WebdriverIO JavaScript. Review the code, configure test data, credentials and runner dependencies, and run it in your own repository. The CLI also supports local checks and JUnit reports for CI/CD.

terminal

illustrative Playwright export

import { test, expect } from '@playwright/test'

test('Dashboard is visible', async ({ page }) => {
  await page.goto('https://staging.example.com')
  await expect(page.locator('[data-testid="dashboard-title"]')).toBeVisible()
})
CLI: local scans and CI/CD commands
# run exported tests in your own repository
$ npx playwright test

# scan localhost with a browser on your machine
$ aegis scan --local --url http://localhost:3000

# managed suite execution with JUnit output
$ aegis run --format junit --output results.xml

// security & trust

Know how your test data is handled.

Encrypted saved credentials, workspace access checks, and private artifact links that expire. Understand the safeguards and data flow before connecting your app.

Explore security & data protection →

// customer experiences

What teams check before they ship.

Authenticated journeys, mobile apps, enquiry forms, and accessible reading experiences — with evidence teams can review before release.

AISarvatra

Authenticated web + mobile

“AegisRunner helps us repeat those checks, review WCAG accessibility findings on the web, and inspect screenshots when something fails.”

Read full review from Rajkumar NHead of QA · AISarvatra

“We need our signed-in journeys to work across the web platform and mobile app. AegisRunner helps us repeat those checks, review WCAG accessibility findings on the web, and inspect screenshots when something fails. We spend less time repeating manual checks and have clearer evidence to review before a release.”

Rajkumar N

Head of QA · AISarvatra

Practical Intelligence

Forms + mobile layouts

“AegisRunner helps us check the form, validation and mobile layout after updates.”

Read full review from Matt CCTO · Practical Intelligence

“Our enquiry form is where a new client conversation starts, so a small break matters. AegisRunner helps us check the form, validation and mobile layout after updates. We can review the findings before publishing instead of relying on a quick look at the homepage.”

Matt C

CTO · Practical Intelligence

FindEverythingAI

Search + saved tools

“AegisRunner helps us repeat those journeys and see where they fail, so we can keep improving the directory with a clearer view of what needs attention.”

Read full review from Tyler NHead of Engineering · FindEverythingAI

“Search, filters and saved tools all need to work together. Checking them by hand after every change was easy to put off. AegisRunner helps us repeat those journeys and see where they fail, so we can keep improving the directory with a clearer view of what needs attention.”

Tyler N

Head of Engineering · FindEverythingAI

LetsRinse

WCAG + reading journeys

“AegisRunner helps us review WCAG accessibility findings alongside our reading and navigation checks.”

Read full review from Denise CQA Manager · LetsRinse

“We want our stories to be easy to read and navigate, including for readers who use assistive technology. AegisRunner helps us review WCAG accessibility findings alongside our reading and navigation checks. Having those findings in one place makes it easier to prioritize fixes before publishing.”

Denise C

QA Manager · LetsRinse

Secured Test Everything

Web + mobile + cross-surface testing

“AegisRunner helps us run web and mobile checks and carry a single journey across both.”

Read full review from David JCTO · Secured Test Everything

“Our projects span web and mobile, so testing each surface in isolation leaves a gap. AegisRunner helps us run web and mobile checks and carry a single journey across both. We can review the actions, screenshots and results together, making cross-surface failures easier to investigate before release.”

David J

CTO · Secured Test Everything

// testing guides

Choose your regression testing approach.

// common questions

What teams ask before the first run.

What is AegisRunner?

AegisRunner uses AI to explore websites and native mobile apps and generate tests from what it finds. Teams can review the tests, run them, and inspect the results.

Do I need to write test code?

You do not need to write test code or record a journey to generate tests. Review and edit the generated cases before running them. Login-protected and local apps require additional setup.

Can it test pages behind a login?

Yes. Configure a dedicated test account in App access so AegisRunner can reach signed-in pages. Keep credentials out of chat and use an environment where testing is authorized.

How are AI-generated tests checked?

An AI model creates test cases and a separate reviewer checks for gaps. Eligible web cases are then replayed in a real browser. Check execution results before treating a test as passed.

Will a scan change data in my app?

Actions that create, edit, or delete data require explicit project permission. Enable them only where changing test data is safe, and use dedicated test accounts.

Does it test mobile apps?

Yes. Provide an Android APK or iOS IPA build. Native mobile testing uses real devices; review device setup and plan availability before starting.

What do I get after a run?

Open Runs to inspect execution results and available screenshots or recordings. Discovery findings and generated tests are separate from passing or failing execution results.

Can it run in CI or against localhost?

Yes. Localhost and private-network targets need the CLI or a supported local integration; the public website scanner cannot reach your machine directly. CI runs can produce JUnit reports.

// start with the product you have

Run a website check now. Add deeper testing when you are ready.

Run a public website scan without an account, or create a permanent Free workspace for ongoing testing. Check plan limits and mobile or CI/CD availability on the pricing page.

Already using AegisRunner? Sign in directly