2-minute setup • Works with GitHub Actions + GitLab CI

Stop digging through CI logs.
See every failed Playwright test in one link — across all shards.

SentinelQA aggregates traces, screenshots, video, and console logs into a single CI failure dashboard so you can triage faster and ship with confidence. Artifacts stay in your S3. Setup takes 2 minutes.

No credit card. Remove anytime. No lock-in.
GitHub ActionsGitLab CICircleCIJenkinsBuilt for parallel Playwright pipelinesArtifacts stay in your S3
Master Link • Grouped Failures • One-click Trace • AI Summary on Open
Master Link
Grouped Failures
Open Trace
AI Summary

See a real CI failure in seconds.

Open a run and instantly see grouped failures across shards, the exact failing step, and the artifacts you need to debug — without downloading anything.

Top failure: login.spec.ts → redirects after login
Top failure: login.spec.ts → redirects after login
Open Trace
Open Video
Copy Master Link
AI summary appears when you open a failed test.

CI failures shouldn’t take 30 minutes to understand.

Without SentinelQA
  • Download artifacts from multiple shards
  • Search CI logs for the real failure
  • Open traces locally and guess what matters
  • Ask “which shard failed?” in Slack
  • Reproduce locally just to confirm
With SentinelQA
  • Open the master link for the run
  • Failures are grouped automatically
  • Open trace + video + console in one click
  • Read an AI summary when you open a failed test
  • Share the exact failure frame in Slack or Jira
Cut triage time from “digging” to “deciding.”
Typical triage time
40 min → 40 min
40 min → 5 min

Built for fast, confident Playwright CI triage.

One master link per run
Master Link

SentinelQA merges failures across every parallel shard into a structured, searchable dashboard.

Trace + video + logs in one view
Visual Triage

Open the exact failure moment instantly — no artifact hunting, no context switching.

Artifacts never leave your cloud
Your S3, Your Data

Store heavy artifacts in your S3. SentinelQA stores only lightweight metadata.

Understand the failure before opening the trace.

When you open a failed test, SentinelQA generates an AI failure summary from logs and screenshots — so you can quickly identify the likely cause and what to do next.

  • Likely root cause in plain English
  • Key evidence (console errors, HTTP status, timeouts, selectors)
  • The first meaningful failure signal (not the noisy symptom)
  • Suggested next step to confirm or fix
AI failure summary
Likely cause: session expired redirect loop after login
Likely cause: login redirect didn’t complete
Evidence: stuck on /auth for 10s • /api/session returned 401
Next step: verify auth cookie / environment variables

Add one step to CI. That’s it.

Connect your S3 bucket (artifacts stay there)
Add the upload step to your pipeline
Get a master link for every run
No infrastructure changes. Remove anytime. Works great with parallel shards.
Copy-paste install
npx sentinelqa upload

Stop sending screenshots. Share the failure.

Paste one link in Slack or Jira. Your team sees the exact frame, trace, logs, and artifacts instantly — without reproducing locally.

  • Faster handoffs between QA and engineering
  • Less “can you reproduce?”
  • Cleaner on-call triage
  • Fewer interruptions during releases
Collaboration preview
Shared: login.spec.ts → redirects after login
One link opens the trace, logs, and exact failure frame.
Slack + Jira friendly preview

Built for high-parallel Playwright pipelines.

  • Works with 10–200+ parallel CI jobs
  • Handles thousands of tests per run
  • Upload step runs in seconds
  • Zero impact on test execution time
Pipeline efficiency
Parallel shards: 10 → 200+
Failure grouping: automatic
Upload duration: seconds

Your artifacts never leave your cloud.

SentinelQA connects directly to your S3 bucket. Heavy artifacts stay in your infrastructure. We store only lightweight metadata to power the dashboard and sharing experience.

  • No storage markup
  • No vendor lock-in
  • Minimal permissions (IAM template available)
  • Built for security-conscious teams
We provide the lens. You keep control.
Security posture
Customer S3 bucket keeps artifacts
Metadata only in SentinelQA
Audit-friendly access model

Simple pricing for growing teams.

Start free. Upgrade when CI volume grows. Cancel anytime.

Starter
$0 / month
  • Monthly uploads: 50
  • Retention: 3 days
  • Share links: 24 hours
  • AI failure summary: Included
  • Users: Up to 3
Start Free
No credit card.
Professional
Recommended
$79 / month
  • Monthly uploads: 2,000
  • Retention: 30 days
  • Share links: 7 days
  • AI failure summary: Included
  • Users: Up to 10
  • Support: Priority
Business
$249 / month
  • Monthly uploads: 10,000
  • Retention: 90 days
  • Share links: Permanent
  • AI failure summary: Included
  • Users: Unlimited
  • Support: Dedicated Slack + SLA options
Remove anytime. No lock-in. Artifacts stay in your S3.

Frequently asked questions

Does SentinelQA work with GitHub Actions and GitLab CI?
Yes. SentinelQA supports common CI systems and parallel Playwright workflows.
Do artifacts leave our S3 bucket?
No. Heavy artifacts stay in your S3. SentinelQA stores lightweight metadata only.
How does the AI failure summary work?
When you open a failed test, SentinelQA analyzes logs and screenshots to generate a concise summary and suggested next step.
Does SentinelQA slow down CI?
No. The upload step runs after tests and doesn’t impact test execution time.
Can we remove SentinelQA easily?
Yes. Remove the CI step and you’re done. No lock-in.

Make CI failures boring again.

Setup in 2 minutes. No credit card. Remove anytime.