---
title: "Atlassian Cloud Price Increase & Rovo Billing 2026: Stay or Switch?"
slug: atlassian-cloud-price-increase-rovo-billing-2026-stay-or-switch
date: 2026-11-16
author: Abdul Aleem
categories: [Atlassian, Jira Service Management, Confluence]
excerpt: "Atlassian Cloud prices rose October 13, 2026 and Rovo usage billing starts December 3. Here's the real cost impact on JSM and Confluence teams."
tldr: "Atlassian's October seat-price increase stacks with December usage-based billing for Rovo and automation. Model your consumption, set spending caps, and decide before December 3."
canonical: https://clonepartner.com/blog/atlassian-cloud-price-increase-rovo-billing-2026-stay-or-switch
---

# Atlassian Cloud Price Increase & Rovo Billing 2026: Stay or Switch?


# Atlassian Cloud Price Increase & Rovo Billing 2026: Stay or Switch?

Atlassian Cloud teams face two back-to-back pricing changes in late 2026: a list-price increase that took effect October 13 ([atlassian.com](https://www.atlassian.com/licensing/future-pricing/cloud)), and usage-based billing for Rovo credits, automation steps, and AI agent resolutions starting December 3 ([atlassian.com](https://www.atlassian.com/blog/company-news/expanded-usage-based-pricing)). The combined effect is a meaningful jump in total cost of ownership — especially for JSM and Confluence teams that rely heavily on automation or are beginning to adopt Atlassian's AI features. For most teams the answer is to stay and cap usage before December 3; switching makes sense when your modeled AI and automation overage, added to the new seat price, pushes the total past what an alternative would cost.

A price increase alone is not a reason to migrate platforms. But the shift from flat-rate SaaS subscriptions to consumption-based billing for core AI and automation features is a structural change. IT directors and procurement leads must now forecast usage, not just headcount.

This article breaks down both changes, models the real cost impact, and helps you decide whether to absorb the increase, optimize your usage, or start evaluating alternatives.

## What changed on October 13, 2026?

Atlassian's new Cloud list prices took effect October 13, 2026 (Pacific Time) for new purchases, renewals, and upgrades ([atlassian.com](https://www.atlassian.com/licensing/future-pricing/cloud)). The change covers Standard, Premium, and Enterprise plans of Jira, Confluence, Jira Service Management / Service Collection, and Teamwork Collection, plus Atlassian Guard, Bitbucket Premium, and Jira Product Discovery.

The size of the increase is not a single flat number, and Atlassian does not publish a percentage. Partners have published their own estimates, and they disagree, so plan from your own renewal quote rather than any one figure.

As of November 2026, Atlassian's pricing pages list these per-unit prices at their default settings ([atlassian.com](https://www.atlassian.com/software/jira/pricing), [atlassian.com](https://www.atlassian.com/software/jira/service-management/pricing), [atlassian.com](https://www.atlassian.com/software/confluence/pricing)):

| Product | Plan | Listed price |
|---|---|---|
| Jira | Standard | $8.48 /user/mo |
| Jira | Premium | $15.56 /user/mo |
| Jira Service Management (Service Collection) | Standard | $21.50 /agent/mo |
| Jira Service Management (Service Collection) | Premium | $55.28 /agent/mo |
| Confluence | Standard | $5.78 /user/mo |
| Confluence | Premium | $11.16 /user/mo |

*Your actual invoice depends on tier, seat count, and billing cycle. Per-unit prices shift at tier boundaries — a 50-agent deployment may price differently from a 100-agent one. Check Atlassian's pricing pages for your own numbers.*

Annual subscriptions keep their current price until renewal and pay the new price on renewals on or after that date. Atlassian honors a quote created before October 13 at the old price until the quote expires.

For teams hovering near the edge of a user tier (say, 485 users on a 500-user band), adding a handful of seats can push you into the next pricing tier — raising the base cost before usage is even counted.

> [!NOTE]
> The October 13 seat-price increase and the December 3 usage-based billing are separate changes. Track them independently on your budget model.

## What is Atlassian usage-based billing, and when does it start?

**Atlassian usage-based billing** is a consumption layer that sits on top of existing seat-based subscriptions, metering specific capabilities and charging for usage above an included monthly allowance. Atlassian announced this expanded usage-based pricing model on September 1, 2026, with effect from December 3, 2026 for most meters ([atlassian.com](https://www.atlassian.com/blog/company-news/expanded-usage-based-pricing)).

The five metered capabilities are: Rovo credits, Automation steps, Assets objects, Bitbucket usage, and Customer Service Management (CSM) AI agent resolutions.

Most paid Cloud apps and Collections include a monthly allowance for the meters they cover, sized by plan tier and seat count, pooled across your entire organization, and refreshing every monthly billing period ([atlassian.com](https://www.atlassian.com/resources/usage)). CSM AI agent resolutions are the exception, with no included allowance. Unused Rovo credits do not roll over to the next month.

### Rovo credit allowances

**Atlassian Rovo** is an AI-powered enterprise search and knowledge discovery product that connects Atlassian tools with third-party SaaS applications (Google Drive, Slack, GitHub, etc.). Rovo and the AI features previously branded as Atlassian Intelligence are included with every paid Jira, Confluence, Service Collection, and Teamwork Collection plan — no separate line item.

**Atlassian Collections** are product bundles: the **Service Collection** includes Jira Service Management, Customer Service Management, Assets, and Rovo; the **Teamwork Collection** includes Jira, Confluence, Loom, and Rovo ([atlassian.com](https://www.atlassian.com/resources/usage)). These bundles carry higher per-user Rovo allowances than standalone product subscriptions.

The monthly credit allowance per user varies significantly by product and tier ([support.atlassian.com](https://support.atlassian.com/rovo/docs/rovo-usage-limits/)):

| Plan tier | Jira / Confluence (standalone) | Service Collection or Teamwork Collection |
|---|---|---|
| Standard | 25 credits/user/mo | 250 credits/user/mo |
| Premium | 70 credits/user/mo | 700 credits/user/mo |
| Enterprise | 150 credits/user/mo | 1,500 credits/user/mo |

**What is free vs. what consumes credits:**
- **Free (no credit cost):** Inline summaries, rewrites, and Rovo Search ([atlassian.com](https://www.atlassian.com/blog/company-news/expanded-usage-based-pricing))
- **Credit-consuming:** Rovo Chat, Confluence AI Slides, Jira Coding Agent, and enriched Teamwork Graph API calls. Basic interactions, such as a Quick Answers message in Rovo Chat, cost 10 credits per billable event, and in chat each user message is a billable event. Premium features use a variable number of credits ([support.atlassian.com](https://support.atlassian.com/rovo/docs/rovo-usage-limits/)).

Overage rate: **$0.01 per credit ($10 per 1,000 credits)** ([atlassian.com](https://www.atlassian.com/licensing/rovo)).

### Automation step allowances

Atlassian is shifting how automation usage is measured, from counting entire "flow runs" to counting individual **steps**. Each trigger, condition, action, branch, and loop that runs now counts as a separate step ([support.atlassian.com](https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/)). A rule with one trigger, three actions, one branch, and two sub-actions consumes 7 steps per execution — not 1 run.

Enterprise plans, which previously included unlimited automation runs, will now include a defined monthly allowance instead ([atlassian.com](https://www.atlassian.com/licensing/automation)). This is a material entitlement reduction for Enterprise customers.

| Plan tier | Jira | Confluence | JSM / Service Collection |
|---|---|---|---|
| Standard | 400/user/mo | 100/user/mo | 3,000/user/mo |
| Premium | 750/user/mo | 250/user/mo | 6,500/user/mo |
| Enterprise | 1,000/user/mo | 500/user/mo | 9,500/user/mo |

Overage rate: **$0.50 per 1,000 steps** beyond the included allowance.

Steps are pooled at the **organization level** across all products. Your Jira automation and your JSM automation draw from the same pool — the previous per-app limits go away under this model.

### CSM AI agent resolutions

**Customer Service Management (CSM)** is Atlassian's newer external-facing support product, distinct from Jira Service Management (JSM), which is primarily for internal IT service desks. CSM AI agent resolutions are billed per resolution, while Atlassian's other AI features, such as Request Resolver and the Self-service Agent, consume Rovo credits ([support.atlassian.com](https://support.atlassian.com/rovo/docs/rovo-usage-limits/)).

CSM plans include no allowance for AI agent resolutions. Your organization is charged **$1.00 per resolution** from the first successful resolution. A resolution is counted only when the AI agent resolves a customer request without handing the conversation to your team. When the AI agent hands off to a human agent, no AI agent resolution fee is billed ([support.atlassian.com](https://support.atlassian.com/customer-service-management/docs/manage-usage-for-ai-agent-resolutions/)).

**CSM AI resolution cost check:** At $1.00 per resolution, 500 resolutions a month cost $500 and 1,000 cost $1,000. Compare that with what your team spends handling the same requests by hand, not with license fees — a seat license does not scale with ticket volume. Model your specific ticket volume before assuming AI deflection is cost-positive.

## Why the Rovo credit math matters more than the seat-price increase

The October seat-price increase is a line-item adjustment: predictable, quantifiable, already on the invoice. The December usage-based billing is structurally different. It introduces **variable cost** into what was previously a flat subscription.

Here is the core tension: a basic Rovo interaction, such as one Quick Answers message in Rovo Chat, costs **10 credits** ([support.atlassian.com](https://support.atlassian.com/rovo/docs/rovo-usage-limits/)). A Premium standalone Jira or Confluence plan includes **70 credits per user per month** — about seven Quick Answers messages per user. Premium features such as Think deeper, Confluence slides, and Jira Coding Agent cost a variable number of credits on top of that.

**Worked example — 100-user Confluence Premium team** (the usage figure is an assumption, not an Atlassian estimate):
- Included allowance: 100 users × 70 credits = **7,000 credits/month**
- Assumed usage: each user sends 5 Quick Answers messages a working day for 20 days = 100 messages × 10 credits = **1,000 credits per user, or 100,000 credits/month**
- Overage: 93,000 credits × $0.01 = **$930/month in Rovo charges alone**, or **$11,160/year**
- Confluence Premium seat cost at the listed $11.16/user/month: 100 users × $11.16 × 12 = **$13,392/year**
- Combined: at that assumed usage, the Rovo overage adds **more than 80%** to the annual Confluence bill

Automation overages are less alarming by comparison. That same 100-user organization has 25,000 pooled Confluence automation steps included per month (100 × 250), which covers moderate automation use. The financial risk concentrates in AI usage, not workflow automation — at least for now.

**Can you disable Rovo?** This is a critical operational question. Extra usage (overage billing) can be disabled per meter in Atlassian Administration, which pauses new credit-consuming requests once the pool is exhausted; a chat or agent task already in progress completes. Organization admins can also deactivate AI altogether: Rovo's core search and Studio apps keep working, but AI-powered search and chat become unavailable ([atlassian.com](https://www.atlassian.com/licensing/rovo)). Disabling extra usage means those features simply stop working mid-month once the pool depletes, rather than continuing to bill. Admins should decide: cap and cut off, or allow overages with a defined spending limit.

> [!WARNING]
> Extra usage is **enabled by default**. If your admins do nothing before December 3, overage charges start accruing the moment your organization exceeds its pooled allowance. Organization and billing admins can disable extra usage at any time in Atlassian Administration ([support.atlassian.com](https://support.atlassian.com/rovo/docs/rovo-usage-limits/)). Set a spending cap before December 3 — not after.

## How does this hit JSM teams?

JSM teams face compounding cost pressure from three directions simultaneously.

**Direction 1: Seat-price increase.** JSM carries the highest per-seat price of the products in the table above. As of November 2026, Atlassian's pricing page lists JSM (Service Collection) Standard at $21.50 per agent per month and Premium at $55.28 per agent per month at its default team size ([atlassian.com](https://www.atlassian.com/software/jira/service-management/pricing)). On a 50-agent Premium deployment, every dollar of increase per agent adds **$600/year** (50 agents × $1 × 12 months), so check your renewal quote's per-agent figure against your current invoice.

**Direction 2: Automation step pooling and step-based counting.** Under the new model, steps are pooled across your entire Atlassian organization. Your Jira automation and your JSM automation draw from the same pool — the previous per-app limits go away. JSM Premium includes 6,500 steps per user per month, pooled org-wide.

The step-based counting model penalizes complex rules disproportionately. A JSM ticket creation rule that:
- Triggers on new ticket (1 step)
- Checks priority condition (1 step)
- Creates sub-task (1 step)
- Sends Slack notification (1 step)
- Looks up asset record (1 step)
- Branches by department (1 step)
- Sends email to department head (1 step)

...consumes **7 steps per ticket**, not 1 run. If your service desk handles 2,000 tickets/month and 60% hit this rule, that is 8,400 steps from one rule alone. A 10-agent JSM Premium team has 65,000 pooled steps/month — this single rule consumes 13% of the pool.

**Direction 3: AI agent resolution costs.** Atlassian's AI features such as Request Resolver and the Self-service Agent consume Rovo credits. For CSM (external customer service), AI resolutions are billed at $1.00 each with no included allowance. A customer service team resolving 10,000 requests per month with the CSM AI agent incurs $10,000/month in resolution fees — a cost that must be weighed against the human handling time it displaces.

Model your specific usage before the change takes effect.

> [!WARNING]
> Audit your Jira and JSM automation rules before December 2026. Count the steps in each rule — not the rules themselves. A single rule with 10 actions, one branch, and two conditions consumes 13+ steps per execution. Identify your highest-frequency rules first; a rule that fires 5,000 times/month at 10 steps consumes 50,000 steps — potentially your entire org-level pool.

If you're evaluating alternatives, we've published a detailed comparison in our [JSM Alternatives 2026](https://clonepartner.com/blog/blog/jira-service-management-alternatives-2026-features-tco-migration) guide and a direct architecture comparison in [ServiceNow vs JSM](https://clonepartner.com/blog/blog/servicenow-vs-jira-service-management-architecture-guide-2026).

## How does this hit Confluence teams?

Confluence is lighter on automation but potentially heavier on AI usage. Standalone Confluence users receive 25 (Standard) or 70 (Premium) Rovo credits per user per month — a tenth of what the Collections include at the same tier. Content-heavy teams using Rovo Chat to search across spaces, generate summaries, or produce AI Slides will exhaust this pool quickly.

**Credit consumption patterns by team type:**

| Team type | Likely usage pattern | Risk level |
|---|---|---|
| Engineering (ADRs, technical specs) | AI search + summarization daily | High |
| HR/Policy documentation | Periodic AI drafting, low volume | Medium |
| Read-heavy knowledge base | Mostly search, minimal AI | Low |
| Product (PRDs, roadmaps) | Rovo Chat for research + drafting | High |

Every Rovo Chat message, AI Slides generation request, or enriched Teamwork Graph call consumes credits from the shared org pool. The usage dashboard sits in Atlassian Administration, where admins can break consumption down by app and user.

A compounding risk: AI is automatically activated for all apps on Standard, Premium, and Enterprise plans ([atlassian.com](https://www.atlassian.com/licensing/rovo)). Users who experiment casually with Rovo Chat drain the pooled allowance without realizing it. The overage bill appears on the org admin's invoice — not on any individual user's screen.

**Standalone Confluence users on Standard plans are most exposed.** At 25 credits/user/month, a team of 50 has 1,250 credits total — 125 Quick Answers messages at 10 credits each. Ten active users sending three messages a day exhaust the pool in about four days.

Teams that use Confluence primarily as a read-heavy knowledge base may find the AI features irrelevant and the price increase hard to justify. For those teams, we've built a framework for evaluating whether to stay: [Should You Migrate Off Confluence?](https://clonepartner.com/blog/blog/should-you-migrate-off-confluence-a-2026-renewal-decision-framework)

## AI pricing across alternatives: a comparison

For teams evaluating whether to switch platforms, AI feature pricing is now a first-order cost consideration — not a secondary feature comparison. Below is a simplified comparison of AI allowances across major alternatives as of November 2026:

| Platform | AI product | Included allowance | Overage / add-on |
|---|---|---|---|
| Atlassian Confluence Premium | Rovo | 70 credits/user/mo | $0.01/credit |
| Notion (Business plan, $20/seat/mo) | Notion AI | 1,500 Standard credits and 500 Select credits per seat per month | Admins can buy more Notion credits |
| Microsoft 365 + Copilot | Microsoft 365 Copilot | Separate add-on for enterprise plans | $30/user/mo, paid yearly |
| Freshservice | Freddy AI | Enterprise includes Freddy AI Agent (Classic), 1,200 sessions per license per year | Freddy AI Copilot: $29/agent/mo add-on |

*Sources: [notion.com](https://www.notion.com/pricing), [microsoft.com](https://www.microsoft.com/en-us/microsoft-365-copilot/pricing/enterprise), [freshworks.com](https://www.freshworks.com/freshservice/pricing/). Competitor pricing changes frequently. Verify current rates directly with vendors before making switching decisions.*

Key observation: Notion now meters AI in credits too, so a credit pool is not unique to Atlassian. Microsoft 365 Copilot is a flat per-user add-on, which is more predictable for heavy AI users but costs the same for light ones.

## Should you switch platforms?

The seat-price increase alone does not justify migration. On a $30,000/year Confluence bill, every 1% of increase is $300 a year — real money, but usually less than what a switch costs in internal engineering time, retraining, and disruption. The question is whether the **cumulative cost trajectory** changes the calculus.

**Consider switching if:**

- **Rovo adoption is near zero, and you want to keep it that way.** Rovo is included in your seat price whether your teams use it or not; admins can deactivate AI, but the seat price stays the same. SharePoint, which comes with Microsoft 365 E3/E5 licenses many organizations already pay for, can cost less for low-AI teams.
- **You're on Data Center and facing the [2029 EOL](https://clonepartner.com/blog/blog/atlassian-data-center-end-of-life-2029-guide).** The October Cloud price increase and December usage billing make the "move to Cloud" path more expensive than it appeared during planning. If you haven't committed, the cost-of-inaction calculation shifts. See our [Data Center End of Sale pricing guide](https://clonepartner.com/blog/blog/atlassian-data-center-end-of-sale-2026-pricing).
- **Your JSM automation is complex and high-volume.** A rule that used to count as one run now counts one step for every trigger, condition, action, branch, and loop that executes, so a 10-step rule uses ten units where it used one. Model your step consumption before renewal — not after.
- **You've been quoted for Enterprise based on the "unlimited automation" promise.** Enterprise, which previously included unlimited automation runs, now lands at 1,000 steps per user per month. This is a material entitlement reduction that changes the Enterprise value proposition.
- **You only use JSM for IT support or Confluence as a standalone wiki.** If you're not embedded across the full Atlassian stack (Jira + Confluence + JSM + Bitbucket + Guard), migration is significantly easier and the switching cost is lower.

**Consider staying if:**

- **You're deeply integrated across the full Atlassian stack.** Migration cost across Jira + Confluence + JSM + Bitbucket is high, and few single-vendor alternatives replicate the full surface area without significant workflow rebuilding.
- **Your Rovo usage is light or controllable.** If you disable extra usage or set a spending cap and your teams stay within the included allowance, the December change is a non-event financially.
- **You're on a Service Collection or Teamwork Collection.** Bundle users receive 10x the Rovo credits of standalone product users (250 vs. 25 at Standard tier), making regular use more likely to stay within the included allowance.
- **You've already negotiated annual pricing.** Annual contracts renew at the new rate, but you have a locked price until that renewal date. Use the remaining contract period to measure actual consumption, model the December bill, and decide with real data.

## What to do before December 3, 2026

Regardless of whether you stay or switch, these steps are immediate:

1. **Audit your usage.** Open Atlassian Administration → Insights → Platform usage ([atlassian.com](https://www.atlassian.com/resources/usage)). Check current consumption for Rovo credits and Automation steps against your included allowances.

2. **Set spending caps before December 3.** Extra usage is on by default. Decide per meter: allow extra usage with a defined cap, or disable it entirely. If you disable it, credit-consuming requests pause until the pool resets on the billing date. Know which workflows and user-facing features break before you flip the switch.

3. **Identify heavy consumers.** Use the Rovo credits dashboard in Atlassian Administration, which breaks usage down by app and user, to identify which users, automated agents, or integration workflows drive the most consumption. Atlassian lists a usage data export among the capabilities it plans to launch by December 3, 2026.

4. **Model the December bill.** Formula: (Current monthly consumption − included allowance) × overage rate = incremental monthly cost. Run this calculation separately for Rovo credits and automation steps. If your current consumption data is incomplete, use the week-1 numbers and extrapolate.

5. **Review and simplify automation rules.** Count the steps in your highest-frequency rules — not the rules themselves. Each trigger, condition, action, branch, and loop is a step. Simplify multi-step chains, disable redundant rules, and consolidate webhook actions where possible. Prioritize rules that fire most frequently.

6. **Deprovision inactive users.** Compare your identity provider logs against your Atlassian billing console. Remove users who haven't logged in for 90 days. This reduces your seat cost and, because allowances are user-count-based, reduces the denominator of your pooled budget — but it also reduces the included allowance pool. Confirm the net effect in your specific tier before bulk deprovisioning.

7. **Decide on platform trajectory before renewal.** If the combined seat increase and usage billing push your TCO past acceptable thresholds, start scoping alternatives at least 3–4 months before your Atlassian renewal deadline. Platform decisions require time; starting the analysis at renewal leaves you no leverage.

## Migration technical realities

If the combined pricing changes push your analysis toward switching platforms, the migration itself has specific technical constraints worth understanding before committing to a target platform.

### JSM data migration challenges

JSM stores issue descriptions and comments in **Atlassian Document Format (ADF)**, a structured JSON schema. Zendesk and Freshservice expect HTML or rich text. Migration requires parsing ADF node arrays and converting inline images, mentions, tables, and formatting blocks into target-platform equivalents.

JSM Service Level Agreements (SLAs) and historical SLA metric data rarely map 1-to-1 via standard APIs. Ticket records, comments, and attachments can migrate; historical SLA compliance timers and reporting baselines typically remain in the source system. Plan for a reporting gap period.

### Confluence data migration challenges

Confluence pages rely heavily on **macros**: Jira Issue links, Dynamic Content, Table of Contents, Draw.io diagrams. These macros have no native equivalents in Notion or SharePoint. When migrating, dynamic Jira issue tables become static text, Draw.io diagrams must be exported as PNGs or XML and re-embedded, and Table of Contents macros require manual reconstruction or platform-specific alternatives.

Notion's API allows 600 requests per minute per connection on Business and Enterprise plans and 180 per minute on other plans, with a separate per-workspace limit shared by all connections ([developers.notion.com](https://developers.notion.com/reference/request-limits)). That constrains migration speed for large workspaces. Creating 50,000 Confluence pages at one request each takes about 1.4 hours at 600 a minute, or about 4.6 hours at 180 a minute, for page creation alone — before page content and attachment uploads, which need more requests.

SharePoint is frequently "free" because it's bundled with Microsoft E3/E5 licenses, but it represents a usability downgrade from Confluence for teams accustomed to wiki-style content architecture. The migration tooling is mature, but the post-migration user experience requires deliberate information architecture work.

For self-hosted teams seeking to escape SaaS consumption billing entirely, open-source alternatives including **XWiki** (Confluence-like wiki with macro support) and **BookStack** (documentation-focused, simpler structure) are worth evaluating. Neither has usage-based billing.

### Evaluating migration scope

Before selecting a migration partner or tool, establish:
- **Record count by type:** tickets, pages, comments, attachments
- **Attachment total volume (GB):** drives storage and transfer time
- **Custom field complexity:** non-standard fields require explicit mapping
- **API access:** confirm admin-level API tokens for both source and target
- **Data residency requirements:** confirm where each target hosts your data and whether that meets your compliance requirements before committing

Keep two clocks apart when you plan. The data migration ClonePartner performs is usually completed within 1–5 business days, depending on data volume, complexity, and API rate limits, and in under 24 hours for small datasets under 10,000 records. Your team keeps working in Jira and Confluence while the history loads during the working days before go-live. On go-live Monday, the Atlassian instance is frozen before the working day starts, a final delta of changed records runs in about 30 minutes, and everyone logs in to the new platform that morning. Rebuilding workflows, automations, and macros on the new platform runs on your own team's timeline.

## Fixed-price migrations, no surprises

We've executed 1,500+ successful migrations and built 500+ integrations. Our process follows API → JSON → CSV transfer preferences, with multi-stage validation using checksums and field-level parity checks.

One fixed price per project, starting at $500. No hourly billing, no per-record pricing. You get a dedicated migration engineer — not a ticket queue. Our SOC 2 Type II and ISO 27001 controls are independently audited, with AES-256 encryption at rest and TLS 1.2+ in transit. Staging databases are purged within 30 days of project close.

If you're evaluating your Atlassian Cloud renewal, we provide unlimited sample migrations until the data mapping is right.

> Book a free 30-minute scoping call. We'll review your Atlassian data volume, evaluate target platform API limits, and provide a fixed-price migration proposal — before the December 3 billing change hits.
>
> [Talk to us](https://clonepartner.com/talk-to-us?duration=30&utm_source=blog&utm_medium=button&utm_campaign=demo_bookings&utm_content=cta_click&utm_term=demo_button_click)

## Frequently asked questions

### How much did Atlassian Cloud prices increase in October 2026?

Atlassian raised Cloud list prices for new purchases, renewals, and upgrades on October 13, 2026 (Pacific Time). Atlassian does not publish a percentage increase, and partner estimates disagree. Compare your renewal quote line by line with Atlassian's current Cloud pricing tables.

### When does Atlassian usage-based billing for Rovo start?

Usage-based billing for Rovo credits, Automation steps, Assets objects, Bitbucket usage, and CSM AI agent resolutions takes effect December 3, 2026 for most meters. Atlassian announced the change on September 1, 2026. Extra usage is enabled by default — admins should set spending caps before that date.

### How many Rovo credits are included per user?

Jira and Confluence include 25 Rovo credits per user per month on Standard, 70 on Premium, and 150 on Enterprise. Service Collection and Teamwork Collection include 10x those amounts: 250, 700, and 1,500 per user. Credits are pooled organization-wide and reset monthly with no rollover. Overage costs $0.01 per credit.

### Does Atlassian Enterprise still include unlimited automation?

No. As of the December 3, 2026 change, Enterprise plans shift from unlimited automation runs to 1,000 automation steps per user per month for Jira (9,500 for JSM/Service Collection). Automation is now counted per step — each trigger, condition, action, branch, and loop counts individually — rather than per rule run.

### Should I switch from JSM or Confluence because of the 2026 price increase?

The seat-price increase alone typically doesn't justify a migration. The bigger question is whether stacking that increase with Rovo usage billing and automation step metering pushes your total cost of ownership past the break-even point for switching. Model your actual usage in Atlassian Administration before deciding.
