Gaffer is purpose-built for Playwright HTML reports. display.dev hosts Playwright reports and everything else — architecture diagrams, AI-generated dashboards, CI artifacts, internal docs — with company SSO at $49/month flat. One tool for every artifact your team produces.
| display.dev | Gaffer | |
|---|---|---|
| Playwright HTML reports | ✅ | ✅ |
| Any HTML file | ✅ | ❌ |
| Markdown rendering | ✅ | ❌ |
| AI-generated artifacts (Claude Code, Cursor) | ✅ | ❌ |
| CI/CD artifacts (coverage reports, build outputs) | ✅ | ❌ |
| Google SSO | ✅ | ✅ |
| Microsoft SSO | ✅ | Limited |
| MCP for Claude Desktop | ✅ | ❌ |
| Unlimited viewers | ✅ | Varies by plan |
| Flat pricing | ✅ ($49/mo) | Per-report or per-seat |
Gaffer solves one problem: sharing Playwright reports. If that's your only use case and you'll never need to share anything else, Gaffer works.
Most engineering teams publish more than test reports. Architecture proposals, data visualizations, sprint summaries, competitive analyses, internal dashboards — all of these are artifacts that need to live behind company auth. display.dev covers the whole problem at $49/month.
Gaffer was built specifically for Playwright reports. It understands the Playwright output format and shows them cleanly. For that specific job, it's a focused solution.
The limitation: every other artifact your team generates has no home. Claude Code produces architecture diagrams — no Gaffer path. Your data engineer exports a Plotly dashboard — no Gaffer path. Your PM creates a competitive analysis in Claude Desktop — no Gaffer path.
display.dev was built to be the publishing layer for everything. Any HTML file, any Markdown file, from any source, at any URL, behind your company's Google or Microsoft login. One workspace, one CLI, one price.
CLI (direct):
dsp publish ./playwright-report/ --name "playwright-run-$(date +%Y%m%d)"GitHub Actions (automated):
- name: Run Playwright tests
run: npx playwright test
- name: Publish report
run: dsp publish ./playwright-report/ --name "playwright-${{ github.run_id }}"
env:
DISPLAY_TOKEN: ${{ secrets.DISPLAY_TOKEN }}The URL is posted to the PR comment or Slack notification. QA leads, PMs, and stakeholders click it, authenticate with their company email once, and see the full interactive test report. No GitHub account required.
Your team's only internal sharing need is Playwright reports, and Gaffer's specific report rendering meets your requirements.
You publish Playwright reports and also publish anything else. You want one workspace, one CLI, and one flat price for every internal artifact. You want Google and Microsoft SSO included. You want MCP for non-technical users publishing from Claude Desktop.
Yes. Playwright generates self-contained HTML reports with all assets inlined. dsp publish ./playwright-report/ serves the index.html at the root URL with all assets resolved. The full interactive report — test results, screenshots, traces — renders exactly as Playwright generated it.
Yes. Add the display CLI to your CI environment and call dsp publish in your workflow. The URL can be written to a PR comment, a Slack message, or a test summary. See the CI artifacts guide.
Yes. You can grant access to specific external email addresses, or switch an artifact to public mode for anyone with the URL. The gate is per-artifact and configurable.
The free tier includes 50MB storage and unlimited viewers with one-time password authentication. Teams ($49/month) adds Google/Microsoft SSO, 25GB storage, and a custom domain.
Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Teams ($49/month flat).