Free
Sign in
Operations command center
Investigate the incident. Preserve the proof. Finish the fix.
One accountable record for support impact, evidence, timeline, ownership, remediation, and review.
Investigation path
Choose evidence by what happened
01
Repeated operational problemPaste redacted call notes, QA comments, tickets, or CSV rows.
Open analyzer
02
Technical or call-path failureInspect HAR, JSON, log, or text captures for structured failure signals.
Open diagnostics
03
Issue happening during a sessionRecord permitted issue flags, mic health, notes, and timestamps locally.
Open live log
Recent activity
Workspace changes
No workspace activity yetSign in to keep a shared audit trail.
No proof, no claimFindings remain tied to supplied rows, captures, or session events.
Explicit cloud savingUploads are processed transiently; workspace saving is a separate action.
Confidence stays visibleProbable causes remain distinct from verified evidence.
Source evidence
Analyse recurring support problems
Use 20 to 50 redacted call notes, QA comments, ticket notes, CSV rows, or transcript snippets.
Evidence standard
Every finding must point back to a supplied row. Uploaded text is not stored by the analysis endpoint.
Rank the repeated issue before treating individual complaints.
Results separate impact, confidence, likely cause, recommended action, and exact supplied proof.
Impact and confidencePrioritised without turning weak signals into facts.
Supplied proofEvery finding links back to the exact evidence row.
Owner and next actionA practical handoff for investigation and remediation.
Evidence report
Waiting
Saved in this browser
Permitted session evidence
Record what happened while the issue is still happening
VeriTriage records user-confirmed flags, optional notes, and local microphone-health signals. It does not record full call audio.
Ready
Microphone access is requested only after Start session.
Microphone healthNot started
Silence is a diagnostic signal, not proof of one-way audio.
One-click flags
Timestamp an observed issue
Session timeline
Timestamped evidence
System alerts
Signals needing context
Analyse HAR and log evidence
Detect authentication, API, WebSocket, WebRTC, network, device, and browser-policy signals without storing the uploaded capture.
No file selected
Before uploading
Remove tokens, cookies, request bodies, and customer identifiers where possible.
What this checks
Identity and sessionLogin, SSO, expiry, redirects, refresh recovery
Network and transportDNS, VPN, proxy, TLS, WebSocket, timeouts
WebRTC and mediaICE, STUN, TURN, call setup, termination, device change
API and service health4xx, 5xx, rate limits, malformed responses, CORS
Browser interferenceExtensions, CSP, mixed content, multiple tabs, sleep, CPU
Technical diagnostic
Upload a capture to begin
The capture is processed transiently.
Diagnostic output
From request failures to a defensible incident timeline
The analyzer groups related symptoms under the most likely primary failure and keeps confidence visible.
Primary causeStructured signal, severity, confidence, and exact evidence.
Session timelineAuthentication, signalling, media, reconnect, and termination.
PerformanceFailures, slow requests, retries, WebSocket uptime, and ICE state.
Recommended fixActionable next step with downstream symptoms grouped below it.
Sign in to manage shared incidents
Evidence tools remain available without an account. Incident ownership, timelines, and actions live in a workspace.
Sign in or create accountSelect an incidentReview its evidence, timeline, actions, and accountable owner.
Trust Center
Checking services
Clear boundaries for support evidence
VeriTriage separates supplied proof from probable causes and makes cloud storage an explicit choice.
Data map
What leaves the browser
Evidence analysisSent to the Cloudflare Worker for transient processing; not retained by the endpoint.
HAR and log capturesSent for transient analysis; raw captures are not written to D1 or KV.
Local reportsRemain in this browser until cleared.
Workspace reportsSaved to Cloudflare D1 only after the user chooses Save to workspace.
Live issue sessionsRun locally; only the completed report is uploaded if explicitly saved.
Bug reportsStored in D1 with obvious identifiers in free text redacted before storage.
PaymentsHandled by Stripe Checkout; VeriTriage does not receive card details.
Report a problem with enough evidence to reproduce it
Reports go directly into the VeriTriage bug inbox. Do not include customer names, payment details, private transcripts, or authentication tokens.
Sign in to manage members and cloud reports
Local analysis remains available without an account.
Sign in or create accountName and access
Members
Workspace access
Plans and purchasing
Start by card or route the purchase through company finance.
Stripe-hosted Checkout supports self-service payment. Invoice, bank transfer, purchase order, direct debit, vendor onboarding, and custom requirements receive a documented finance review.
Local
FreeFor individual evidence analysis and local reports.
- Evidence and HAR/log analysis
- Live issue sessions
- 25 cloud reports with an account
- One member
Shared incident workspace
£49/monthFor one support team sharing evidence and accountable actions.
- Up to 10 members
- 1,000 incidents and reports
- Email invitations and roles
- Timeline, actions, owners, and due dates
- Shared audit trail
Multi-team operations
£149/monthFor support operations managing more people and workspaces.
- Up to 50 members
- 10,000 incidents and reports
- Up to 5 workspaces
- Everything in Team
- Priority procurement support
Company purchasing
Use the payment route your organisation requires
Submit the purchasing details once. VeriTriage will preserve the reference, requirements, and status so finance handoffs do not disappear into email threads.
- Invoice and bank transfer
- Purchase order references
- Direct debit and annual terms
- Vendor onboarding questionnaires
- Tax IDs and finance contacts
Account
Free plan
No paid subscription.
Change password
Account controls
Delete account
Shared workspaces must have ownership transferred before deletion.