Atlassian Sets Rovo FedRAMP Moderate Submission Target for June 2027
Atlassian targets submitting its Rovo AI product for FedRAMP Moderate authorization in Atlassian Government Cloud by June 2027, followed by Impact Level 5 and FedRAMP High submissions in 2028 and 2029. These are submission targets—not authorization or availability dates—and Rovo is currently unavailable to Atlassian Government organizations.
Key Signals
- Atlassian targets Rovo FedRAMP Moderate submission in June 2027
- Rovo is currently unavailable to Atlassian Government organizations
- Impact Level 5 submission target is July 2028
- FedRAMP High submission target is January 2029
- Submission milestones do not establish authorization or availability
Atlassian has established a sequence of future government-cloud submission targets for Rovo, its AI product. The company is targeting a FedRAMP Moderate submission in June 2027 through Atlassian Government Cloud. It has also set targets for an Impact Level 5 submission in July 2028 and a FedRAMP High submission in January 2029. These milestones give federal agencies, contractors, and other government customers a view of Atlassian’s stated roadmap, but they do not indicate that any authorization has been granted.
Rovo is currently unavailable to Atlassian Government organizations. The distinction between a planned submission and an authorization is important for procurement and security decisions: submitting a package is a step in an authorization process, not proof that a service has completed review or can be used for government workloads. The announced dates should therefore be treated as planning targets rather than firm operational availability dates. The source does not state that the product has received FedRAMP Moderate, Impact Level 5, or FedRAMP High approval.
For procurement teams evaluating Atlassian services, the June 2027 target may help frame market research and future requirements planning, but it does not make Rovo currently eligible for use in an agency environment. Teams should verify the product’s authorization and availability status at the time of acquisition, and should assess whether the applicable cloud environment and impact level meet their security requirements. Contractors should likewise avoid treating a roadmap milestone as permission to process government information using Rovo.
The later targets may be relevant to organizations planning for higher-assurance cloud environments. Atlassian’s stated sequence places Impact Level 5 in July 2028 and FedRAMP High in January 2029, after the planned Moderate submission. Those future milestones could inform long-range vendor assessments and cloud modernization planning, but the available information does not establish whether submissions will occur on schedule, how long reviews may take, or when the product might become available. Agencies should use the targets as indicators of vendor intent while maintaining independent authorization and suitability checks.
- Atlassian targets a June 2027 FedRAMP Moderate submission for Rovo in Atlassian Government Cloud.
- The June 2027 date is a submission target, not a completed FedRAMP authorization or a promised availability date.
- Rovo is currently unavailable to Atlassian Government organizations.
- Atlassian targets an Impact Level 5 submission in July 2028.
- The company targets a FedRAMP High submission in January 2029.
- None of the announced submission targets establishes that Rovo will receive authorization or become available by the stated date.
- Procurement teams should distinguish a planned submission from an authorization when evaluating product eligibility and government-cloud requirements.
- Agencies and contractors should confirm current authorization status before considering Rovo for government workloads, particularly for higher-assurance environments.
Agencies
- Federal Risk and Authorization Management Program
Vendors
- Atlassian
Sources
- Atlassian Targets June 2027 Rovo Submission in Atlassian Government Cloud | TokenPostwww.tokenpost.com · Nov 07