Comparison
Nijam vs Currents
Currents is a hosted dashboard for Playwright and Cypress test results and orchestration. Nijam reports your Playwright, pytest, and Vitest runs with the same clarity, and lets you keep every run and artifact in your own cloud on flat, predictable pricing.
Hosted vs your cloud
Two ways to hold your test data
Currents keeps your results and artifacts on its cloud and meters usage. Nijam can keep the very same data in your own Postgres and storage bucket.
Why Nijam
Own your data, and your bill
The two reasons teams move from a hosted dashboard to Nijam: keeping test data in their own cloud, and swapping metered usage for a flat, predictable price.
Your runs, your database
Point Nijam at your own Postgres and every run and project lives there. With Currents, results sit on their cloud; with Nijam, the data is already yours.
Your artifacts, your bucket
Traces, screenshots, and video stream straight to your own S3, Google Cloud Storage, or Azure bucket, so heavy artifacts never leave your infrastructure.
Flat, predictable pricing
Currents meters the number of test results you record. Turn on bring your own cloud and Nijam waives metering entirely, you pay a flat $20/month, whatever the volume.
Data residency, handled
Because your test data stays in infrastructure you control, residency and compliance stop being a vendor question and become a setting you own.
Beyond Playwright
First-class pytest and Vitest support, not just Playwright, so unit, component, and Python suites land in the same hosted history, flakiness, and failure views.
AI-ready via MCP
Point your agents at Nijam’s MCP server to ask about failures, flakiness, and history in plain language, right from your editor or CI.
Feature by feature
How they compare
Currents is genuinely strong at Cypress and orchestration, which is why those rows go its way. On data ownership and pricing, the story flips.
Pricing
Metered usage, or flat and yours
Currents bills on the test results you record. Nijam charges per report, and bring your own cloud replaces metering with a flat monthly base.
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-classAttempts, shards, and a run timeline, plus one click into the native Playwright trace viewer with screenshots and video attached.
pytest
First-classA lightweight pytest plugin streams results from every CI job. No traces required, and flaky tracking is included from the first run.
Vitest
First-classA first-class Vitest reporter turns unit and component runs into the same hosted history, flakiness scoring, and failure views as the rest.
FAQ