Enterprise

Atlassian and OpenAI wire GPT-6 into Rovo, raising the context bar for small B2B teams

An expanded Oct. 6 partnership routes OpenAI's frontier models through Atlassian's Teamwork Graph — turning Jira and Confluence records into fuel for AI-assisted work decisions.

By Asher Glick· Enterprise software desk·2026-10-09·3 min read

Photo: Unsplash / Ngital — Six colleagues collaborating around a conference table with laptops in a modern office

Atlassian and OpenAI expanded their partnership on Oct. 6, routing GPT-6 Astra and the GPT-5.6 series through Rovo and wiring them directly into the Teamwork Graph, Atlassian’s enterprise context layer. The deal extends a collaboration that began in 2023, but the shape of it has changed: the model is no longer the product, the record is.

That reframing matters more than the version numbers. In the same week, Atlassian rebuilt its MCP server to let outside agents reach into the same substrate. Steve McDowell, writing in Forbes, reports the server exposes “more than 200 tools to agents, including Claude, ChatGPT, Codex, and Cursor.” The Teamwork Graph itself, per McDowell, “now holds more than 250 billion connections, up from roughly 150 billion six months ago.” A context layer that nearly doubles in half a year isn’t a feature. It’s a land grab.

For a five-to-thirty-person B2B shop, the practical change is immediate. Inside AI News describes a product manager querying launch readiness across Jira tickets, Confluence documents, and relevant discussions in one pass, surfacing engineering blockers and missed milestones without a separate knowledge-graph project. That’s work that previously required either a dedicated ops hire or an afternoon of manual stitching.

The commercial design is the quieter tell. Atlassian says Rovo credits will transition to usage-based billing in December 2026, aligning revenue with billable agent activity rather than seats. It’s the same metering logic Vida Global applied to outcome-based billing for AI sales agents and that Cohere’s North 2 release implied for reusable enterprise agents: the unit of value is the action, not the login.

Two caveats sit under the announcement. Atlassian’s AMP protocol hasn’t been published as a specification other vendors can independently implement, which keeps the openness story one-sided. And TokenPost notes the company didn’t disclose a timeline for additional features beyond the integrations shipped this week.

The AWS re:Invent 2017 keynote established that whoever owns the data gravity owns the next decade’s margin. Atlassian is running the same play on workflow records, and OpenAI just agreed to be the engine inside it.

Sources