Enable developers with AI for the full software delivery lifecycle

Rovo Dev Standard is available with a free 30-day trial, sign up here.

Annual plans for Rovo Dev Standard are designed for large organizations and include a free 30-day trial for eligible customers. To learn more, register your interest today.

There is no free tier for Rovo Dev. However, limited monthly Rovo Dev credits per developer may be gradually offered to selected customers with a Standard, Premium, or Enterprise Cloud plan of Jira, starting with sites that already use Rovo. Admins will be notified 30 days prior to their rollout and will have an option to opt-out if needed.

Yes. Rovo Dev is available on an annual plan so customers can scale AI development with more predictable budgets. On the annual plan, Rovo Dev credits are still allocated and reset monthly per user, while billing is annual. Register your interest to learn more.

Rovo Dev credits represent units of usage based on interactions with specific Rovo Dev AI features. For example, reviewing a pull request or interacting with Rovo Dev CLI.

Credits are allocated per user and the amount of credits an interaction uses depends on the complexity of that interaction.

For Rovo Dev Standard, when a user’s allocated credit limit is reached, additional usage incurs charges of $0.01 per credit, with a default monthly limit of 2,000 Rovo Dev credits per user. Admins can set custom limits and controls on a per-site basis.

For more information on Rovo Dev credits, please review Rovo Dev documentation.

Rovo Dev is also available as an annual billing plan. This annual plan includes a Rovo Dev credit allowance per user that is allocated and resets monthly. Sign up to learn more.

Yes, Rovo Dev AI features that are labeled as beta will use Rovo Dev credits, unless otherwise communicated. The amount of credits an interaction uses depends on the complexity of that interaction.

For more information on Rovo Dev credits, please review Rovo Dev documentation.

We don’t require upgrading your entire site to Rovo Dev Standard. Seats can be purchased for individual developers.

Yes, the Atlassian Customer Agreement and all terms incorporated therein govern your use of Rovo Dev, including the Privacy Policy, Acceptable Use Policy, Data Processing Addendum, and Product-Specific Terms.

If your request does not align with these terms, it may not be fulfilled by Rovo Dev.

Rovo Dev respects all of your existing permissions. In fact, two users may receive different results based on the content they have access to.

The data a user has access to is not limited to the product they’re working on. Due to the connected nature of our products, information can be pulled from various experiences to inform a response (or output). All permissions set in the Atlassian platform will be respected as long as they are set accordingly.

Some Rovo Dev features allow users to connect third-party data sources and enter prompts to send data outside your Atlassian site. If you don’t want users to access this feature, you can turn off Rovo Dev. Learn more about MCP Client security considerations here.