> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testdino.com/llms.txt
> Use this file to discover all available pages before exploring further.

# TestDino Billing & Pricing Plans

> Compare TestDino plans, test usage limits, and billing cycles across the Free, Pro, Team, and Enterprise tiers.

TestDino bills based on monthly test executions.

## Quick Reference

| Topic | Description |
| :- | :- |
| [How Usage Is Measured](#how-usage-is-measured) | What counts as a test execution |
| [Choosing the Right Plan](#choosing-the-right-plan) | Estimate usage and pick a plan |
| [Billing Cycles](#billing-cycles) | Monthly, annual, and trial billing |
| [What Happens at the Limit](#what-happens-at-the-limit) | Behavior at the execution and project limits |
| [Upgrading and Downgrading](#upgrading-and-downgrading) | Changing plans mid-cycle |
| [Cancellation](#cancellation) | Ending your subscription |
| [Invoices and Payment](#invoices-and-payment) | Payment methods and invoice access |
| [FAQ](#faq) | Common billing questions |

## How Usage Is Measured

TestDino meters usage by **test executions**. One test execution is one test case (`test()` or `it()` block) that runs in a test run and reports a final result. A test counts **once per run, no matter how many times Playwright retries it**.

<Tabs>
  <Tab title="What counts">
    * Each test that reports a final result: passed, failed, or flaky
    * One execution per test per run, whatever the attempt count
    * The same test in a second browser or Playwright project (it is a separate test case)
    * Each new CI run of the same suite
  </Tab>

  <Tab title="What does not count">
    * Retry attempts. A test that fails twice and passes on the third attempt is 1 execution, counted flaky
    * Skipped tests (`it.skip`, `test.skip`) and interrupted tests
    * Attachments (screenshots, videos, traces) do not affect execution count
  </Tab>
</Tabs>

### Example

A test suite with 200 test cases running with `retries: 2`. 5 tests are skipped. 3 tests fail and retry twice each.

```text theme={null}
Tests reporting a result: 195 (200 total - 5 skipped)
Retry attempts:           not counted (6 extra attempts, 0 executions)
Attachments:              not counted
Total executions:         195
```

The 3 failing tests each run 3 times, and each still counts as 1 execution. Raising the Playwright `retries` setting does not increase your usage.

## Choosing the Right Plan

Estimate your monthly executions:

```text theme={null}
Monthly executions = (number of test cases) x (CI runs per month)
```

| Scenario | Tests | CI Frequency | Monthly Executions | Recommended Plan |
| :- | :- | :- | :- | :- |
| Solo developer | 100 | 2x/day | 6,000 | Pro |
| Small team | 200 | 3x/day | 18,000 | Team |
| Growing team | 400 | 3x/day | 36,000 | Team |
| Large team | 1,000+ | 5x/day | 150,000+ | Enterprise |

### Plan limits at a glance

| | Free | Pro | Team | Enterprise |
| :- | :- | :- | :- | :- |
| **Monthly price** | Free | \$49/mo | \$99/mo | Custom |
| **Annual price** | Free | \$39/mo, billed yearly | \$79/mo, billed yearly | Custom |
| **Monthly executions** | 5,000 | 10,000 | 40,000 | Custom |
| **Team members** | 1 | 3 | 30 | Custom |
| **Projects** | 1 | 3 | 5 | Custom |
| **Environments** | Not included | 3 | 10 | Custom |
| **Data retention** | 7 days | 90 days | 90 days | 90 days |
| **Artifact retention** | 7 days | 21 days | 21 days | 21 days |
| **Analytics retention** | 1 month | 3 months | 1 year | Custom |
| **Test case attachment storage** | Not included | 10 GB | 50 GB | Custom |

### Test management limits

Manual test cases, manual test runs, and exploratory sessions are part of [Test Management](/test-management/overview), which starts on the Pro plan.

| | Free | Pro | Team | Enterprise |
| :- | :- | :- | :- | :- |
| **Manual test cases** (per project) | Not included | 250 | 1,000 | Custom |
| **Manual test runs** (per project) | Not included | 10 | 100 | Custom |
| **Exploratory sessions** (per project) | Not included | 5 | 50 | Custom |
| **Test case version history** (per test case) | Not included | Latest 100 | Latest 250 | Unlimited |

<Tip>
  **Tip**

  Annual plans save approximately 20% compared to monthly billing.
</Tip>

## Billing Cycles

<Tabs>
  <Tab title="Monthly">
    Subscriptions renew on the same date each month. Usage resets at the start of each billing period.
  </Tab>

  <Tab title="Annual">
    Annual subscriptions are billed once per year at a discounted rate. Execution limits still reset every 30 days, on the same date each month, within the annual term.
  </Tab>

  <Tab title="Free Trial">
    New customers on paid plans receive a **14-day free trial** with full plan features. A payment method is required to start the trial. The subscription converts to a paid plan automatically when the trial ends. One trial per organization.
  </Tab>
</Tabs>

## What Happens at the Limit

When your organization reaches the monthly execution limit:

<Steps>
  <Step title="Test submissions blocked">
    New test results are blocked for the remainder of the billing period.
  </Step>

  <Step title="Existing data stays accessible">
    Dashboards, reports, and historical test data remain available.
  </Step>

  <Step title="Usage notifications">
    Email notifications are sent at 50%, 75%, 90%, and 100% usage thresholds.
  </Step>
</Steps>

To continue submitting tests, upgrade to a higher plan. The upgrade takes effect immediately.

### Project limit

Each plan includes a fixed number of projects. At the limit, **New Project** shows an upgrade prompt instead of creating one. Existing projects and their test data are unaffected.

If your organization holds more projects than your current plan includes, every project keeps working. You cannot create another until the count drops below the limit. Deleting a project frees its slot immediately.

## Upgrading and Downgrading

<Tabs>
  <Tab title="Upgrading">
    Upgrade at any time from **Billing & Usage > Change Plan**.

    * The new plan takes effect immediately
    * Usage limits and feature access update instantly
    * If upgrading from a trial, the trial ends and billing begins

    Plan order: Free > Pro > Team > Enterprise
  </Tab>

  <Tab title="Downgrading">
    Downgrade from **Billing & Usage > Change Plan**.

    * The downgrade takes effect at the end of the current billing period
    * Current plan features remain available until the period ends
    * If your current usage exceeds the lower plan's limits (members, projects), reduce usage before the downgrade activates

    <Warning>
      **Warning**

      Analytics history beyond the lower plan's retention window is deleted according to [data retention policies](/security/overview#data-retention). Upgrading later does not restore deleted data. Artifact and test data retention are the same on every plan, so a downgrade does not shorten them.
    </Warning>
  </Tab>
</Tabs>

## Cancellation

Cancel your subscription from **Billing & Usage > Cancel Subscription**.

* Cancellation can be immediate or at end of billing period
* The organization reverts to the Free plan after cancellation
* To resume service after cancellation, start a new subscription

## Invoices and Payment

### Payment methods

TestDino processes payments through Razorpay. Accepted methods:

| Method | |
| :- | :- |
| Credit and debit cards | Visa, Mastercard, RuPay |
| Net banking | All major banks |
| UPI | Google Pay, PhonePe, etc. |
| Digital wallets | Supported wallets via Razorpay |
| Bank transfer | Direct bank transfer |

No card data is stored by TestDino.

### Invoices

Access all invoices from **Billing & Usage > Invoices**. Each invoice shows the plan, billing period, amount, and payment status.

### Billing contacts

Configure who receives billing notifications in **Billing & Usage > Billing Emails**. Notifications include payment confirmations, failure alerts, invoice receipts, and usage threshold alerts.

<Note>
  **Note**

  Billing notifications are separate from operational notifications. Operational notifications (test failures, alerts) are sent to members with Admin role by default.
</Note>

## FAQ

<AccordionGroup>
  <Accordion title="How do I estimate which plan I need?">
    Multiply your test count by the number of CI runs per month. For example, 200 tests running 3 times per day is 18,000 executions/month, which fits the Team plan (40,000 limit).
  </Accordion>

  <Accordion title="Do retries and flaky tests inflate my usage?">
    No. A test counts once per run regardless of how many attempts it takes. A test that fails and retries twice is 1 execution. A flaky test (failed, then passed on retry) is also 1 execution. Changing the Playwright `retries` setting does not change your usage.
  </Accordion>

  <Accordion title="Do screenshots, videos, or traces affect billing?">
    No. Attachment volume does not affect execution count. Artifact storage is tracked separately and included in your plan.
  </Accordion>

  <Accordion title="What happens if I exceed my storage limit?">
    New artifacts are rejected when storage is full. Existing artifacts remain accessible. Storage is freed automatically when data expires per your plan's retention period.
  </Accordion>

  <Accordion title="Can I change plans in the middle of a billing cycle?">
    Yes. Upgrades take effect immediately with updated limits. Downgrades take effect at the end of the current billing period.
  </Accordion>

  <Accordion title="Is the free plan limited in features?">
    The Free plan includes flaky test detection, quality metrics, and a dashboard summary. It does not include failure categorization, error grouping, custom defect types, MCP, PR features, Slack/Jira integrations, or team management.
  </Accordion>

  <Accordion title="Can I switch between monthly and annual billing?">
    Contact **[support@testdino.com](mailto:support@testdino.com)** to switch billing cycles. Changes take effect at the end of the current billing period.
  </Accordion>

  <Accordion title="What happens if my payment fails?">
    TestDino retries the payment automatically. If the payment remains unpaid past the due date, the subscription is marked past due. Resolve payment issues in **Billing & Usage** to restore service.
  </Accordion>

  <Accordion title="Can I pause my subscription instead of cancelling?">
    Yes. Contact **[support@testdino.com](mailto:support@testdino.com)** to pause your subscription. Features are inactive while paused. Resume at any time.
  </Accordion>

  <Accordion title="Who can manage billing?">
    Owners and Administrators can manage subscriptions and payments. Billing Managers get read-only access to subscriptions, invoices, and payments.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Billing & Usage" icon="credit-card" href="/platform/billing-and-usage/overview">
    Monitor subscription status and current usage
  </Card>

  <Card title="Invoices" icon="file-invoice" href="/platform/billing-and-usage/invoices">
    View, download, and filter billing invoices
  </Card>

  <Card title="Data Retention" icon="clock" href="/security/overview#data-retention">
    How long test data and artifacts are retained
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.