The research in brief
Atlassian Government Cloud is a good fit for regulated industry security and compliance project management, but only for eligible U.S. government agencies and government contractors whose workloads fit FedRAMP Moderate. Two of seven platforms named it during the ranking stage, with an average listed rank of 3.0 and a best rank of 2. Its strongest advantage is FedRAMP Moderate authorization for Jira, Confluence, and Jira Service Management in a separate U.S.-resident environment [25]. The main limitation is eligibility: purchase is restricted to U.S. government agencies and organizations doing government-related work, and customer-managed encryption keys are not available [25].
Research Snapshot
| Field | Finding |
|---|---|
| Platform mentions in ranking stage | 2 of 7 platforms (Gemini, Perplexity) |
| Share of included platform responses | 28.6% |
| Average listed rank | 3.0 |
| Best listed rank | 2 (Gemini) |
| Software offering | Atlassian Government Cloud with Jira; Jira Software Enterprise on Government Cloud |
| Overall use-case fit | Good, with eligibility and feature-parity constraints |
| Research date | 2026-10-02 |
Why Atlassian Government Cloud Qualified for This Study
Questions explored
- Is Atlassian Government Cloud a good choice for regulated industry security and compliance pm?
- Why did only two of seven AI platforms name Atlassian Government Cloud in the ranking stage?
Atlassian Government Cloud qualified because it cleared the study's minimum-mention threshold and because its FedRAMP Moderate authorization maps directly to the certification gate that regulated buyers apply before approval. Two of seven platforms named it during ranking discovery, giving it a 28.6% share of included platform responses, an average listed rank of 3.0, and a best rank of 2 (Gemini). The remaining five platforms evaluated fit but did not name the entity during ranking, so their fit ratings are not evidence of ranking support.
The qualification rests on a specific, verifiable authorization rather than general brand familiarity. Atlassian states that Jira, Confluence, and Jira Service Management on Government Cloud hold FedRAMP Moderate authorization [30], and the FedRAMP Marketplace lists Atlassian Government Cloud as FedRAMP Certified / Class C (Moderate) [39]. An independent source reports the authorization was achieved in March 2025 through GSA sponsorship and FedRAMP PMO approval [37].
Government Cloud is a separate environment from commercial Atlassian Cloud, not a configuration of it. Commercial Jira Cloud Enterprise should not be treated as FedRAMP Moderate compliant by itself [25]. That distinction is the reason this entity, rather than standard Jira Cloud Enterprise, appears in a regulated-industry study at all.
The software offering in focus
Questions explored
- Which Atlassian Government Cloud plan should a buyer choose if they need FedRAMP Moderate project management for regulated industry security and compliance pm?
- Is Jira Cloud Enterprise the same as Atlassian Government Cloud for compliance purposes?
The relevant offering is Jira on Atlassian Government Cloud, with Jira Software Enterprise as the plan foundation and Confluence and Jira Service Management available alongside it. Platforms described the relevant product differently - ChatGPT specified "Atlassian Government Cloud with Jira" and explicitly noted that commercial Jira Cloud Enterprise is not the FedRAMP-authorized offering [25], while Perplexity named "Jira Software Enterprise on Atlassian Government Cloud" [5]. These describe the same environment from different angles, but buyers should confirm which SKU appears in the quote.
Government Cloud is built on the same foundations as the Cloud Enterprise plan with additional compliance assurance [25]. Only Jira, Jira Service Management, and Confluence are available in the environment [11]. Advanced Atlassian products such as Guard Premium, Rovo, and Loom are reported as unavailable or restricted [11].
The environment runs in a separate dedicated perimeter isolated from standard Atlassian Cloud via a cross-partition gateway, with network firewalls restricting data egress [11]. Primary data resides in AWS us-east-1 with select components in us-west-2 [11]. Data residency is not a selectable option in Government Cloud; all data is pinned to U.S. regions [15].
What the AI Platforms Agreed About
Questions explored
- What do AI platforms agree Atlassian Government Cloud provides for regulated industry security and compliance pm?
- Does Atlassian Government Cloud include audit logging and SSO for compliance program management?
Platforms agreed on four points with strong consistency: FedRAMP Moderate authorization, U.S.-only data residency, mandatory SSO-based identity, and a documented shared-responsibility model.
On authorization, ChatGPT, Claude, Grok, Perplexity, and Gemini all described FedRAMP Moderate status for Jira, Confluence, and Jira Service Management [30]. The FedRAMP Marketplace listing corroborates this independently [39].
On data residency, Claude, Perplexity, and Grok agreed that all Government Cloud data is U.S.-resident and that residency selection is not offered [15]. Grok added that customer data is encrypted at rest with AES-256 and in transit with TLS 1.2+ [32].
On identity, platforms agreed that SAML single sign-on is the only user login method and that an identity provider is required [9]. Google Workspace is not supported as an identity provider [9].
On shared responsibility, Claude, Grok, and Perplexity all cited the same Atlassian shared-responsibility documentation, which assigns specific Access Control and Audit and Accountability control families between Atlassian and the customer [10].
Where the AI Platforms Disagreed or Were Uncertain
Questions explored
- Do AI platforms disagree about Atlassian Government Cloud pricing and feature parity for regulated buyers?
- Is Atlassian Government Cloud pricing publicly disclosed or quote-only?
Platforms diverged on pricing, feature parity, and overall fit rating. These are genuine conflicts in the supplied evidence, not resolved here.
Pricing conflict. Google reported a 25% premium over Cloud Enterprise with public tiers starting at 201 users and $82,000 annually for 300 Jira users [17]. Perplexity also reported the 25% premium [24]. OpenAI published a tier table listing $82,000 for 300 users, $100,000 for 400 users, $117,500 for 500 users, and $381,500 for 2,000 users, and separately noted a 50% list-price discount for Jira Enterprise Government Cloud subscriptions in Atlassian's purchasing information [25]. Anthropic stated pricing is not publicly disclosed at all and requires direct negotiation [25]. Kimi likewise reported that exact Government Cloud pricing is not publicly listed [22]. These positions cannot all be simultaneously accurate as stated, and the relationship between the published tier table and the discount language should be confirmed in the quote.
Feature parity uncertainty. Anthropic reported that feature parity with standard Jira Cloud Enterprise is uncertain and that Government Cloud may lag due to FedRAMP change-management constraints [11]. OpenAI reported ongoing feature-parity work and advised that commercial Jira features and integrations should not be assumed available [25]. Grok stated AI features, mobile apps, and external customer portals in JSM are unavailable [35]. No platform supplied a definitive feature-by-feature comparison.
Fit rating spread. Ratings ranged from "strong" (Claude, Perplexity) to "good" (ChatGPT, DeepSeek, Gemini, Grok) to "mixed" (Kimi). Kimi's lower rating reflects its view that Atlassian is a general-purpose collaboration platform rather than a purpose-built GRC tool lacking native continuous controls monitoring and pre-mapped frameworks [2].
Stale or conflicting public language. Atlassian's public pages are not fully consistent: some current pages state Government Cloud has achieved FedRAMP Moderate authorization, while an Atlassian government marketing page still contains older "coming soon" and "in process" language [25]. Atlassian's FedRAMP page uses 2026 terminology describing the former FedRAMP Moderate authorization as FedRAMP Certification Class C, while procurement documents may still use the older wording [30].
Features for this workload
Questions explored
- What audit logging, encryption, and access governance features does Atlassian Government Cloud include for regulated industry security and compliance pm?
- Does Atlassian Government Cloud support customer-managed encryption keys for compliance?
Certifications. Atlassian publishes SOC 2 reports and describes an ISO 27001-based Trust Management Program [31]. Anthropic reported a SOC 2 Type II report covering October 1, 2023 to September 30, 2024 with a bridge letter dated January 16, 2025 confirming no material changes [18]. Kimi reported SOC 2 Type II, ISO 27001, and PCI DSS for cloud infrastructure [29]. The exact product-by-product SOC 2 and ISO scope for Jira Government Cloud was not established from the public pages reviewed [25].
Encryption. Government Cloud uses Atlassian-managed encryption keys exclusively. Bring-your-own-key and customer-managed keys are explicitly not available for Government Cloud; BYOK is available only for standard Jira Cloud [14]. This is a hard limitation for buyers whose control baseline requires customer key custody.
Audit logging and access governance. Atlassian provides audit logs covering apps and administration activities as a platform responsibility, and customers must configure their identity provider to disable expired accounts within 24 hours, disable high-risk accounts within one hour, and review accounts annually [10]. Atlassian Cloud Enterprise materials describe organization audit logs and security governance capabilities [20]. The exact Government Cloud audit-log retention, export formats, SIEM connectors, and administrator-event coverage remain unclear from the public pages reviewed [25].
Identity. Government Cloud requires an identity provider because single sign-on is the only user login method, and key Enterprise identity features are included in the Government Cloud subscription without a separate Atlassian Guard requirement for those features [9]. Multi-factor authentication enforcement is not explicitly confirmed in the public documentation reviewed [10].
Marketplace and integrations. Only a subset of Marketplace apps is available. Compatible apps are not necessarily FedRAMP authorized, may not store data in the United States, and require customer security assessment; Atlassian support teams or certified partners install Government Cloud apps rather than customers installing them freely [13]. The current list of compatible apps and their individual data flows can change [25].
Support and uptime. Atlassian documentation states dedicated support and a 99.95% monthly uptime percentage are available for Government Cloud [12]. Atlassian's Cloud Enterprise page describes a 99.95% financially-backed uptime guarantee [22].
Pricing, renewal terms, and ongoing costs
Questions explored
- How much does Atlassian Government Cloud cost per year, and are there setup or cancellation fees?
- What contract terms and minimum user counts apply to Atlassian Government Cloud for regulated industry security and compliance pm?
Pricing is the least settled area in the supplied evidence, and platforms contradicted each other. Buyers should treat every figure below as quote-dependent.
| Source | Reported pricing position |
|---|---|
| 25% premium over Cloud Enterprise; $82,000/yr for 300 Jira users; $100,000/yr for 400; $207,500/yr for 1,000; public tiers to 2,500 users ($468,000/yr) [17] | |
| OpenAI | $82,000 for 300 users; $100,000 for 400; $117,500 for 500; $381,500 for 2,000; larger tiers listed to 150,000 users [25] |
| OpenAI (purchasing page) | 50% list-price discount for Jira Enterprise Government Cloud subscriptions [26] |
| Perplexity | 25% more expensive than Cloud Enterprise; Jira/Confluence start at 201+ users; JSM starts at 26+ agents [24] |
| Anthropic | Not publicly disclosed; direct negotiation required [25] |
| Kimi | Not publicly listed; sales engagement required [22] |
| Grok | Annual contracts only; ~$82,000/yr for 300 users; 8%+ increases planned October 2026 [25] |
Minimum commitment. Google and Perplexity both reported a 201-user minimum entry tier for Jira on Government Cloud, which excludes smaller teams [17].
Contract structure. Government Cloud is purchased by contacting Atlassian directly and is available only as an annual subscription [25]. Google reported purchase through Carahsoft or directly via Atlassian enterprise sales [17]. Grok reported annual terms with usage limited to U.S. government entities or contractors and termination for prohibited use with no refunds [25]. The exact minimum term, renewal, cancellation, price-protection, overage, and termination provisions are unclear from the public materials reviewed [25].
Additional fees. Marketplace app licenses may be separately charged, and app installation and deployment costs may apply and vary by customer [25]. Third-party Marketplace apps may require separate security assessment and authorization work [25]. Migration, implementation, configuration, and partner costs are not publicly quantified [25]. Kimi noted that separate audit and assessment costs are not included [22].
Best Suited For
Questions explored
- Who is Atlassian Government Cloud best suited for in regulated industry security and compliance pm?
- Is Atlassian Government Cloud worth it for federal contractors managing Controlled Unclassified Information?
Atlassian Government Cloud is best suited to U.S. federal, state, and local government organizations and contractors performing government-related work who need Jira-based project and issue management inside a FedRAMP Moderate environment [25]. Federal system integrators and defense contractors managing Controlled Unclassified Information are a named fit [37].
It also suits regulated teams that need mature project, issue, workflow, approval, and reporting capabilities for security and compliance program management, since Jira provides those functions and SSO is mandatory, supporting centralized identity governance [25].
Enterprises willing to operate a separate government environment, accept annual contracting, and run a controlled Marketplace app process are also a fit [25]. Organizations migrating from self-managed Atlassian Data Center to a highly regulated SaaS model were named by Gemini as a fit [17].
Probably Not Best Suited For
Questions explored
- Who should not choose Atlassian Government Cloud for regulated industry security and compliance pm?
- Is Atlassian Government Cloud suitable for healthcare or financial services companies without federal contracts?
Commercial regulated enterprises that are not eligible for Government Cloud should not choose it, because purchase and adoption are restricted to U.S. government agencies and organizations working with the U.S. government on government-related work [25]. Non-federal healthcare enterprises in HIPAA-only environments with no FedRAMP requirement, and financial services firms without federal contracts or CUI obligations, were named as poor fits by Claude [25].
Workloads requiring FedRAMP High, DoD IL5, dedicated customer infrastructure, or customer-managed encryption keys should not select Government Cloud. Public Atlassian materials describe FedRAMP High and IL5 as future or roadmap objectives rather than current authorization [19], and BYOK is explicitly unavailable [14].
Organizations dependent on a large portfolio of Marketplace integrations or self-service app installation are a poor fit, as are buyers seeking transparent self-service pricing or monthly cancellation flexibility [25]. Teams with fewer than 201 Jira users cannot justify the minimum entry tier [17]. Buyers needing out-of-the-box continuous controls monitoring, pre-mapped regulatory frameworks, automated evidence collection, or auditor portals should note that Jira is a general-purpose platform without those native capabilities [2].
When Another Option May Be Better
Questions explored
- What is a better alternative to Atlassian Government Cloud for a regulated buyer who needs customer-managed encryption keys?
- When should a regulated buyer choose commercial Jira Cloud Enterprise instead of Atlassian Government Cloud?
A commercial regulated enterprise needing broad SaaS eligibility rather than a government-only environment should evaluate commercial Jira Cloud Enterprise or another enterprise platform with the required certifications and contractual controls [25]. Non-federal Regulated Industries without FedRAMP requirements may find standard Jira Cloud Enterprise with SOC 2 compliance sufficient and more cost-effective [25].
A workload requiring dedicated single-tenant infrastructure, customer-managed keys, or stronger data-isolation guarantees should evaluate Atlassian Isolated Cloud or a suitable self-managed Data Center alternative, since customer-managed encryption keys are identified for Isolated Cloud rather than Government Cloud [4].
A workload requiring FedRAMP High, DoD IL5, or another authorization above Moderate should select a service with the required current authorization [25]. Buyers needing multi-region data residency or global deployment should consider Jira Cloud Enterprise with data residency selection or on-premises Jira Data Center, since Government Cloud offers no residency choice [15].
Buyers needing out-of-the-box multi-framework compliance automation with pre-mapped controls, continuous automated posture monitoring, or auditor portals should evaluate purpose-built GRC platforms, which offer capabilities Atlassian lacks natively [2]. Buyers requiring on-premises, self-managed, or air-gapped deployment should look elsewhere, as Government Cloud is cloud-only [21].
Questions to ask before choosing a provider
Questions explored
- What should a buyer confirm with Atlassian Government Cloud before signing a contract?
- Which FedRAMP authorization boundary and data locations apply to the proposed Atlassian Government Cloud tenant?
The supplied research surfaced a consistent verification list across platforms. Buyers should confirm each item in writing before signing.
Eligibility and authorization. Confirm the buyer is legally eligible for Government Cloud and that Atlassian will document eligibility in the contract [25]. Confirm the exact Jira Government Cloud service, FedRAMP package, authorization boundary, and current certification status for the proposed tenant [25]. Confirm whether the required control baseline exceeds FedRAMP Moderate - for example FedRAMP High, IL5, HIPAA, PCI DSS, state-specific requirements, or contractual data-localization rules [25].
Data and encryption. Confirm exact data locations for primary data, backups, disaster recovery, audit logs, support records, telemetry, and subprocessors [25]. Confirm what encryption is used at rest and in transit, who controls the keys, and whether any customer-managed key capability is available [25].
Audit and identity. Confirm what audit events are captured, how long they are retained, whether they can be exported, and whether they integrate with the buyer's SIEM [25]. Confirm which identity providers, SAML settings, SCIM capabilities, MFA controls, privileged-access controls, and break-glass procedures are supported [25].
Features and apps. Confirm which Jira features, APIs, automation functions, analytics capabilities, and integrations are unavailable or altered in Government Cloud [25]. For every required Marketplace app, confirm compatibility, data processing location, FedRAMP authorization status, and who performs the required security assessment [25].
Commercial terms. Confirm annual minimums, renewal increases, cancellation rights, service credits, support commitments, implementation fees, and Marketplace charges [25]. Confirm what customer responsibilities remain under the shared-responsibility model and what evidence Atlassian will provide for the buyer's authorization package [25].
The consensus assessment
Atlassian Government Cloud is a good fit for regulated industry security and compliance project management, but only within a narrow eligibility band. Two of seven platforms named it during ranking, with an average listed rank of 3.0 and a best rank of 2. Platform fit ratings ranged from strong (Claude, Perplexity) to good (ChatGPT, DeepSeek, Gemini, Grok) to mixed (Kimi).
The consensus case for it rests on FedRAMP Moderate authorization for Jira, Confluence, and Jira Service Management, U.S.-only data residency in a separate environment, mandatory SSO, and a documented shared-responsibility model [30]. The consensus case against broad adoption rests on restricted eligibility, unavailable customer-managed encryption keys, uncertain feature parity, limited Marketplace app availability, and pricing that platforms described inconsistently [25].
For U.S. government agencies and contractors whose workload fits FedRAMP Moderate and whose risk team accepts the separate environment, annual commercial model, and shared-responsibility obligations, it is a defensible choice. For broader regulated-industry procurement, it is a specialized option rather than a generally applicable enterprise compliance choice [25]. AI-platform agreement here reflects shared source material, not independently verified product quality.
How This Review Was Produced
This review was produced from a fixed research run dated 2026-10-02. Seven AI platforms were asked which providers they would recommend for a compliance officer at a regulated-industry company evaluating project management software against strict encryption, audit logging, access control, and certification requirements. Platforms that named Atlassian Government Cloud during ranking discovery were counted toward the mention statistics; all seven platforms contributed fit research.
The article uses only the supplied platform responses, citation catalog, and official-page excerpts. No independent testing, customer interviews, or vendor briefings were conducted. Company-owned citations materially outnumber independent citations in the supplied set, so company claims are reported as company claims rather than independently verified facts. Where platforms contradicted each other, the conflict is described rather than resolved.
Research limitations
Several limitations apply. Platform-reported research dates differ from the authoritative run date: Claude reported 2025-01-23 and DeepSeek reported 2026-01-15, while the remaining platforms reported 2026-10-02. These dates are provenance metadata and do not independently prove freshness. Deepseek's response was produced with search disabled, so its claims require explicit verification before being treated as current facts.
The supplied URLs were collected from platform responses and were not independently validated. Company-owned sources materially outnumber independent sources, and no company claim in this review should be read as independently verified. Atlassian's own public pages conflict on Government Cloud status, with some pages describing FedRAMP Moderate authorization as achieved and others retaining older "coming soon" language. Atlassian's FedRAMP page uses 2026 terminology describing the former FedRAMP Moderate authorization as FedRAMP Certification Class C, while procurement documents may still use the older wording.
Pricing was the least consistent area across platforms, with reported positions ranging from a published tier table to a 50% discount to no public disclosure at all. The exact product-by-product SOC 2 and ISO scope for Jira Government Cloud was not established. Government Cloud audit-log retention, export formats, SIEM connectors, backup residency, support-access logging, and customer-managed-key availability remain unclear. The current list of Government Cloud-compatible Marketplace apps and their individual data flows can change. One normalization note records that official-site retrieval failed for at least one mention, and no failed fetch was used as a verified domain key.
Explore more project management and team collaboration software guidance in the category directory.
Sources
Company-Owned Sources
- Updated SOC 2 Reports for Atlassian Products: https://community.atlassian.com/forums/Trust-Security-discussions/Updated-SOC-2-Reports-for-Atlassian-Products/td-p/2924843
- The AI GRC platform for regulated enterprises: https://csquaregrc.com/en-US/regulated-enterprises
- Atlassian Trust Center: https://customertrust.atlassian.com/
- Atlassian Cloud environments: https://developer.atlassian.com/platform/forge/cloud-env/cloud-environments/
- Atlassian Government Cloud: https://developer.atlassian.com/platform/framework/agc/
- Security and compliance on the AGC: https://developer.atlassian.com/platform/framework/agc/security-compliance/
- Atlassian outage and incident reporting: https://status.atlassian.com/
- Explore Jira Cloud plans: https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/
- Plan your Cloud to Atlassian Government Cloud migration: https://support.atlassian.com/migration/docs/learn-about-migrating-cloud-to-atlassian-government-cloud/
- Atlassian Government Cloud shared responsibility model: https://support.atlassian.com/organization-administration/docs/atlassian-government-cloud-shared-responsibility-model/
- How does the Atlassian Government Cloud environment work?: https://support.atlassian.com/organization-administration/docs/how-does-the-atlassian-government-cloud-environment-work/
- Learn about Atlassian Government Cloud: https://support.atlassian.com/organization-administration/docs/learn-about-atlassian-government-cloud/
- Manage Marketplace apps for Atlassian Government apps: https://support.atlassian.com/organization-administration/docs/manage-apps-for-atlassian-government-products/
- Data managed with encryption - Atlassian Support: https://support.atlassian.com/security-and-access-policies/docs/data-managed-with-byok-encryption/
- Understand data residency - Atlassian Support: https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency/
- What is BYOK encryption? - Atlassian Support: https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQEEIobiRJJht6Fx4wxYrtNNR_C8lAWA2t00gKsx5KrzyS6k6qNliufeiMvldafERE99PwNmtvmruqBVbujxZdJuHLyLpxzLYLwxWEMR2IZhmBylNDe8FyfQSrVDd5PGeDDf8lw9Ft05G8dRQXJklEwicZdL1wTKavf3fBX39B5KoM0DPB5tm6c2G0VL0W0mu9KVMv6ofIe7rp6iEcymJNO3R3Bldfs=
- FY25 Mega Audit Atlassian SOC 2 Bridge Letter Template: https://wac-cdn.atlassian.com/misc-assets/pdfs/FY25_Mega_Audit_Atlassian_SOC_2_Bridge_Letter.pdf
- Ramping Up US Government Missions with Atlassian's FedRAMP Moderate Authorized Cloud: https://www.atlassian.com/blog/company-news/atlassiangovernmentcloud
- Peace of mind with built-in security and compliance: https://www.atlassian.com/dam/jcr%3A8fce890f-6a40-4f80-a8b8-5b8c35be9d0f/Cloud_Enterprise_Datasheet.pdf
- Atlassian Enterprise Cloud: https://www.atlassian.com/enterprise/cloud
- Atlassian Cloud Enterprise and Government Cloud: https://www.atlassian.com/enterprise/cloud/cloud-enterprise
- Atlassian Government Cloud: https://www.atlassian.com/government
- Atlassian Government Cloud: https://www.atlassian.com/government/cloud
- Atlassian Government Cloud: https://www.atlassian.com/licensing/government-cloud
- Atlassian Purchasing and Licensing FAQ: https://www.atlassian.com/licensing/purchase-licensing
- Atlassian Pricing: https://www.atlassian.com/pricing
- Atlassian Access: https://www.atlassian.com/software/access
- Atlassian Trust Center: https://www.atlassian.com/trust
- FedRAMP | Atlassian: https://www.atlassian.com/trust/compliance/resources/fedramp
- SOC 2 | Atlassian: https://www.atlassian.com/trust/compliance/resources/soc2
- Atlassian Cloud architecture and operational practices: https://www.atlassian.com/trust/reliability/cloud-architecture-and-operational-practices
- Atlassian Security Incident January 2023: https://www.atlassian.com/trust/security-advisory
- Security Practices | Atlassian: https://www.atlassian.com/trust/security/security-practices
Independent Sources
- Atlassian Government Cloud Is Now GA: https://oxalis.io/atlassian-government-cloud-is-now-ga-heres-what-it-means-for-regulated-agencies-and-their-industry-partners/
- SOC 2 Compliance Software for Fintech: Framework Fit: https://soc2auditors.org/soc-2-compliance-software-for-fintech/
- Atlassian Government Cloud: FedRAMP & Federal Compliance: https://us.seibert.group/blog/atlassian-government-cloud-fedramp
- Atlassian Government Cloud: FedRAMP & Federal Compliance - Seibert Solutions: https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQEEcTBYOmOJkOq7HjTBNJ5H-VSyfOXedWU7Wj45JZjGShxqxOGbkAb1i1z1Kbz2BhPrTSy-KVXTiUoTp1WmS1VWBqbhQjFyBN_C3jW0TNHyx5giLAqMa9T_PiSgL1MU_tDupn1rb8xKWFRYjpzXim5QW7coFm-L
- Atlassian Government Cloud | FedRAMP Marketplace: https://www.fedramp.gov/marketplace/products/FR2412062433/
- Atlassian Cloud Migration Compliance: What Regulated Industries: https://www.praecipio.com/resources/atlassian-cloud-migration-compliance-regulated-industries