> For the complete documentation index, see [llms.txt](https://docs.testvibe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testvibe.com/pricing.md).

# Pricing

TestVibe pricing is based on the plan attached to the current workspace and the TestVibe credits used by generation and test runs. Credits cover both the AI tokens used during generation and the cloud test session time used by runs. Plans primarily differ by monthly price and the number of included credits. Plan, credits, and storage all belong to the workspace, so each workspace is billed separately.

All prices are in USD. The checkout price shown during billing is the final price before payment.

## Plans

| Plan       | Best for                                               |
| ---------- | ------------------------------------------------------ |
| Free       | Trying TestVibe with a small monthly credit allowance. |
| Starter    | Teams running regular generation and regression work.  |
| Pro        | Higher-volume teams that want more included credits.   |
| Enterprise | Workspaces with high volume or custom requirements.    |

Current prices and included credit amounts are shown on the plan cards in **Settings > Billing**. Yearly billing is 10% cheaper than monthly, and the year's credits are granted up front.

## What Every Plan Includes

Every plan gives you the core TestVibe experience:

* Cloud-hosted projects.
* AI-assisted feature and Playwright test generation.
* Test execution in isolated cloud test sessions.
* Result review with screenshots, videos, traces, console output, and network details when the run produces them.
* Billing visibility from **Settings > Billing**, with credit consumption broken down in **Settings > Credit Usage** and storage in **Settings > Storage**.

## Credits At A Glance

TestVibe meters usage in credits. AI generation consumes credits based on the AI tokens it uses, and test runs consume credits based on cloud test session time.

Included monthly plan credits are used first, then purchased credit packs. On the Free plan, work stops once the balance reaches zero. On Pro and Enterprise plans, overage past the balance is tracked and billed at the end of the period.

## Credit Packs

Paid plans can buy one-time credit packs. Purchased credits are consumed after the plan's included credits and never expire. Pack sizes and prices are shown in the **Credit** card in **Settings > Billing**.

## Where To Manage Billing

Open **Settings > Billing** to:

* Review the current plan for this workspace.
* Compare available plans.
* Upgrade or schedule a downgrade.
* Cancel a scheduled plan change.
* Purchase credit packs.

For details about what credits cover, see [Credits and what they cover](/pricing/billable-minutes-and-credit.md). For plan-change behavior, see [Manage billing](/pricing/manage-billing.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.testvibe.com/pricing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
