Atlassian has introduced a trust badge for marketplace apps called “Runs on Atlassian” (RoA). Apps with this badge run 100% on Atlassian infrastructure, benefitting enterprise customers with strict data privacy requirements.
To understand whether the standard edition of Slide Presenter will be “Runs on Atlassian” or not, there are three things to know.
Slide Presenter itself runs 100% on Atlassian infrastructure
The Slide Presenter app itself, the presentation layouting, the storage for your themes and settings - everything runs on Atlassian infrastructure and locally in your browser. No addcraft-operated infrastructure is involved.
The only egress happening is analytics and can be switched on and off by you, which is completely “Runs on Atlassian” compliant.
So, being “Runs on Atlassian” should be as easy as pie, shouldn’t it? Unfortunately, no. There are two aspects:
The problem: Egress for external presentation content
Your Confluence content may contain embedded YouTube videos, a loom video - or an iFrame with your Tableau KPI dashboard. Many of our customers love Slide Presenter because exactly these kinds of content can be presented.
To be able to display this content in your presentations, we need to allow egress to these websites. And because we cannot guess all the websites you might want to embed, we have to allow all egress. Of course, this is not accepted for “Runs on Atlassian”.
But not all hope is lost: customer-managed egress might save the day.
Introducing customer-managed egress
Using customer-managed egress, you can decide yourself which external domains you want to accept yourself. This Forge feature is in preview and we already have implemented it completely.
Currently, we are waiting for Atlassian to fix a bug in the feature (see FRGE-2262) - when this is done, we’ll roll out customer-managed egress settings for Slide Presenter.
But even when this will be rolled out: Unfortunately, “Runs on Atlassian” does not accept using the customer-managed egress options. We’re in the process of discussing this with Atlassian and the developer community. We hope that Atlassian will declare the way we offer you customer-managed egress as RoA-eligible.
Migration from Connect to Forge
As our customers are updating Slide Presenter to the new Forge-only version, their data has to be migrated from the old Connect backend to their new Forge installation. To do that, the app has to access the old Connect backend, obviously.
We only fetch our customers data from our Connect databases and send it to Forge - nothing is sent the other way round. However, this migration feature blocks us from being RoA-eligible for the time being.
We’ll sunset this migration feature when Atlassian sunsets Connect - so presumably in January 2027, we’ll remove this. Ideally, Slide Presenter will then directly be RoA.
The quick solution: a zero-egress app listing
If you would like to use Slide Presenter in the meantime but have a strict RoA requirement, please get in touch with us. What keeps the app from being RoA are just some options, we can provide a RoA-compatible version of the app in no time. We’d love to hear from you!