.webp)
Set Menu or A La Carte? A Practical Guide to Atlassian Collections
Go price Jira Service Management this month and something quietly odd happens: the answer that comes back is not really about Jira Service Management. Atlassian’s pricing now speaks in terms of something called the Service Collection. Same product, same per-agent rates, different menu. And it is not an isolated rebranding. Since April 2025, Atlassian has reorganized its catalog into five Collections, and if you buy, renew, or govern Atlassian licensing, the shape of that menu now matters more than most feature announcements.
Here is what sits in each Collection, which products you can no longer order à la carte, and the math that decides whether the set menu saves you money or charges you for a course nobody eats.
What Atlassian actually changed
Collections are curated bundles of Atlassian apps and Rovo agents sold as a single subscription: one price, one invoice line, one pool of users. The rollout has been steady rather than loud. Teamwork and Strategy arrived at Team ’25 in April 2025, Service and Software followed in late 2025, and Product, the fifth, was announced at Team ’26 this spring. Each is organized around a type of work rather than a job title, which is a genuinely useful way to think about tooling and, not coincidentally, an effective way to sell more of the platform at once. All five are cloud subscriptions, which for Data Center holdouts makes the Collections question part of the migration conversation rather than separate from it.
The five collections at a glance
Teamwork Collection
Jira, Confluence, Loom, and Rovo: the general-purpose bundle for planning, documenting, and communicating across an organization. It ships in Standard, Premium, and Enterprise tiers; Premium and Enterprise include Rovo and Atlassian Guard Standard at no extra charge, and Enterprise becomes available above 800 users on annual billing only. This is the flagship, with the clearest economics of the five. We covered what changed in the Teamwork Collection at Team ’26 earlier this year.
Strategy Collection
Focus for enterprise strategic planning, Talent for putting the right people on the right priorities, and Align (the product formerly sold as Jira Align), plus Rovo. This one targets leadership and portfolio seats rather than the whole company, and pricing is quote-based. The structural detail worth noting: under current packaging, Focus, Talent, and Align are not offered as individual subscriptions. You buy the set.
Service Collection
Jira Service Management, Customer Service Management, Assets, and Rovo. This is less a new bundle than a repackaging: the familiar per-agent price points carried over, at current list $20 per agent per month on Standard and $51.42 on Premium with Enterprise quoted, and Customer Service Management joined every tier. Assets, which recently moved out into its own apartment as a platform app, ships with object allowances by tier. If you run a service desk on Atlassian Cloud, you are already a Collections customer whether you noticed or not; my field notes on the Service Collection reinvention cover how fast the product side is moving underneath the packaging.
Software Collection
Rovo Dev for agentic coding, DX (the engineering intelligence platform Atlassian acquired), Pipelines for continuous integration and delivery at scale, and Bitbucket for source code management. This is the engineering bundle, priced per seat plus consumption, and best modeled per developer rather than per organization.
Product Collection
The newest, announced at Team ’26: Jira Product Discovery, a new Feedback app that pulls customer input from support tickets, sales calls, and chat channels into structured insight, and Rovo, with Pendo as the first product-analytics integration. Release-state precision matters here. Per Atlassian’s announcement, Feedback is available through an Early Access Program waitlist, and a Jira Product Discovery Enterprise edition is expected in the coming months. Real and promising, but partially Early Access, so plan pilots rather than production rollouts.
The fine print worth reading twice
Three structural details separate a good Collections decision from an expensive one.
Some products only exist inside a bundle. Focus, Talent, and Feedback have no standalone price, and the à la carte menu has only shrunk since April 2025. Avaratak’s read: expect the next interesting Atlassian app to ship inside a Collection first.
The consumption meters. Collections keep per-user or per-agent pricing, but several capabilities inside them are metered. On the Service Collection, Atlassian’s published pricing includes Assets object allowances of 5,000, 50,000, and 500,000 per month by tier with overage from $0.02 per object per month, 1,000 virtual service agent assisted conversations per month then from $0.30 each, and a Customer Service Management artificial-intelligence agent priced at $1 per resolution. None of this is hidden. It simply belongs in the budget on day one rather than in a surprised finance email on day ninety.
The union rule. Per Atlassian’s billing documentation, a Collection is one billable subscription, and every user with access to it on a site counts once. That is elegant when your Jira and Confluence audiences overlap, and expensive when they do not, because everyone is billed for the whole bundle.
The licensing math
Atlassian’s headline claim is savings of up to 40 percent versus buying the apps individually. That figure is vendor-reported, but published list pricing points the same direction: at the time of writing, a 100-user Teamwork Collection Standard runs roughly $15 per user per month, against roughly $34 per user per month for standalone Standard Jira, Confluence, and Loom. The Rovo gap is wider still. Atlassian’s documented credit allowances give single-product seats 25, 70, or 150 Rovo credits per user per month by tier; Teamwork Collection seats carry 250, 700, or 1,500. If your organization is serious about agents, that ten-fold pool can decide the question on its own.
Where the math flips: a component nobody opens (usually Loom) erodes the discount, and diverging audiences erode it faster, because the union rule bills every user for the full set. Guard Standard is included from Premium up; Guard Premium is not. Marketplace apps remain separately billed, and moving installed apps into a Collection can change their pricing, so check before migrating a heavily customized instance. All of this sits inside Atlassian’s broader flexible commercial model, which increasingly rewards committing to more of the platform at once.
The decision rule we use with clients is simple. If the same population would genuinely use two or more of the paid components at the same edition, or you have real Rovo adoption plans, the Collection wins. If you are a one-product shop, or your per-product user counts diverge wildly, price it both ways in Atlassian’s cloud pricing calculator before you sign anything.
The Avaratak Take
The most common mistake in Collections conversations is treating this as a technology decision. It mostly is not. The integration story, with Teamwork Graph context flowing between apps, is a platform property; you get it whether you license individually or as a bundle. What a Collection actually changes is commercial: the price curve, the Rovo credit pool, the number of renewals you juggle, and increasingly whether a product can be purchased at all. Evaluate it the way you would evaluate any enterprise agreement, with a seat census, a shelfware audit, and a three-year view, rather than the way you would evaluate a feature.
The direction of travel is not subtle. Atlassian’s Q4 FY26 shareholder letter made the platform-and-graph strategy explicit, and Collections are its commercial expression: bigger, simpler, stickier subscriptions that make the platform the unit of purchase. That is not a complaint — the bundles are genuinely good value for the right buyer — but it does shift the burden of fit analysis onto you. Atlassian curates the box. Deciding whether your organization will eat everything in it is still your job.
If you want help working out which side of the math your environment lands on, Avaratak’s senior Atlassian consultants run exactly this analysis, from seat census to shelfware audit to a like-for-like quote comparison. Start at avaratak.com.