🔐 Not All Cloud Apps Are Built the Same, Here’s Why That Matters
When evaluating an app for your Atlassian instance, the first question is usually: What does it do?
But for security teams, the real question is often:
Where does our data go?
In today’s enterprise environment, architecture matters just as much as features. With increasing focus on compliance, residency, and data protection, understanding how an app is built has become critical.
That’s where the Runs on Atlassian badge comes in
The Runs on Atlassian badge, introduced by Atlassian, is more than just a label in the Marketplace.
It indicates that the app:
Is built on Forge
Runs entirely on Atlassian-hosted infrastructure
Aligns with data residency controls
Does not move customer data outside Atlassian (except permitted analytics data)
In short, the app operates completely within Atlassian’s cloud environment, no external servers, no hidden backend infrastructure, no unexpected data flows.
If you’ve ever been part of a security review or vendor assessment, you know how detailed those discussions can get.
Where is the data processed?
Is it stored externally?
What regions are involved?
Who has access?
Apps that Run on Atlassian simplify those conversations. There’s architectural clarity. There’s infrastructure transparency. And that reduces friction during approvals.
As more organizations adopt cloud-first strategies, trust isn’t just about functionality, it’s about design choices.
The Runs on Atlassian badge helps teams quickly identify apps that align with Atlassian’s cloud security model, making it easier to move forward with confidence.
For teams focusing on protecting sensitive information, solutions like miniOrange DLP follow this approach ensuring data protection within the Atlassian ecosystem while maintaining the transparency enterprises expect.
Absolutely right, appreciate you adding this perspective to the discussion!