Corvis

Questions from the bench

What's a journey?

A journey is a path a customer takes through your app written in plain English, such as sign up, log in, upgrade to Pro, or ask the AI assistant. Corvis suggests journeys by reading your code and you select the ones that matter. Each one runs in a real browser on your Vercel preview and production deployments, and if a step fails, you get a screenshot, the reason, and a fix brief for your AI coder, with Corvis retesting once the fix lands.

Will it touch my production data?

No. Journeys that change data, like signing up or paying, run only on preview deployments and payments use Stripe test mode. Production checks are read-only: Corvis looks at your live app and never signs up, pays or changes anything there.

What about pages behind a login?

You give Corvis a test account for your app. Its password is sealed and stored encrypted like every other secret Corvis holds, and is used only to run your journeys. You should use a dedicated test account rather than a real customer's account.

What if my app isn't on Vercel?

Corvis can still check your live app on a schedule if you give it your app's public https address and it runs your read-only journeys there, plus a Run now button whenever you want a check. However, preview checks on pull requests are not available yet as they need Next.js on Vercel, so journeys that sign up or pay do not run on other hosts.

How does Corvis know payments or signups stopped?

On paid plans, Corvis learns how many payments from Stripe and signups from Supabase Auth your app normally gets in each hour of the day, keeping weekdays and weekends separate. After about three days of history, if payments or signups stop or fall far below that normal rate, it alerts you, names the deploy it started after, runs your production checks, and offers to roll that deploy back, always asking first.