App compatibility with the AGC

To make an app available to AGC customers, the app must be compatible with the AGC:

• Apps must be registered as Connect-on-Forge or Forge apps.
• Marketplace partners must receive a developer license from the AGC provisioning team. See Request access to the AGC for instructions.

Runs on Atlassian

The Runs on Atlassian (RoA) signal guarantees that an app’s data is hosted exclusively on secure Atlassian cloud infrastructure (which also supports Data Residency features). This signal also guarantees the customer that they're in full control of all app data egress.

This will meet the authorisation requirements of most AGC customers. However, some customers have additional requirements beyond this, and may reach out to you for assistance and clarification.

Customer-specific technical requirements

Each AGC customer will have their own criteria for authorizing an app before installing it. These criteria may include:

• Data residency: some AGC customers may require that your app store customer data only in the US. Others may allow apps that store or process customer data on services hosted outside the US.
• Data segregation: some AGC customers may require their data to be isolated from the data of non-AGC customers. Others may allow their data to be co-mingled with non-AGC customer data.

FedRAMP compatibility and authorization

Marketplace apps deployed in Atlassian Government Cloud (AGC) will not require FedRAMP compliance. App authorization in AGC is considered a customer responsibility, as stated in the Marketplace Shared Responsibility Model.

See Security and compliance on the AGC for related information.