Credits are the unit of consumption in Gatling Enterprise Edition. Every test run spends credits proportional to the number of load generators deployed and the duration of the run. Understanding how credits are consumed helps you plan your testing budget, avoid surprises at billing time, and configure usage quotas to keep teams within their allotted share.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/gatling/gatling.io-doc/llms.txt
Use this file to discover all available pages before exploring further.
How credits are consumed
The consumption rule is straightforward:1 credit = 1 load generator × 1 minute of runtimeThis means a test that runs for 10 minutes with 3 load generators consumes 30 credits.
Credits are consumed the same way for both managed locations (hosted by Gatling) and private locations (hosted on your own infrastructure). The billing model does not differentiate between the two.
When does consumption begin?
Credit consumption begins as soon as the load generator instances or containers are provisioned and running—not when virtual users start injecting load. In particular, the simulation initialization phase (which may include long-running custom setup code) is included in the billable time.Viewing credit usage
Credit consumption details are visible in the Billing section of Organization Settings (accessible to Administrators only).- Paid Plans
- Trial Plans
The Billing page shows the number of credits consumed and the number remaining for the current billing period. Credits refresh at the start of each billing cycle.
Extra credits
When you approach the credit limit of your current plan, Gatling Enterprise can be configured to allow extra credits to keep tests running. This prevents a hard block on test launches when the plan allocation runs out.Approach the credit limit
As your available credits decrease, the Billing page displays a warning indicator.
Enable extra credits
Click Edit spending limit on the Billing page and enter the maximum number of extra credits your organization is allowed to consume above the plan allocation.
Extra credits and spending limits are only available for subscriptions billed through Stripe. Organizations subscribed via the AWS Marketplace manage consumption through AWS billing controls.
Team credit quotas
Organization administrators can assign credit quotas to individual teams to prevent any single team from consuming a disproportionate share of the organization’s total allocation.Edit the quota
Click the edit icon (✏️) in the Quota column next to the team whose limit you want to set.
Enter a quota value
Enter the maximum number of credits the team can consume per billing period. Leave the field empty to allow unlimited consumption for that team.
You must be an Organization Administrator with an annual plan to set team credit quotas. The quota applies to either an annual or monthly period depending on your plan configuration.
Plans and offers
Current plan details and available offers are visible at the bottom of the Billing page.| Field | Description |
|---|---|
| Status | Current plan state: Active, Terminated, or PaymentFailure |
| From / To | Start and optional end date of the current plan |
| Credits | Number of credits awarded per billing cycle |
- Stripe: click Subscribe now on the desired offer, or click Contact us for custom plans.
- AWS Marketplace: subscribe via the Gatling Enterprise listing on AWS Marketplace.