How Gauntly works

Your app. A closer look.
A practical next step.

Start with a website address. Understand what a check found. Make a focused change, then see what improved.

Start my first check

Step 01

Bring your app, then verify it.

Create a free account and add your deployed website address. Follow the ownership instructions in the app. Browser checks require a verified site and reject private or local addresses. You can start without GitHub.

Step 02

Choose the question you want to answer.

A Quick Check samples pages and interactions. The four AI visitors explore from different perspectives. A code review looks at the GitHub repository or ZIP you provide. These checks cover different things; none claims to test your entire app.

Step 03

Look at the evidence.

Read what was observed, where it happened and why it may matter. Compare the finding with the behavior you intended. An automated finding is a reason to investigate, not a reason to accept a suggested change without review.

Step 04

Make the change. Check it again.

Take the suggested fix prompt to your developer or AI coding tool. Review and apply the change yourself, then deploy it to the right environment. Recheck to see what the new run actually observes. Gauntly does not push code fixes for you.

Step 05

Go deeper with approved staging scenarios.

Cheater and Hacker require an independently verified staging origin, disposable accounts and explicitly approved request recipes. They can send requests and perform approved writes. Setup, authentication proof and assertions are required; data-changing tests also need cleanup. Payment checks require test mode.

Step 06

Keep the release in context.

Use the App Map and recheck history to connect product promises to results. Review the environment, code version and remaining issues before sharing a release receipt. Device previews are browser emulations, not physical-device testing. A receipt is scoped evidence, not a safety guarantee.

Step 07

Know what is kept and what can run next.

Findings and check history help you track progress. Uploaded ZIPs are deleted after review; rehearsal media and staging evidence follow their retention windows. On an eligible plan, Guardian can run recurring checks while allowance is available. Review your usage and settings in the app.

Clear scope matters.

Learn what checks can and cannot tell you.

Security & scope