Dashboard & data
The dashboard is where reports land, get triaged, and turn into decisions. It lives at /dashboard and signs in with Better Auth.
Projects & tokens
Every project has public embed tokens (the apiKey you pass to init). Reports arrive in the project the token belongs to. Copy or revoke a token from project settings.
Views
- Inbox — shared issues with report counts, status, severity, category and text filters. Open an issue for its shared AI summary and every original report, or choose All reports to browse individual captures. Review possible matches and correct grouping with merge or split.
- Setup — project details, domain configuration and SDK installation steps.
- Insights — aggregates over time so patterns survive individual reports.
- Usage — the live meter: submissions vs your plan allowance, storage vs quota, prepaid balance (EUR), per-project counts, and the last 6 closed periods. Top-ups and plan changes live in Usage & billing.
- Settings — rename, archive, tokens, allowed origins, webhook, notifications, billing, and integrations.
Limits & spending policies
| Plan | Projects | Submissions / month | AI credit |
|---|---|---|---|
| Free | 1 | 100 | €1.00 / mo |
| Pro | 10 | 10,000 | €3.00 / mo |
For larger requirements, contact us to agree resource allowances, AI credit and support terms.
Choose Stops at limit or eligible paid overage for each resource, and set alert thresholds. Submission and AI allowances reset monthly; reaching them stops new submissions or new AI processing respectively. Storage and seats stay occupied across months: free up storage to make room for new uploads, or remove members to make room for new invitations. An upgrade or eligible paid overage can add capacity. See Pricing.
Overage is opt-in
Each metered resource on the Usage page has a policy switch: Stops at limit (the default) or Overage billing. Overage needs two yeses — a plan that supports it (Pro or Enterprise), and your opt-in for that specific resource. Missing either, usage stops at the included limit and nothing bills. With both, usage past the included allowance continues at the published rate and is drawn from your prepaid balance at period close. Every resource also has an alert threshold (10–100%): cross it and Testosaurus emails you, so surprises arrive as mail, not as charges.
AI usage follows the same opt-in but meters input and output tokens at the current catalog base-token rates plus 5%, against your plan's included credit. The catalog converts gateway rates to EUR and does not reconcile provider invoices or cached-token discounts. Once the credit is used up and you've opted in, AI charges draw from your prepaid balance in real time. When available credit runs out, new distillation stops. Feedback remains available, subject to submission and storage limits; skipped reports are not automatically reprocessed after a top-up. The daily AI spend cap can also stop processing until the next UTC day. Free has no overage, so its €1.00 credit stops processing when exhausted. Alert thresholds apply to the included credit. The Usage page itemizes tokens and metered euros per model.
Automatic top-ups and monthly credit
In Usage & billing, workspace owners on paid plans can authorize a saved refill payment method and enable automatic top-ups. Choose when the balance is low, how much to add and a monthly automatic-purchase limit. Saving a payment method does not enable charges. The limit follows UTC calendar months and includes pending purchases; turn off refills at any time, allowing payments already processing to finish.
Monthly credit adds a fixed amount to your existing monthly Pro invoice, starting at the next renewal. Credit is granted after payment and rolls over in the same prepaid balance as other top-ups. Change or stop the credit line while keeping Pro. Failed payments grant no credit, and funding does not change your resource overage policies. See Pricing & limits.
Activation at a glance
The Usage page has an activation table with one row per project: submissions this month, the first submission date, the first distilled insight date, and the time between the two. A "Not yet" in the insight column means the widget works but no report has been distilled for that project yet — worth a look at its settings.
Export
Every tier can export everything as JSON, whenever you want: reports, distilled fields, and attachments. No lock-in, no ransom, no waiting on support.
The button lives in Settings → General → Data export and downloads one JSON file per project: settings, every submission with its distilled fields, and a manifest of the stored screenshots and replays. The same download is available as GET /api/projects/:id/export — see the API reference for the exact shape.
Turnstile modes
Testosaurus provisions a Cloudflare Turnstile widget per project. Invisible runs silently; Managed can show an interactive challenge when needed. New projects default to invisible. If you bring your own Turnstile keys, manage their mode in your Cloudflare dashboard.
AI settings
Distillation control lives in Project settings → AI & routing. Instead of picking one provider, you assign models to roles — each role meters tokens at its model's catalog rates plus 5%:
- Default — matches differently worded reports and builds or refreshes shared issue summaries. Exact known repeats reuse the existing analysis. It also routes new issue analysis to a deeper analysis role when appropriate. It can be left on the server default.
- Vision — optional. Takes the Default's place when a submission carries a screenshot; the picker only lists vision-capable models.
- Analysis roles — you name the slot and pick the model: "Bug investigator" on a reasoning model, "Idea synthesizer" on a big generalist. The semantic router and category rules dispatch deeper analysis to these roles.
- Coding roles — choose a model, instructions, branch, allowed paths, setup and test commands, and run/monthly budgets. Install the reviewed GitHub Actions workflow, then use Propose fix on a distilled report. Optional automatic categories start a coding role after matching reports arrive. Coding roles produce tested draft PRs for human review.
Auto-assign fills every slot from the model catalog in one click — each slot stays individually editable afterwards. A collapsed Advanced block holds per-category rules: the four distilled categories (bug, confusing, idea, other) can each be pinned to one of your roles, so, say, every bug report is deepened by the bug role's model. A rule beats the router when both would fire.
The model browser behind the slots lists every model on the Vercel AI Gateway — searchable, grouped by owner — with per-1M-token input and output prices, capability badges (vision, structured output, reasoning, free), and a typical-cost-per-report estimate, so the price tag is visible before you pick. The panel footer shows the project's month-to-date AI spend against its included credit.
Coding reserves the role's maximum run budget from prepaid credit and meters actual model tokens at the same catalog rates plus 5%; unused reserved credit is returned once. Your GitHub Actions account runs the job, with no additional Testosaurus execution fee. Run progress, test results, spending and the draft-PR link appear on the report. Only the workspace owner can start or cancel runs; publication already in progress completes its draft handoff. See Reports & distillation.
Invite your team
Under Settings → Access you can invite teammates to your workspace by email. They receive an invite link; accepting it switches their dashboard to your workspace, where they see your projects and reports. Every seat beyond your plan's included seats bills the published seat rate from your prepaid balance, and removing a member frees the seat immediately.
Deep links
Submission detail views have stable URLs, so "look at this one" is a link you can paste into Slack or an issue: /dashboard/?id=…