The 60-second brief
- 1JetBrains launched Air on September 22, combining agent tools in its IDEs, Air Teams workflows and Air Governance, formerly JetBrains Central.
- 2Air Teams, available to business customers, assigns AI credits and service accounts to projects and ships with 10 automation templates.
- 3Pricing and firm release dates were not published; buyers should confirm supported third-party agents and cap project credit spending.
- Air product components
- 3 (Air in IDEs, Air Teams, Air Governance)
- Automation templates in Air Teams at launch
- 10
- Years JetBrains has built developer tools
- 26
Why CEOs should care
For engineering leaders, Air's pitch is continuity: one environment for individual agent use, shared workflows and oversight, without committing to a single AI model vendor. If your developers already use JetBrains IDEs, ask which third-party agents are supported through ACP at launch, since the launch post did not name them, and whether Air Governance policies apply equally to Junie and to outside agents.
CFOs should pay attention to the credit model. Air Teams assigns AI credits to projects and lets administrators choose whether automations spend project or personal credits, and JetBrains says automations using project credits keep running after their creator leaves. That helps continuity, but it also means spending can persist unnoticed. Ask for per-project usage reports and set caps before automations multiply.
CISOs should ask what Air Governance records about which agents accessed which repositories and where code was sent, the kinds of questions JetBrains says the product is meant to answer. Project service accounts should be reviewed like any other non-human identity, with least-privilege access to Jira, Figma, Linear and GitHub.
Key takeaways
- JetBrains launched Air on September 22, combining agent tools in its IDEs, Air Teams workflows and Air Governance, formerly JetBrains Central.
- Air Teams, available to business customers, assigns AI credits and service accounts to projects and ships with 10 automation templates.
- Pricing and firm release dates were not published; buyers should confirm supported third-party agents and cap project credit spending.
The news
JetBrains Air, announced September 22, regroups JetBrains' AI coding products into one system spanning individual developer tools, shared team workflows and company-wide governance, as businesses look for control over how AI agents touch their code.
The system has three parts, according to a post by Kirill Skrygan on the JetBrains blog. Air in JetBrains IDEs is where developers direct agents and verify their output. Air Teams coordinates software-delivery workflows involving both developers and autonomous agents. Air Governance, the renamed JetBrains Central, covers organizational policy, visibility, auditability and cost management for AI-assisted development. Junie, JetBrains' own coding agent, works across all three.
JetBrains is betting on openness rather than a single model. Air connects to agents through the Agent Client Protocol (ACP), a standard for linking development environments with coding agents, plus an ACP Registry for finding compatible agents. The company wrote that no single model, agent or service will suit every developer, team or task. Techzine reported JetBrains' view that multi-model support is the minimum requirement, and that the products grew out of six months of public experimentation.
On September 28, JetBrains detailed Air Teams, which it said is available now to business customers, with individual customers to follow. Teams get shared cloud environments, cloud tasks, team projects and automations for recurring work, with 10 automation templates at launch. Projects have their own service accounts and AI credits, and administrators decide whether an automation draws on project credits or the creator's personal credits. Connectors link to Jira, Figma and Linear, and GitHub pull requests and events can trigger work. JetBrains summed up the idea: “What one developer figures out, everyone can use.”
JetBrains did not publish pricing or firm release dates for every component. The launch post said Air will develop through a rolling series of releases, with the availability of each part to be clarified as it ships.
The numbers
- Air product components
- 3 (Air in IDEs, Air Teams, Air Governance)
- Automation templates in Air Teams at launch
- 10
- Years JetBrains has built developer tools
- 26
Why CEOs should care
For engineering leaders, Air's pitch is continuity: one environment for individual agent use, shared workflows and oversight, without committing to a single AI model vendor. If your developers already use JetBrains IDEs, ask which third-party agents are supported through ACP at launch, since the launch post did not name them, and whether Air Governance policies apply equally to Junie and to outside agents.
CFOs should pay attention to the credit model. Air Teams assigns AI credits to projects and lets administrators choose whether automations spend project or personal credits, and JetBrains says automations using project credits keep running after their creator leaves. That helps continuity, but it also means spending can persist unnoticed. Ask for per-project usage reports and set caps before automations multiply.
CISOs should ask what Air Governance records about which agents accessed which repositories and where code was sent, the kinds of questions JetBrains says the product is meant to answer. Project service accounts should be reviewed like any other non-human identity, with least-privilege access to Jira, Figma, Linear and GitHub.
The bigger picture
Developer tooling is converging on the same theme as the rest of enterprise software: governance for AI agents. JetBrains, which has built developer tools for 26 years, is repositioning from single-developer workbenches toward team and organizational control, Techzine noted. In the same week, Docker made cloud sandboxes for coding agents generally available and Okta expanded its agent identity controls, a sign that vendors at every layer of the stack are competing to own agent oversight.
For buyers, the practical effect is that AI coding is shifting from a per-developer tool purchase toward a platform decision with administration, credits and audit trails. That moves ownership from individual teams to central engineering, security and finance functions, and turns vendor lock-in into a governance question as much as a technical one. JetBrains' emphasis on the Agent Client Protocol is its answer to that concern.
What's next
Watch for JetBrains to publish pricing and availability for Air Governance, to open Air Teams to individual customers, and to list the third-party agents that work through ACP. How Air's credits are priced against rivals' AI coding plans will shape adoption.
Sources
- PrimaryJetBrains Air: Building a System of Products for Agentic Software Development— JetBrains
- PrimaryAir Teams: Bring Your Best Agentic Workflows to the Whole Team— JetBrains
- ReportJetBrains consolidates agentic tooling under the new name Air— Techzine Global
- PrimaryIntroducing Cloud Sandboxes: Start on Your Laptop, Finish in the Cloud— Docker
- PrimaryNew Okta for AI Agents innovations increase visibility into agent behavior, secure connections at runtime, and enforce continuous agent governance— Okta
Spotted an error? Request a correction. Read our editorial standards and AI policy.
Free newsletters
The technology briefing for people running businesses.
Daily, weekly, bi-weekly or monthly. You choose.
