AI does the testing. You review the results.

You can get test code that way, but you still have to run it, keep it working, and check that it's right. AegisRunner finds what to test, drafts the tests for you to review, runs them on real browsers and real phones, and shows you the screenshots and video behind the results.

Yes. The free website scan needs only your email address (no account and no credit card) and checks the pages it reaches for accessibility, search, security settings and speed. The Free plan is permanent. It covers one website and includes 2 scans and 5 test runs a month. Paid plans are Starter at $19 a month, Pro at $49 a month and Business at $149 a month.

No. You do not write test code or record your own steps. AI creates the tests, and you can review and edit them before they run.

Websites and mobile apps. On a website, AI explores the pages it can reach and writes tests for what it finds, such as forms, buttons, navigation and the links between pages. It also reports broken links and pages. For a mobile app, you upload your Android or iPhone app file and the tests run on real phones (Pro and Business plans). Anything that creates, edits or deletes data in your app needs your permission for the project first.

Yes. Each scan checks the pages it reaches against the WCAG 2.2 guidelines (levels A and AA) using axe-core, an open-source accessibility checker, and lists what needs fixing page by page, next to the search, security-settings and speed checks. Automated checks cannot judge everything, for example whether an image description makes sense or how a page works with a keyboard and a screen reader, so the WCAG report also lists what a person still needs to review. It is not a compliance certificate.

With Playwright or Selenium, your team writes the test code, keeps it working as the site changes, and runs it somewhere. With AegisRunner, AI explores your site and drafts the tests, you review and edit them, and AegisRunner runs them on its own browsers and phones, on a schedule if you like, and keeps the results. It runs on Playwright underneath, and you can export tests as code: Playwright for websites, Appium for mobile apps. If you want full control over every assertion, writing the tests yourself may suit you better.

Not for small changes. Each step remembers several ways to find the same button or field, such as its test ID, its name, its label or its text. If the first one no longer matches, the run tries the others, so a restyle or a moved button often does not break the test. If the page has really changed, for example a button has been removed, the test can fail and the result shows a screenshot so you can decide what to do. Changed behavior still needs your review.

The result shows the steps that ran, which one failed, the error message and a screenshot, and a recording of the test when one is available. Where AegisRunner can tell, it also says what likely went wrong, such as a change in your app or a problem with the test itself, and it says "cause unverified" when it cannot. A check that could not be confirmed is marked "needs review" instead of passed. Edit the test or fix your app, then run it again.

Yes, on the Pro and Business plans. Upload your Android or iPhone app and AegisRunner drafts tests from the screens it records on a real phone; you review them, then run them on real phones.

Not on customer websites yet. Testing pages behind a login is currently available only on our controlled demos; customer activation is pending. Customer sign-in testing is currently paused for both websites and mobile apps. Until then, customer scans are limited to pages that do not require sign-in.

Actions that create, edit, or delete data require explicit project permission. Turn them on only where changing test data is safe. Where sign-in testing is available, use dedicated test accounts.