Comparison

Nijam vs TestDino

TestDino is a hosted, Playwright-only reporting cloud, metered on test executions and tiered by seats, projects, and how long your history survives. Nijam reports Playwright, pytest, and Vitest with the same clarity, keeps projects unlimited, and lets every run and artifact live in your own cloud.

One framework vs three

The same run, two ceilings

TestDino reads Playwright and meters every execution it sees. Nijam reads three frameworks and can put the whole record in infrastructure you own.

Why Nijam

Wider coverage, and no cap on your team

The three reasons teams move: suites TestDino cannot read, data they would rather keep, and plan limits they would rather not think about.

More than Playwright

TestDino is a Playwright-only cloud. Nijam is first-class for Playwright, pytest, and Vitest, so your E2E, Python, and unit suites land in one history with one flakiness view.

Your runs, your database

Point Nijam at your own Postgres and every run and project lives there. With TestDino, results sit on their cloud; with Nijam, the data is already yours.

Your bucket, not an upsell

TestDino puts bring your own storage behind an Enterprise contract. Nijam streams traces, screenshots, and video straight to your own S3, Google Cloud Storage, or Azure bucket on the $20 Pro plan.

Executions add up, credits do not

TestDino counts every test execution, so three browsers and a retry turn one test into four. Nijam counts one credit per Playwright test report, and bring your own cloud drops metering entirely for a flat $20/month.

No seat or project math

TestDino gates members and projects by tier: 1 and 1 on free, 3 and 3 on Pro. Nijam gives every plan unlimited projects, and Pro adds unlimited members, so nobody is left outside the dashboard.

History on your terms

Hosted retention on both products is a plan setting, 60 days on TestDino Pro, 90 on Nijam Pro. With bring your own cloud the window disappears: the rows are in your database for as long as you keep them.

Feature by feature

How they compare

TestDino is a good Playwright product, which is why the live-run, flake-classification, and tracker rows go its way. On frameworks, ownership, and plan limits, the story flips.

Capability
TestDino
Nijam
Frameworks
Playwright
First-class, the whole product
First-class: attempts, shards, timeline
pytest
Not supported
First-class plugin
Vitest
Not supported
First-class reporter
One home for every suite
Playwright runs only
E2E, Python, and unit runs side by side
Data ownership (bring your own cloud)
Your own database
Results stored on TestDino
Runs live in your own Postgres
Your own storage
Bring your own bucket on Enterprise
Traces & video in your S3/GCS/Azure, on Pro
Data residency & compliance
Their infrastructure and regions
Data never leaves your cloud
Certifications
ISO 27001 and SOC 2 Type II
None yet, but BYOC keeps data with you
Pricing & plan limits
Model
Tiers metered on test executions
Per report, with a flat BYOC option
What counts as usage
Every browser and every retry
1 credit = 1 Playwright test (100 pytest/Vitest)
Team members
1 free, 3 on Pro, 30 on Team
3 free, unlimited on Pro
Projects
1 free, 3 on Pro, 5 on Team
Unlimited on every plan
History retention
14 days free, 60 on Pro, 365 on Team
7 days free, 90 on Pro, unlimited with BYOC
Single sign-on (SSO/OIDC)
Enterprise only
Included on Pro, $20/mo
Reporting & insight
Playwright trace viewer
Opens traces in the browser
Opens the native Playwright trace
Flaky detection
Retry analysis with root-cause buckets
Auto-detected and ranked per test
Live view of a running suite
Real-time monitoring across shards
The report lands when the run finishes
AI / MCP access
MCP server and AI PR summaries, Pro and up
MCP server for agents
Workflow
GitHub pull requests
PR gates and AI summaries
PR check plus a results comment
GitLab merge requests
GitLab CI integration
Runs report from GitLab CI, no MR comments
Chat alerts
Slack
Slack, per project and per event
Issue trackers
Jira, Linear, Azure DevOps, Asana, monday
Slack and GitHub today
First-class
Partial or gated
Not really

Pricing

Executions and seats, or credits and your cloud

TestDino prices tiers around executions, members, projects, and retention. Nijam charges per report, keeps members unlimited on Pro, and drops metering when the data is yours.

TestDino
Metered executions, fully hosted
Free: 5,000 executions, 1 member, 1 project, 14-day history
Pro $39/mo: 10,000 executions, 3 members, 3 projects
Team $79/mo: 40,000 executions, 30 members, 5 projects
Bring your own bucket and SSO: Enterprise only
Nijam
Per report, or flat with your own cloud
Free: 1,000 credits, up to 3 members, unlimited projects
Pro $20/mo: 10,000 credits, then $0.001 per extra (early bird)
Unlimited members and SSO/OIDC on Pro, no per-seat pricing
Bring your own cloud: flat $20/mo, unmetered, unlimited retention

Playwright · pytest · Vitest

First-class for the frameworks you automate

Real reporters and plugins for the three we focus on, so results flow in without an API mapping to build.

Playwright

First-class

Attempts, shards, and a run timeline, plus one click into the native Playwright trace viewer with screenshots and video attached.

pytest

First-class

A lightweight pytest plugin streams results from every CI job. No traces required, and flaky tracking is included from the first run.

Vitest

First-class

A first-class Vitest reporter turns unit and component runs into the same hosted history, flakiness scoring, and failure views as the rest.

FAQ

Questions teams ask us

Report every suite, not just Playwright

Bring your Playwright, pytest, and Vitest runs into one dashboard with flakiness, retries, and traces, and keep every run and artifact in your own Postgres and bucket when you want to.

Free while you connect your first project · works with GitHub Actions, Jenkins, GitLab CI & CircleCI