As we transition from the beta program to our GA offering, here’s what you need to know.
After this date, beta features will no longer be available.
We’ll shift our support focus from the beta program to the generally available Rovo Dev Standard plan.
Hands‑on support for the legacy beta program will stop, but we will continue to support you through Rovo Dev Standard, including access to future beta features through the Standard plan.
Switch to Rovo Dev Standard. To keep your team using Rovo Dev, you’ll need to move from the beta program to Rovo Dev Standard.
Rovo Dev Standard includes:
A free 30‑day trial
All the latest Rovo Dev features
2,000 Rovo Dev credits during the trial
9am–5pm regional support
Ongoing access to new beta capabilities delivered through Rovo Dev Standard
After the trial, Rovo Dev Standard is $20 USD per user, per month.
To start your Rovo Dev Standard trial:
Go to Atlassian Administration and select your organization.
Select Billing from the sidebar.
Find your Rovo Dev subscription on your site and select Manage.
Select Change plan.
Under Standard, select Try it free.
You can learn more about pricing at the Rovo Dev Pricing | Atlassian.
Here’s how your existing beta capabilities map to Rovo Dev Standard:
Rovo Dev CLI
Available with Rovo Dev Standard.
Code Reviewer
Available with Rovo Dev Standard, now integrated as code reviews in Bitbucket and GitHub.
Deployment Summarizer & Pipeline Troubleshooter
Available with Rovo Dev Standard, now part of Rovo Dev in Bitbucket Pipelines (beta).
Coding agents
Will be available via Rovo Dev in automations (limited beta) with Rovo Dev Standard.
This new experience is designed to improve generated code quality and reduce flakiness when generating code and raising PRs.
Code Planner / Work Item Planner
Not available as a standalone feature in Rovo Dev Standard.
However, code planning capabilities are still available in the Rovo Dev CLI.
Before the beta ends on 26 January 2026, make sure you:
Save any custom coding agent prompts
Export or document any automation rules involving coding agents
Preserve any prompts stored inside automation rules
You’ll lose access to these once the beta program closes, but you can reuse them in Rovo Dev Standard, especially through the CLI and upcoming automations experience.
Working with you during the beta program has been invaluable in helping us refine Rovo Dev and get it ready for launch. We’re excited to see what you build next with Rovo Dev.
If you have questions about the transition, please reach out through our usual support channels or reply in this community thread and we’ll be happy to help.
Laurena Alves
0 comments