AI adoption and usage
The AI adoption and usage segment lets you track AI adoption and engagement in your organization over a period of time by providing insight into the active use of AI in the organization. You can also track the consumption of AI credits and have an overview of consumers who have reached their monthly limits. This can help you analyze the extent of AI adoption and identify where further action may be needed.
The following adoption and usage metrics are available:
Each metric is presented as a bar chart. The chart can be filtered by the following criteria:
Select one of the predefined time filters that show the last specified period or select a custom date range.
Show only usage data originating from the selected IDEs.
Search for and select users, service accounts, or groups to filter the data. Selecting a group includes all of its members, including members of its subgroups. Expand the group to select which subgroups to include or exclude.

Data included in the metrics
As the data shown in this analytics segment is mostly based on the consumption of AI credits, the metrics include only the data related to the following AI tools and features that consume AI credits:
Junie, both Code and Ask mode. Junie-related data is included in the metrics for both ways of using Junie: through the Junie tool window and through AI Assistant.
Claude Agent, a third-party coding agent by Anthropic integrated with AI Assistant. The AI credit consumption sub-metrics include only the use of Claude Agent with JetBrains AI. For more information, see License with AI.
Codex, a third-party coding agent by OpenAI integrated with AI Assistant. The AI credit consumption sub-metrics include only the use of Codex with JetBrains AI. For more information, see License with AI.
AI Assistant (Chat mode, when used with cloud-hosted third-party models).
Uncategorized: Any tools that consume AI credits but aren't listed above.
The metrics in this analytics segment exclude the following usage of AI tools and features:
In-editor features: The use of features such as Next edit suggestions and Code Completion is not included, as they don't consume AI credits.
Bring Your Own Key (BYOK): This approach lets you use your own API key from a supported AI provider. This usage is billed directly by the provider and does not consume AI credits.
The following interactions are excluded from AI adoption and usage metrics when using an API key from a third-party provider:
AI Assistant in Chat mode when using a model from that provider.
AI Assistant in agent mode when using an agent from that provider.
AI Assistant in Junie mode, if Junie is configured to use a model from that provider. Currently supported for OpenAI and Anthropic models.
AI access and usage
The AI access and usage bar chart shows how many consumers in your organization have AI access and how many of them are actively using AI. This lets you identify the current level of AI availability and adoption in your organization, as well as adoption trends over time.

The following sub-metrics in the chart's legend show the total numbers:
Principals with AI access: The total number of unique consumers who had AI access during the selected period. A consumer is added to the count if the period during which they had AI access overlaps with the selected period in the filter. For example, if the selected period on the chart is from January 15 until January 31, and the user had AI access from January 1 until January 20, they are added to the count.
Active AI consumers: The total number of unique consumers who made at least one request to JetBrains AI that spent AI credits during the selected period.
Depending on the period selected in the time-based filter, the chart shows a different granularity: per day, month, or year. In all cases, each consumer is counted only once per bar, even if they appear in more than one time unit.
What each bar counts depends on the sub-metric:
Principals with AI access: Each bar counts the unique consumers who had AI access during that time unit. For example, a consumer who had access throughout January is counted once in the January bar when the chart shows data per month, and once in each daily bar from January 1 to January 31 when the chart shows data per day.
Active AI consumers: Each bar counts the unique consumers who made at least one request that spent AI credits during that time unit. For example, if a consumer makes requests on January 15 and January 26, they are counted once in the January bar when the chart shows data per month, and once in the January 15 bar and again in the January 26 bar when the chart shows data per day.
AI credit consumption
The AI credit consumption chart shows the number of AI credits spent by AI consumers, broken down by tool.

In addition to the filters available for all charts, you can use the All tools filter above the chart to show AI credit consumption for specific AI tools only. By default, the chart shows the five categories with the highest consumption. The legend also includes the following items:
Total: The total number of AI credits spent across all available AI tools.
Uncategorized: Combined consumption by new or less common tools that are not yet assigned to their own dedicated category. Uncategorized can also appear among the five categories with the highest consumption.
Remaining: Combined consumption of all other categorized tools whose individual consumption falls below that of the five categories with the highest consumption.
Number of AI consumers who hit their AI credit limit
This chart shows the number of unique consumers who used up all of their AI credits. These insights let you identify usage patterns and potential needs to adjust the number of AI credits.

The chart includes the following sub-metric:
Total number of AI consumers who hit their limit: The total number of AI consumers who hit their limit during the selected period.
Depending on the period selected in the time-based filter, the chart shows data per day, month, or year. Each consumer is counted only once per bar, even if they hit their limit multiple times during that period. For example, if a consumer hits their limit on January 15 and again on January 26, they are counted only once in the bar for January when the chart shows data per month. This also applies if a consumer's limit is increased and they reach the new limit within the same period: they are still counted only once for that bar.
For a list of individual AI consumers who hit their limit, see the List of AI consumers who hit their AI credit limit table.
List of AI consumers who hit their AI credit limit
This table lists all consumers who reached their AI credit limit during the selected period. For users, the table includes the consumer's name, email, and the date when they hit the limit. For service accounts, the information includes the service account name, the user who created the account, and the date when it hit the limit.
As a single consumer can hit their quota limit multiple times in a single time period, there may be multiple entries for the same consumer in the table. However, since limit hits are aggregated on a daily level, if a consumer hits more than one limit during the same day, a single entry is added to the table.
