{
  "doc": {
    "id": "cloud/account-management/billing-and-usage",
    "title": "Billing & usage in Cypress Cloud",
    "description": "Understand your Cypress Cloud plan and the Billing & Usage page: how test results and AI prompts are metered, what happens when you reach your limit, how to set usage notifications, manage your payment method and billing email, download invoices, and request a free Open Source plan.",
    "section": "cloud",
    "source_path": "/llm/markdown/cloud/account-management/billing-and-usage.md",
    "version": "fbc9225067c51c52ee13224e3b702cf8a025ec12",
    "updated_at": "2026-08-14T12:36:26.878Z",
    "headings": [
      {
        "id": "cloud/account-management/billing-and-usage#billing-usage",
        "text": "Billing & Usage",
        "level": 1
      },
      {
        "id": "cloud/account-management/billing-and-usage#plan-overview",
        "text": "Plan overview",
        "level": 2
      },
      {
        "id": "cloud/account-management/billing-and-usage#cloud-test-results",
        "text": "Cloud test results",
        "level": 2
      },
      {
        "id": "cloud/account-management/billing-and-usage#usage-over-time",
        "text": "Usage over time",
        "level": 3
      },
      {
        "id": "cloud/account-management/billing-and-usage#usage-by-project",
        "text": "Usage by project",
        "level": 3
      },
      {
        "id": "cloud/account-management/billing-and-usage#prompt-executions",
        "text": "Prompt executions",
        "level": 2
      },
      {
        "id": "cloud/account-management/billing-and-usage#usage-over-time",
        "text": "Usage over time",
        "level": 3
      },
      {
        "id": "cloud/account-management/billing-and-usage#usage-by-project",
        "text": "Usage by project",
        "level": 3
      },
      {
        "id": "cloud/account-management/billing-and-usage#usage-notification",
        "text": "Usage notification",
        "level": 2
      },
      {
        "id": "cloud/account-management/billing-and-usage#payment-method-and-billing-email",
        "text": "Payment method and billing email",
        "level": 2
      },
      {
        "id": "cloud/account-management/billing-and-usage#invoices",
        "text": "Invoices",
        "level": 2
      },
      {
        "id": "cloud/account-management/billing-and-usage#open-source-plan",
        "text": "Open Source Plan",
        "level": 2
      },
      {
        "id": "cloud/account-management/billing-and-usage#requesting-oss-plan-for-an-organization",
        "text": "Requesting OSS plan for an Organization",
        "level": 3
      },
      {
        "id": "cloud/account-management/billing-and-usage#common-billing-questions",
        "text": "Common billing questions",
        "level": 2
      },
      {
        "id": "cloud/account-management/billing-and-usage#see-also",
        "text": "See also",
        "level": 2
      }
    ]
  },
  "chunks": [
    {
      "id": "cloud/account-management/billing-and-usage#plan-overview",
      "doc_id": "cloud/account-management/billing-and-usage",
      "heading": "Plan overview",
      "heading_level": 2,
      "content_markdown": "## Plan overview\n\nThe card at the top of the page summarizes your subscription at a glance, so you always know what you are entitled to and when it renews:\n\n*   **Current plan:** your plan tier and price.\n*   **Included test results:** the number of [test results](#Cloud-test-results) included in your plan (Team, Business, etc.) each billing period.\n*   **Bundled test results:** the number of extra test results you have purchased up front, mid-term, to extend your allowance before you rely on on-demand pricing.\n*   **On-demand test results:** the per-unit price for any test results recorded beyond your included and bundled amounts, so you can anticipate these costs before they appear on an invoice.\n*   **cy.prompt executions:** how many [cy.prompt](/llm/markdown/api/commands/prompt.md) executions your plan allows and how many you have used.\n*   **Users:** how many of your plan's [user](/llm/markdown/cloud/account-management/users.md) seats are in use.\n*   **Data Retention:** how long your recorded runs and their artifacts stay available in Cypress Cloud.\n*   **Renews on:** the date your plan renews and your usage cycle resets.\n\nUse the **Subscribe**, **Change plan**, or **Contact us** buttons to subscribe, upgrade, or ask questions about your plan.\n",
      "section": "cloud",
      "anchors": [
        "plan-overview"
      ],
      "path": "/llm/json/chunked/cloud/account-management/billing-and-usage.json",
      "token_estimate": 251
    },
    {
      "id": "cloud/account-management/billing-and-usage#cloud-test-results",
      "doc_id": "cloud/account-management/billing-and-usage",
      "heading": "Cloud test results",
      "heading_level": 2,
      "content_markdown": "## Cloud test results\n\nA **test result** is each passed or failed test recorded when you run [`cypress run --record`](/llm/markdown/app/references/command-line.md#cypress-run); pending and skipped tests are not counted (see [what counts as a test result](/llm/markdown/cloud/faq.md#What-counts-as-a-test-result)). It is the core unit Cypress Cloud meters, and it is what unlocks everything Cloud does for your team. In exchange for recording, each run becomes debuggable and measurable: you get [Test Replay](/llm/markdown/cloud/features/test-replay.md) to reproduce failures exactly as they happened in CI, [Flaky Test Management](/llm/markdown/cloud/features/flaky-test-management.md) to catch unreliable tests, [analytics](/llm/markdown/cloud/features/analytics/overview.md) to track quality over time, and [Smart Orchestration](/llm/markdown/cloud/features/smart-orchestration/overview.md) to run specs in parallel and cut CI time. Test results are the meter behind all of that value.\n\nCypress Cloud counts test results across three tiers, consumed in this order:\n\n*   **Included:** the test results included in your plan (Team, Business, etc.) for each billing period.\n*   **Bundled:** extra test results you purchase up front, mid-term, to top up your allowance before any on-demand usage begins.\n*   **On-demand:** unexpected, non-prepaid test results recorded beyond your included and bundled amounts, generally billed at a higher per-unit price point.\n\nThe **Test results** card highlights the number of used and included test results in your current billing period. It also shows how many **bundled** test results you have purchased and used, and any **on-demand** test results recorded beyond those amounts, if applicable.\n\nKeeping an eye on this card matters because of what happens once you exhaust your included and bundled test results. If your plan does not allow on-demand usage, recording keeps working but [parallelization is disabled and new results are hidden from the dashboard](/llm/markdown/cloud/faq.md#What-happens-once-I-reach-the-test-results-limit) until you upgrade or the cycle resets:\n\n| Once included and bundled test results are used | Behavior |\n| --- | --- |\n| Recording (`--record`) | Still runs |\n| On-demand test results | Recorded at a higher per-unit price, where your plan allows |\n| Parallelization | Disabled if on-demand usage is not available |\n| New results in dashboard | Hidden until upgrade or cycle reset if on-demand is not available |\n| Usage cycle | Resets each billing period (monthly or annual) |\n\nReviewing usage here lets you [upgrade](https://www.cypress.io/pricing) ahead of time and avoid any interruption.\n\n### Usage over time\n\nClick the **Usage details** button in order to view graphs of your test results usage.\n\nThe **Detailed** tab shows your usage over time during the selected billing period, broken down by **included**, **bundled**, and **on-demand** test results. Use it to spot trends: a steadily rising line tells you when it's time to move to a larger plan, while a sudden spike can reveal a misconfigured pipeline recording far more than you expected. A growing share of on-demand usage is a signal to consider more included or bundled test results, which are typically more cost-effective.\n\n### Usage by project\n\nThe **By project** tab shows your usage per project during the selected billing period, so you can see which projects consume the most of your plan and attribute cost back to the teams that drive it. Click the **CSV** button to download your results usage for chargeback reporting or further analysis.\n",
      "section": "cloud",
      "anchors": [
        "cloud-test-results"
      ],
      "path": "/llm/json/chunked/cloud/account-management/billing-and-usage.json",
      "token_estimate": 692
    },
    {
      "id": "cloud/account-management/billing-and-usage#usage-over-time",
      "doc_id": "cloud/account-management/billing-and-usage",
      "heading": "Usage over time",
      "heading_level": 3,
      "content_markdown": "### Usage over time\n\nClick the **Usage details** button in order to view graphs of your test results usage.\n\nThe **Detailed** tab shows your usage over time during the selected billing period, broken down by **included**, **bundled**, and **on-demand** test results. Use it to spot trends: a steadily rising line tells you when it's time to move to a larger plan, while a sudden spike can reveal a misconfigured pipeline recording far more than you expected. A growing share of on-demand usage is a signal to consider more included or bundled test results, which are typically more cost-effective.\n",
      "section": "cloud",
      "anchors": [
        "usage-over-time"
      ],
      "path": "/llm/json/chunked/cloud/account-management/billing-and-usage.json",
      "token_estimate": 131
    },
    {
      "id": "cloud/account-management/billing-and-usage#usage-by-project",
      "doc_id": "cloud/account-management/billing-and-usage",
      "heading": "Usage by project",
      "heading_level": 3,
      "content_markdown": "### Usage by project\n\nThe **By project** tab shows your usage per project during the selected billing period, so you can see which projects consume the most of your plan and attribute cost back to the teams that drive it. Click the **CSV** button to download your results usage for chargeback reporting or further analysis.\n",
      "section": "cloud",
      "anchors": [
        "usage-by-project"
      ],
      "path": "/llm/json/chunked/cloud/account-management/billing-and-usage.json",
      "token_estimate": 73
    },
    {
      "id": "cloud/account-management/billing-and-usage#prompt-executions",
      "doc_id": "cloud/account-management/billing-and-usage",
      "heading": "Prompt executions",
      "heading_level": 2,
      "content_markdown": "## Prompt executions\n\nThe **AI Prompts** card tracks [cy.prompt](/llm/markdown/api/commands/prompt.md) usage in your organization for the current billing period, both the number of prompt executions and the number of steps those prompts ran. `cy.prompt` is the AI capability that turns natural-language steps into executable Cypress commands and can [self-heal](/llm/markdown/api/commands/prompt.md) tests when selectors change. Its value is in the manual work it removes: faster test authoring from plain English, and fewer broken tests to fix when your UI evolves. This card shows you how broadly that value is being adopted across your organization.\n\nThe \"Prompt execution\" information conveys how many times the [cy.prompt](/llm/markdown/api/commands/prompt.md) command has been executed in your organization, either on developer machines or in CI. Each [cy.prompt](/llm/markdown/api/commands/prompt.md) command can define more than one step to be executed. We also break down the number of commands that took place in \"Open mode\" or in \"Run mode\". Together this tells you not just how much AI is being used, but _where_: whether developers are authoring tests interactively, or whether self-healing is running in CI, so you can see how your team is putting AI to work.\n\nFor limit behavior, the grace period, and what happens when you exceed your allowance, see [cy.prompt](/llm/markdown/cloud/faq.md#cyprompt) in the Cloud FAQ.\n\n### Usage over time\n\nClick the **Usage details** button in order to view graphs of your cy.prompt AI usage.\n\nThe **Detailed** tab shows your prompt usage over time during the selected billing period, so you can watch AI adoption grow as more of your team picks it up.\n\n### Usage by project\n\nThe **By project** tab shows your prompt usage per project during the selected billing period, surfacing which projects are getting the most out of AI-assisted testing. Click the **CSV** button to download your AI prompt usage for further analysis.\n",
      "section": "cloud",
      "anchors": [
        "prompt-executions"
      ],
      "path": "/llm/json/chunked/cloud/account-management/billing-and-usage.json",
      "token_estimate": 393
    },
    {
      "id": "cloud/account-management/billing-and-usage#usage-over-time",
      "doc_id": "cloud/account-management/billing-and-usage",
      "heading": "Usage over time",
      "heading_level": 3,
      "content_markdown": "### Usage over time\n\nClick the **Usage details** button in order to view graphs of your cy.prompt AI usage.\n\nThe **Detailed** tab shows your prompt usage over time during the selected billing period, so you can watch AI adoption grow as more of your team picks it up.\n",
      "section": "cloud",
      "anchors": [
        "usage-over-time"
      ],
      "path": "/llm/json/chunked/cloud/account-management/billing-and-usage.json",
      "token_estimate": 64
    },
    {
      "id": "cloud/account-management/billing-and-usage#usage-by-project",
      "doc_id": "cloud/account-management/billing-and-usage",
      "heading": "Usage by project",
      "heading_level": 3,
      "content_markdown": "### Usage by project\n\nThe **By project** tab shows your prompt usage per project during the selected billing period, surfacing which projects are getting the most out of AI-assisted testing. Click the **CSV** button to download your AI prompt usage for further analysis.\n",
      "section": "cloud",
      "anchors": [
        "usage-by-project"
      ],
      "path": "/llm/json/chunked/cloud/account-management/billing-and-usage.json",
      "token_estimate": 57
    },
    {
      "id": "cloud/account-management/billing-and-usage#usage-notification",
      "doc_id": "cloud/account-management/billing-and-usage",
      "heading": "Usage notification",
      "heading_level": 2,
      "content_markdown": "## Usage notification\n\nA **usage notification** emails your organization's owner and admins when your recorded test results reach a number you choose in the current billing cycle. Instead of remembering to check this page, you get told when you are approaching your limit, so you can upgrade or adjust before [parallelization is disabled and new results are hidden](/llm/markdown/cloud/faq.md#What-happens-once-I-reach-the-test-results-limit). That early warning is the difference between a planned upgrade and a surprise interruption to your CI feedback, and it keeps owners and admins aware of usage trends without anyone having to monitor the dashboard manually.\n\nFrom the **Usage notification** card, click **Create notification**\n\nChoose the threshold that triggers the email:\n\n*   **Included with your plan:** notify when you reach the test results already included in your plan, so you hear about it right as you hit the ceiling.\n*   **Custom:** notify at a number you set, which is useful for getting an earlier heads-up while you still have room to act.\n\nClick **Save notification** to enable it. The notification email is sent to the organization's owner and admins.\n",
      "section": "cloud",
      "anchors": [
        "usage-notification"
      ],
      "path": "/llm/json/chunked/cloud/account-management/billing-and-usage.json",
      "token_estimate": 236
    },
    {
      "id": "cloud/account-management/billing-and-usage#payment-method-and-billing-email",
      "doc_id": "cloud/account-management/billing-and-usage",
      "heading": "Payment method and billing email",
      "heading_level": 2,
      "content_markdown": "## Payment method and billing email\n\nThe **Payment method information** card shows the credit card on file and the email address your invoices are sent to, and lets an **Owner** or **Admin** keep both current without contacting support. Keeping these accurate means uninterrupted service and invoices that reach the right inbox, so a renewal never fails because of an expired card and finance always receives the bill.\n\n*   **Credit card:** Click **Change** to update the card on file, for example when it expires or you switch to a corporate card.\n*   **Invoices sent to:** this is the billing email address. Click **Change** to open the **Change billing email** dialog, enter the new address, and click **Update billing email**. Invoices and billing-related notifications are sent here, so point it at the inbox your finance or accounting team monitors.\n\nTo update other billing details, such as your billing address or company name, contact [billing@cypress.io](mailto:billing@cypress.io).\n",
      "section": "cloud",
      "anchors": [
        "payment-method-and-billing-email"
      ],
      "path": "/llm/json/chunked/cloud/account-management/billing-and-usage.json",
      "token_estimate": 203
    },
    {
      "id": "cloud/account-management/billing-and-usage#invoices",
      "doc_id": "cloud/account-management/billing-and-usage",
      "heading": "Invoices",
      "heading_level": 2,
      "content_markdown": "## Invoices\n\nEvery invoice for your organization is listed at the bottom of the **Billing & Usage** page, giving owners and admins self-serve access to a complete billing history for expense reporting, audits, and accounting, without having to request copies from support. Each row shows the invoice **status** (such as _Paid_ and the date it was paid), the invoice **ID**, the **invoice date**, the **amount invoiced**, any **credits** applied, and the **amount paid**.\n\nTo download a past invoice, click **Download** on its row. This gives you a PDF you can forward to finance or attach to an expense report at any time, including for older billing periods.\n",
      "section": "cloud",
      "anchors": [
        "invoices"
      ],
      "path": "/llm/json/chunked/cloud/account-management/billing-and-usage.json",
      "token_estimate": 143
    },
    {
      "id": "cloud/account-management/billing-and-usage#open-source-plan",
      "doc_id": "cloud/account-management/billing-and-usage",
      "heading": "Open Source Plan",
      "heading_level": 2,
      "content_markdown": "## Open Source Plan\n\nThe Open Source Software (OSS) plan is a free upgrade for qualifying public, non-commercial projects. It includes 5 free users, 100k test results/month, [parallelization with load balancing](/llm/markdown/cloud/features/smart-orchestration/parallelization.md) to keep CI fast as your suite grows, and access to numerous [integrations](/llm/markdown/cloud/integrations/github.md), so open source maintainers get the orchestration and debugging power that helps commercial teams ship faster, without the cost.\n\nTo qualify, all Projects in your Organization must meet the following criteria:\n\n*   Be a non-commercial entity\n*   Be [Public](/llm/markdown/cloud/account-management/projects.md#Change-project-access) in Cypress Cloud\n*   Your Project source code is available in a public location with an [OSI-approved license](https://opensource.org/licenses)\n*   Record minimum of 500 [tests](/llm/markdown/cloud/faq.md#What-counts-as-a-test-result) included with the [Starter Plan](https://www.cypress.io/pricing)\n\n### Requesting OSS plan for an Organization\n\n1.  [Login](https://on.cypress.io/dashboard) to the Cypress Dashboard, or [create an account](https://on.cypress.io/dashboard) if you are a new user.\n    \n2.  Go the [Organizations page](https://on.cypress.io/dashboard/organizations) to select the Organization you want to associate with an OSS plan. If you have no Organizations, you can create one by clicking the **\\+ Create New Organization** button.\n    \n3.  Go to the **Billing & Usage** page, click **Upgrade** and then click on the **Apply for an open source plan** link at the bottom of the page. _Note: Access to all Projects must be set to **public** to enable this link._\n    \n4.  Fill in and submit the OSS plan request form.\n    \n5.  You'll receive an email confirming your request. The Cypress Team will review your request and, if approved, an OSS plan subscription will be applied to your Organization.\n    \n\nIf you have any questions regarding the OSS plan, please feel free [contact us](mailto:hello@cypress.io).\n",
      "section": "cloud",
      "anchors": [
        "open-source-plan"
      ],
      "path": "/llm/json/chunked/cloud/account-management/billing-and-usage.json",
      "token_estimate": 351
    },
    {
      "id": "cloud/account-management/billing-and-usage#requesting-oss-plan-for-an-organization",
      "doc_id": "cloud/account-management/billing-and-usage",
      "heading": "Requesting OSS plan for an Organization",
      "heading_level": 3,
      "content_markdown": "### Requesting OSS plan for an Organization\n\n1.  [Login](https://on.cypress.io/dashboard) to the Cypress Dashboard, or [create an account](https://on.cypress.io/dashboard) if you are a new user.\n    \n2.  Go the [Organizations page](https://on.cypress.io/dashboard/organizations) to select the Organization you want to associate with an OSS plan. If you have no Organizations, you can create one by clicking the **\\+ Create New Organization** button.\n    \n3.  Go to the **Billing & Usage** page, click **Upgrade** and then click on the **Apply for an open source plan** link at the bottom of the page. _Note: Access to all Projects must be set to **public** to enable this link._\n    \n4.  Fill in and submit the OSS plan request form.\n    \n5.  You'll receive an email confirming your request. The Cypress Team will review your request and, if approved, an OSS plan subscription will be applied to your Organization.\n    \n\nIf you have any questions regarding the OSS plan, please feel free [contact us](mailto:hello@cypress.io).\n",
      "section": "cloud",
      "anchors": [
        "requesting-oss-plan-for-an-organization"
      ],
      "path": "/llm/json/chunked/cloud/account-management/billing-and-usage.json",
      "token_estimate": 201
    },
    {
      "id": "cloud/account-management/billing-and-usage#common-billing-questions",
      "doc_id": "cloud/account-management/billing-and-usage",
      "heading": "Common billing questions",
      "heading_level": 2,
      "content_markdown": "## Common billing questions\n\n*   [What counts as a test result?](/llm/markdown/cloud/faq.md#What-counts-as-a-test-result)\n*   [What happens once I reach the test results limit?](/llm/markdown/cloud/faq.md#What-happens-once-I-reach-the-test-results-limit)\n*   [When does my billing period reset?](/llm/markdown/cloud/faq.md#When-does-my-billing-period-reset)\n*   [cy.prompt usage and limits](/llm/markdown/cloud/faq.md#cyprompt)\n*   [How do I reduce my Cypress Cloud usage or lower my bill?](/llm/markdown/cloud/faq.md#How-do-I-reduce-my-Cypress-Cloud-usage-or-lower-my-bill)\n*   [What happens if I downgrade my account?](/llm/markdown/cloud/faq.md#What-happens-if-I-downgrade-my-account)\n*   [How much does it cost?](/llm/markdown/cloud/faq.md#How-much-does-it-cost)\n",
      "section": "cloud",
      "anchors": [
        "common-billing-questions"
      ],
      "path": "/llm/json/chunked/cloud/account-management/billing-and-usage.json",
      "token_estimate": 80
    },
    {
      "id": "cloud/account-management/billing-and-usage#see-also",
      "doc_id": "cloud/account-management/billing-and-usage",
      "heading": "See also",
      "heading_level": 2,
      "content_markdown": "## See also\n\n*   [Cypress Cloud pricing](https://www.cypress.io/pricing)\n*   [Free Trial of Cypress Cloud](/llm/markdown/cloud/get-started/free-trial.md)\n*   [Managing organizations](/llm/markdown/cloud/account-management/organizations.md)\n*   [Managing users](/llm/markdown/cloud/account-management/users.md)\n*   [Managing teams](/llm/markdown/cloud/account-management/teams.md)\n*   [cy.prompt()](/llm/markdown/api/commands/prompt.md)\n*   [Cypress AI](/llm/markdown/cloud/features/cypress-ai-features.md)\n*   [Cypress Cloud FAQ](/llm/markdown/cloud/faq.md)\n",
      "section": "cloud",
      "anchors": [
        "see-also"
      ],
      "path": "/llm/json/chunked/cloud/account-management/billing-and-usage.json",
      "token_estimate": 41
    }
  ]
}