Currents Documentation
Currents.devGitHubChangelog
  • Getting Started
    • What is Currents?
    • Playwright
      • Playwright: Quick Start
      • Troubleshooting Playwright
    • Cypress
      • Your First Cypress Run
      • Integrating with Cypress
        • Compatibility
        • Alternative Cypress Binaries
      • Troubleshooting Cypress
    • Jest
      • Your First Jest Run
      • Detox + Jest
      • Troubleshooting Jest
    • Others
    • CI Setup
      • GitHub Actions
        • Cypress - GitHub Actions
        • Playwright - GitHub Actions
        • Jest - GitHub Actions
        • Node.js - GitHub Actions
        • Commit data for GitHub Actions
        • Custom Docker runners
        • Named Runners
      • GitLab
        • Cypress - GitLab CI/CD
        • Playwright - GitLab CI/CD
        • Custom Docker runners
      • Jenkins
        • Cypress - Jenkins
        • Playwright - Jenkins
      • CircleCI
        • Cypress - CircleCI
        • Playwright - CircleCI
      • Bitbucket
        • Cypress - Bitbucket Pipelines
      • Azure DevOps
        • Cypress - Azure DevOps
        • Playwright - Azure DevOps
      • AWS Code Build
        • Cypress - AWS Code Build
        • Playwright - AWS Code Build
      • NX
        • Playwright - NX
        • Cypress - NX
  • Guides
    • Record Key
    • CI Build ID
    • Reporting
      • Reporting Strategy
      • Reporting in CI
      • Step-Level Reporting
    • CI Optimization
      • Playwright Parallelization
      • Orchestration Setup
      • Fully Parallel Mode
      • Re-run Only Failed Tests
      • Cloud Spot Instances
      • Failing Fast
      • Load Balancing
    • Code Coverage
      • Code Coverage for Playwright
      • Code Coverage for Cypress
    • Currents Actions
      • Setup Currents Actions
      • Using Currents Actions
      • Reference
        • Conditions
        • Actions
    • Playwright Component Testing
    • Playwright Visual Testing
    • Playwright Annotations
    • Playwright Tags
    • MCP Server
  • Dashboard
    • Projects
      • Projects Summary view
      • Project Settings
      • Archive and Unarchive Projects
    • Runs
      • Run Status
      • Run Details
      • Commit Information
      • Tags
      • Run Timeouts
      • Cancelling Runs
      • Deleting Runs
      • Run Progress
    • Tests
      • Spec File Status
      • Test Status
      • Flaky Tests
      • Test History
    • Test Suite Explorer
      • Test Explorer
      • Spec Files Explorer
      • Errors Explorer
      • Reference
  • Automated Reports
  • Insights and Analytics
  • Administration
    • Email Domain Based Access
    • SSO SAML2.0
      • SAML2.0 Configuration
      • SCIM User Provisioning
      • IdP-initiated Sessions
      • JumpCloud
        • JumpCloud User provisioning
      • Okta
        • Okta User provisioning
      • Troubleshooting SSO
    • Billing & Usage
  • Billing and Pricing
  • Resources
    • Reporters
      • cypress-cloud
        • Batched Orchestration
        • Migration to Cypress@13
      • @currents/cli
      • @currents/playwright
        • Configuration
        • pwc
        • pwc-p (orchestration)
        • Playwright Fixtures
      • @currents/jest
      • @currents/node-test-reporter
      • @currents/cmd
        • currents api
        • currents upload
        • currents cache
        • currents convert
      • Data Format Reference
    • Integrations
      • GitHub
        • GitHub App
        • GitHub OAuth
      • GitLab
      • Slack
      • Microsoft Teams
      • HTTP Webhooks
      • Bitbucket
    • API
      • Introduction
      • Authentication
      • API Keys
      • Errors
      • Pagination
      • API Resources
        • Instances
        • Runs
        • Projects
        • Spec Files
        • Test Signature
        • Test Results
    • Data Privacy
      • Access to Customer Data
      • Data Retention
      • Cloud Endpoints
    • Support
Powered by GitBook
On this page
  • Pricing Components
  • Usage Estimation
  • Subscription Types
  • Extra Seats
  • Extra Usage
  • Enterprise Plans
  • FAQ

Was this helpful?

Billing and Pricing

How Currents Billing and Pricing Works

PreviousBilling & UsageNextReporters

Last updated 21 days ago

Was this helpful?

Currents has a flexible subscription-based billing model. It is designed to allow different types of customers to find a convenient plan that matches their needs.

All the plans incorporate volume discounts - as your usage increases, the cost per unit decreases.

Pricing Components

The plans are based on the number of test recordings and the number of team members.

Test Recordings

Test recording is a result of running a . It includes:

  • Execution details - test outcome, timing data, error details and metadata for all the included attempts;

  • Attachments - screenshots, videos, trace files, performance reports and any other attachment.

recordings do not count for billing purpose. Number of attempts or the attachments volume for not affect billing.

Team Members

Every account associated with your organization is considered a team member for billing purposes. Each plan has a predetermined limit of seats (Team Members). You can purchase additional seats, up to 30 seats total, using Billing & Usage section.

If you need more seats please contact us at .

Usage Estimation

For a ballpark estimate, count the number of it and test statements in your source code and multiply by average number of CI runs.

Test Recording Volume = it or test statements x CI runs per month

Subscription Types

Monthly Subscriptions

You pay a monthly fee for the selected plan. For example consider a 10K plan that costs $49:

  • we charge a $49 prepayment for the first 10K test recordings;

  • we charge an Extra Usage fee for every additional 1K tests (or portion of it) at the end of usage cycle.

The usage cycle resets each month when you renew the subscription.

Month
Charge
End-of-month usage

May 12

$49 prepayment for June

9K

June 12

$49 prepayment for June

12K

July 12

$49 prepayment for July +$12 extra usage fee for the previous month

...and so on

Annual Subscriptions

You pay an annual fee (with a discount) for the selected plan. For example consider a 10K plan that costs $539/year:

  • we charge a $539 prepayment for the 10K test recordings available each month;

  • if you record more than 10K test recordings in any month, we will charge the Extra Usage fee for every additional 1K tests (or portion of it) at the end of usage cycle.

Month
Charge
End-of-month usage

May 12, 2024

$539 prepayment for the year

9K

June 12

-

12K

July 12

$12 extra usage fee for the previous month

...and so on

...

May 12, 2025

extra usage fees, if any

end of contract

The usage cycle resets each month on the day of subscription creation.

Extra Seats

Extra Usage

We will charge the Extra Usage fee for every additional 1K tests (or portion of it) at the end of usage cycle. The price for the extra usage unit depends on the plan and varies.

When your organization start incurring Extra Usage fee Currents sends a period email notification to organization owners with an alert. Additionally, you can set up usage warning in Billing & Usage section of the dashboard.

Depending on the Usage and Billing Cycle (see below) and payment method, we will charge the fee on Monthly, Quarterly or Annual Basis.

We recommend switching to a higher-tier plan to avoid incurring extra usage fees.

Enterprise Plans

Enterprise Plans allows customizing the terms and cadence of billing and usage cycle, in addition to premium support, unlimited seats and other contract customizations.

Usage Cycle vs Billing Cycle

  • Usage Cycle - defines when usage counter resets. For example:

    • Monthly Usage Cycle resets every month, usually on subscription start day.

    • Annual Usage Cycle resets every year, usually on a contract renewal.

  • Billing Cycle - defines how often we invoice or charge customers: monthly, annually or every couple of years. Usually Billing Cycle is bound to contracts renewal date.

You can mix different types of Usage Cycle and Billing Cycle based on your needs. For example:

Usage Cycle
Billing Cycle
Description

Monthly

Monthly

Standard month-to-month subscriptions. Not available for Enterprise Plans.

Monthly

Annual

You pay a discounted price in advance for the whole year, usage resets every month.

Annual

Annual

You pay in advance for the whole year and get a relatively big package of test records, the usage cycle resets at the end of the year. This option matches companies with varying usage patterns.

Annual

Monthly

Not supported.

We can occasionally send an out-of-cycle invoices for Extra Usage or mid-term upgrades

Tiered Contract

We offer tiered contracts for better estimating the potential costs and reducing the paperwork overhead.

With a tiered contract, we will activate a different tier as soon as you reach the previous tier's threshold. Each next tier has an embedded discount, you will know in advance the max potential amount you pay.

For example, consider a 3-tier contract - the initial payment is $10,000 for 1MM test records. The next-tier charges kick in only if and after you exceed the previous tier threshold.

Tier
Threshold
Charge

Tier 1

1MM test records

$10,000 on subscription creation

Tier 2

1.5MM test record

$4,000 after exceeded 1MM test records

Tier 3

2MM test records

$3,000 after exceeding 1.5MM test records

FAQ

What is a Test Result / Test Recording?

Test results is ait() or test() statement that was executed by a test runner and was sent to Currents, including all the attempts and artifacts.

What Test Recordings are included for Billed Usage?

recordings do not count for billing purpose, we only count passed or failed test results.

What happens if I exceed the plan limits?

We will charge a small amount of Extra Usage fees for every 1K extra recording or portion of it. The exact amount depends on your plan and varies.

Are there limits on the number of team members I can have?

What kind of support is included in each tier?

  • Non-enterpise plans: email + in-app chat during business hours

  • Enterprise plans: 24/7 support, direct access to Slack and the product-engineering team

Is there a free plan?

Currents doesn't have a free plan.

How can I track my usage?

Use Billing & Usage section to setup usage warnings. Additionally, Currents will send an automated emails when you start incurring Extra Usage fees. Our Customer Success team will reach out to your organization admins if you consistently exceed your plan limits or incur significant charges with a recommendation to update your plan.

Do you charge for data storage?

No, we don't. We periodically delete the data according to Data Retention policy.

Do you discount bigger plans?

Yes, all of our plans have an embedded volume discount - the more you use the lower is the price per unit. For example:

  • 10K plan PPU is $4.9 / 1K

  • 150K plan PPU is 3.32 / 1K

Our custom plan have similar structure but are adjusted per-customer.

Are there discounts for annual or multi-year commitments?

What payment methods do you accept?

Credit Card payments via Stripe. SWIFT and US ACH transfers. We are a registered vendor on popular procurement platforms like Airbase, Coupa, ZipHQ, Bill.com.

To have a more accurate estimation, create a free trial account and start sending the test results, after a couple of days use the Billing & Usage section to review your usage. Contact our team to extend your trial .

Each plan has a predetermined limit of seats (Team Members). You can purchase additional seats, up to 30 seats total, using Billing & Usage section. If you need more seats please contact us at .

Up to 30 team members for non-enterprise plans. No limit for enterprise plans. If you need more seats please contact us at .

Yes! We offer discounts for customers who choose to commit to annual or multi-year plans. This not only provides savings but also ensures budget predictability. Contact us at for customized offers.

hello@currents.dev
hello@currents.dev
hello@currents.dev
hello@currents.dev
hello@currents.dev