Quickstart

Sign up, connect your app, and let Qassandra discover and run its first flows. Most teams see a green check inside ten minutes.

1. Create an account

Head to qassandra.com/login and sign in with your work email or Google account. New accounts start on the Core plan, which includes 10 free agent hours per month — enough to discover and run flows on a small app.

2. Add your app

From the dashboard, click Add app and paste the URL you want to test. This can be a production URL, a staging URL, or a preview deployment.

Qassandra will visit the URL, take a screenshot, and use AI to extract:

• A descriptive name for the app
• What the app appears to do
• The likely user personas

You can edit any of this later under App settings → About. Better descriptions and personas help the discovery agent focus on the flows that matter to your users.

3. Trigger your first check

Open the app and click Trigger check. Because the app has zero flows yet, Qassandra runs in bootstrap mode:

1. It opens the URL in a real browser (Browserbase or local Playwright).
2. The discovery agent crawls the app breadth-first, opening menus, modals, and tabs to reveal as many states as possible.
3. For each state it identifies user journeys (e.g. “Sign up with email”) and writes step-by-step instructions plus assertions.
4. Each discovered flow is auto-approved and immediately executed against the same browser session.
5. Screenshots, assertion results, and a Browserbase replay are saved to the check.

4. Review the results

Open the check from the Checks tab to see:

• Per-flow pass/fail status with the failing step highlighted.
• A scrollable strip of step-level screenshots.
• The Browserbase session replay (if Browserbase is enabled).
• Assertion outcomes generated by the AI verifier.
• New flow suggestions awaiting review.

5. Connect your workflow

Once you have flows, wire Qassandra into your release process. Pick whichever fits:

• GitHub App — runs a check on every pull request and posts status back to GitHub.
• Scheduled checks — run on a cron schedule (e.g. every hour against production).
• HTTP API — call from your CI pipeline, deploy webhook, or any other system.

Here's the smallest possible API call to trigger a check:

curl -X POST https://qassandra.com/api/apps/APP_ID/trigger \
  -H "Authorization: Bearer qsk_..." \
  -H "Content-Type: application/json" \
  -d '{"branch": "main", "git_commit_id": "abc123"}'