What is Rovo Studio? A practical guide to Atlassian's AI builder

TL;DR

Rovo Studio is Atlassian's no-code builder for Rovo agents, automation flows and (in beta) no-code apps, and it's included with every paid Standard, Premium and Enterprise Cloud plan. The unified Studio went generally available on 6 May 2026, and anyone in your organization can build agents by default unless an admin restricts it.

There's no Studio fee, but the agents you build spend Rovo credits each time they run (10 for a basic agent, a variable amount for advanced ones), and from December 3, 2026, usage over the allowance is billed at $0.01 per credit.

It's a strong fit if your work lives in Atlassian Cloud. If your support team runs on Zendesk, Freshdesk or another helpdesk, I'd look at eesel, which works tickets there and in Jira Service Management, priced per ticket or chat.

What is Atlassian Rovo Studio?

Atlassian Rovo Studio is the builder workspace within the Rovo suite where you can design your own AI-powered tools, aimed at "builders and creators" with no coding skills required. Think of it as a workshop for creating virtual teammates (AI agents), setting up automation flows for tedious tasks, building no-code apps (still in beta), and keeping your company's knowledge organized.

You find it in the app switcher of any Atlassian Cloud app, and you can describe your problem in plain language and let Studio recommend what to build.

It’s built to work hand-in-glove with Atlassian's own products, especially Jira, Confluence, and Jira Service Management. The whole system runs on what Atlassian calls the "Teamwork Graph." It's a fancy term for a data layer that maps out all the connections between your projects, documents, and teams, giving the AI a deep understanding of your organization's context.

So, instead of a simple chatbot, Rovo Studio gives you the pieces to build an AI that can handle specific jobs, like answering common questions, summarizing project updates, or even managing parts of your service desk. It's Atlassian's answer to the need for customizable AI that does more than just write text.

What can you build with Rovo Studio?

You can build agents, automation flows and, in beta, no-code apps. Rovo Studio isn't just one thing; it's a collection of Atlassian's building and automation features all pulled into one place. Let's dig into what you can actually do with it.

Build custom AI agents in Rovo Studio

The big promise here is the ability to create your own "Rovo agents." These are AI bots that you can train on specific information and give them jobs to do.

• Virtual teammates: You can create agents with their own personalities and areas of expertise. For instance, you could whip up an "Onboarding Agent" that new hires can ask questions, trained exclusively on your HR docs in Confluence.

• Task-specific helpers: Some teams are already using it for niche tasks. In a case study with Tempo, Atlassian showed how they built an agent to help users write complex formulas in their Structure app. This freed up their technical team from answering the same questions over and over.

• Customer support: You can also build agents for Jira Service Management to handle customer support questions automatically. JSM's virtual service agent is managed in Studio and answers in Slack or Microsoft Teams, the portal, email and the help center widget, but it lives inside JSM and needs a Service Collection Premium or Enterprise plan.

Create and manage automations with Rovo Studio

Atlassian has had automation for a while, but Rovo Studio aims to be the central hub for it all. You can set up triggers and actions to cut down on manual work. For example, you could create a rule that auto-assigns a Jira ticket when a specific keyword pops up, or have an AI agent summarize a long ticket description and post it as a comment. It's all about making sure the routine stuff gets done without someone having to click a button every time.

What else does Rovo Studio cover?

Rovo Studio also ties into other Atlassian features to help organize your company’s information:

• Assets: For IT teams using Jira Service Management, you can manage asset schemas right from the Studio. This is super helpful for keeping track of inventory and understanding how different systems are connected.

• Company hubs: "Company Hubs" are curated intranet pages in Confluence that act as a single source of truth for the whole company. Atlassian says hubs "will be added soon" to the new unified Studio, so for now you build them in Confluence.

• No-code apps (beta): You describe an app in a prompt and Studio builds a Forge app, which a developer can later open in the Forge CLI to keep building with code.

What are the limitations of Rovo Studio?

The main ones are its Atlassian-first reach, how much setup autonomous work takes, and model and data controls. While Rovo Studio sounds great for teams that live and breathe Atlassian, that tight integration has some real downsides. For a lot of teams, particularly in customer support, these limitations can be a real roadblock.

Rovo Studio: A powerful tool locked in the Atlassian ecosystem

Here’s the biggest catch: Rovo Studio is built around Atlassian. Its main advantage, the Teamwork Graph, understands data in Jira, Confluence, and the apps your admins connect (Zendesk is available as a connector, for example). But the tools agents use to act are mostly Jira, Confluence and JSM actions plus a few others like sending a Slack message or a Gmail email, so a Zendesk or Freshdesk ticket queue isn't something a Studio agent works directly. It’s also a cloud-only tool: Data Center customers get connectors that sync data into the cloud, but Studio itself needs a Cloud plan.

This is a problem for any company that picks and chooses the best tools for the job. A useful AI solution has to meet your team where they already are.

How "agentic" are Rovo Studio AI agents, really?

The term "AI agent" makes you think of an autonomous bot that can make its own decisions. Rovo agents can get there, with setup.

In chat, an agent asks for confirmation before tools that change data. In automation flows they can be set to act without confirmation, though Atlassian's out-of-the-box agents don't take actions there. Users still report rough edges, like the "ability to consistently execute without human confirmation" (r/atlassian).

If you're looking for an AI that can triage a ticket, look up an order in an external system, and decide whether to close or escalate it all by itself, Rovo Studio can get part of the way, but reaching an external system means a Forge tool or an MCP connection.

For comparison, a more advanced AI platform has a real workflow engine. The eesel AI Agent, for instance, can be set up with custom actions to check order data in Shopify, update custom ticket fields in Zendesk, and then close the ticket, all in one go without any human intervention.

How does Rovo Studio handle data privacy and model choice?

Rovo uses third-party Large Language Models (LLMs) from providers like OpenAI, and Atlassian notes that certain AI providers may process data in non-EU regions. That applies to your internal data from Jira and Confluence too.

Rovo is covered by Atlassian's data residency, but for companies with strict data privacy rules, the processing location can be a deal-breaker. On models, agents on the Think deeper tier let you pick from a list Atlassian has tested; the choice is Atlassian's list, not any model you bring.

How much does Rovo Studio cost?

Rovo Studio has no fee of its own: it comes with every paid Standard, Premium and Enterprise Cloud plan of Jira, Confluence, Service Collection and Teamwork Collection, and Free plans don't include it. Atlassian first made Rovo and Studio included at no extra cost on Premium and Enterprise Cloud plans in April 2025, and Standard plans now get it too. There is also a standalone Rovo Standard seat in beta, which includes Studio without Forge apps.

While "no extra cost" sounds free, what you pay for is usage. Each paid user adds 25, 70 or 150 Rovo credits a month on Jira or Confluence (250, 700 or 1,500 on the collections) to a shared pool, and the agents you build spend 10 credits per basic run or a variable amount for advanced agents. From December 3, 2026, extra usage is billed at $0.01 per credit, on by default unless an admin caps it.

This bundled model is a sharp contrast to platforms that offer clear, fixed pricing. With a tool like eesel AI, you pay one monthly price sized to your volume (from $299/month for 500 credits), with every integration included and no hidden fees, letting you adopt powerful AI without a massive ecosystem upgrade.

Is Rovo Studio right for your team?

Yes, if your company already lives in Atlassian Cloud. It really comes down to one question: how deep are you in the Atlassian world?

If your company is fully committed to the Atlassian Cloud ecosystem and already paying for a Standard, Premium or Enterprise plan, then Rovo Studio is a pretty nice perk. It gives you a convenient way to build AI helpers and manage your automations without leaving your familiar tools.

But for most customer support and IT teams, the limitations are hard to ignore. The Atlassian-first reach, the setup it takes to run agents unattended, the credit metering and the data processing questions make it a tough sell for anyone using external help desks or needing more advanced, independent automation.

Where does Rovo Studio fall short, and when should you use eesel instead?

Rovo Studio is good at what it was built for. It's inside Jira and Confluence, its agents only see what each person can already see, search and summaries are free, and paid seats come with credits. For a team that lives entirely in Atlassian and mostly wants search, summaries and simple agents it already pays for, Rovo is still the better pick.

It falls short when work leaves Atlassian or runs at volume. Agents act mostly in Jira, Confluence and JSM, the JSM virtual service agent needs Service Collection Premium or Enterprise, and every agent run draws on credits billed at $0.01 each over the allowance from December 3, 2026.

eesel AI is an AI teammate that works inside Jira Service Management through its Jira integration, reads your docs through its Confluence integration (read-only), and also works in Slack, Microsoft Teams and help desks like Zendesk.

It acts, not just searches: it creates, assigns and transitions Jira issues, updates fields, replies to the customer or leaves an internal note. It also connects to Zendesk, Freshdesk and Slack, and you can test it on real questions before it goes live.

Rovo has Slack and Teams apps too, but everyone who asks it something needs an Atlassian account on a Rovo-enabled site, and replies in public channels need a shared account an admin sets up. With eesel, the person asking needs no Atlassian seat. One difference to know: eesel reads Confluence through one Atlassian API token, so it sees what that account can see rather than each asker's own permissions.

Pricing is per ticket or chat handled, not per Atlassian seat: free with 100 credits, then from $299 a month for 500. At an industrial automation company, every ticket arrives with a drafted answer as an internal note. For more options, see my Rovo alternatives guide, or start free.