FAQ
Frequently asked questions
The long tail: comparisons, auth, billing, access. If yours isn't here, email support@supergorilla.ai and a person will answer.
How is this different from Playwright or Cypress?+
Different layer. Playwright and Cypress are frameworks: you write the tests, maintain the selectors, and debug the flake. SuperGorilla is a service: it runs your app and tests it like a user, with no test code in your repo and nothing that breaks when the UI changes.
How is it different from an AI code reviewer?+
A reviewer reads the diff. SuperGorilla runs it. A reviewer can tell you the code looks wrong; SuperGorilla can tell you the signup form throws on submit, with the recording. The two compose well; nothing about running one replaces the other.
Our agents write tests too. Why this?+
Generated unit tests assert that the code does what the code does. Neither they nor the diff can catch a broken flow in a real running app: a form that renders but never submits, a redirect loop, a payment that silently fails. That takes using it.
Will it work with my stack? Monorepo? Multiple services?+
Virtually any web application. SuperGorilla works out how to run yours on its own, and you can steer it in plain English when your setup needs a hint. Bring the weird stack; that is what the beta is for.
How does it log in? What about OTPs and SSO?+
With test credentials you provide, stored encrypted. Auth flows are handled as part of the run, and we help you set up seeded test accounts during onboarding. If your auth does something unusual, tell us, in plain English, in the steering notes.
What happens if my app fails to start?+
The run reports that, with the output that explains why, and you are not billed for it.
Can I tell it what to test, or is it fully autonomous?+
Both. Left alone, it derives tests from what changed. Soon you can also record your critical flows once and have them tested on every change. Steered, it follows plain-language instructions, from "focus on checkout" to "skip the admin panel entirely."
Can I limit what the agents are allowed to do?+
Yes. Guardrails are hard limits set in plain English: pages to stay out of, actions never to take, data never to touch. Steering shapes what a run focuses on; guardrails bound every run, every time.
How noisy is it? Will it flag things that are not real?+
Every finding ships with a severity rating, repro steps and a recording, so judging one takes seconds rather than an investigation. And SuperGorilla remembers your app between runs; the longer it runs, the quieter it gets.
How do I control when it runs, and the bill?+
You configure the trigger per project: on every push to a pull request, whenever selected branches change, or on demand. One push is one test, however many flows the agent finds. You are alerted before overage applies.
When do mobile and desktop arrive?+
In development. Web is live today; iOS, Android and desktop are next. Book a demo and tell us which you need; it genuinely shapes the order.
How do I get started?+
Sign up and connect a repository. There is no waitlist. Since SuperGorilla learns your app with every run, starting sooner compounds.
What happens to my data?+
The short answer: repo access is scoped, credentials are stored encrypted, recordings are yours and purgeable, and Enterprise plans can route model traffic through their own provider account. The longer answer is on the security page.