Hi Remie,
Our guiding principle is to meet customer needs, and we expect all our products to evolve based on customer feedback.
Before Runs On Atlassian, customers moving to Cloud were often concerned about where app data was processed and stored. These customers had already conducted thorough assessments of Atlassian’s trust posture, and applying the same level of scrutiny to each Marketplace app was both complex and burdensome for customers and partners alike. This challenge is even more pronounced with Connect and Forge Remote apps, where there’s uncertainty around how and where user-generated content is stored, processed, and managed.
We’re hearing from customers that Runs On Atlassian provides the assurance they need - that compute and storage happen on our platform, with the data lifecycle and egress controls they require, without the need for costly individual evaluations.
This is the core value of Runs On Atlassian: workloads and storage are handled on Atlassian’s platform, not the partner’s. To ensure this, we’ve disallowed all egress in the initial release and have intentionally left room in the positioning that some forms of egress may be considered in the future if customer needs demand it but only if the customer is in control. If the focus were solely on egress, we would have simply called it “No egress apps.”
We’re currently conducting a study to better understand how enterprise customers feel about optional egress and REST APIs for Runs On Atlassian apps. We’ll share our findings with partners, along with any implications for the program and the necessary controls and rules to make such changes feasible, if we choose to adjust it. If we change the requirements, it would be because we’ve ensured the technical solution raises the control bar for customers and prevents misrepresentation from bad actors.
We recognise that these RFCs haven’t fully captured our unified thinking they’re intended as starting points for discussion, not as policy or program changes.
We truly appreciate your feedback and will consider it, along with customer research, before making any adjustments to Runs On Atlassian.
Thanks,
James Dumay
Group Product Manager