Current situation
Jupyter Viewer for Confluence is an Atlassian Marketplace app built on the Atlassian Connect framework. Today, most cloud apps in the Atlassian Marketplace rely on this framework, which requires apps to be hosted on the Marketplace Partner’s infrastructure.
In 2019, Atlassian announced a new framework called Atlassian Forge, which allows apps to run on Atlassian’s infrastructure instead. Since then, Atlassian has expanded Forge’s capabilities to support the migration of existing Connect-based apps.
We believe Forge offers significant benefits for customers, including improved security and performance. As a result, we are preparing Jupyter Viewer for Confluence to transition to the Forge platform.
Migration Plan
What to Expect
The app experience should remain the same—users should notice only minor differences.
Starting in February 2025, we will begin a staged migration to Forge, releasing several updates along the way. While most updates will be minor, some major updates will be required due to changes in permission scopes between the Connect and Forge platforms. We will strive to maintain a similar permission footprint.
Confluence administrators will need to approve major updates, but they can do so at their convenience.
Timeline
The migration will begin in February 2025 and continue throughout the first part of the year.
During this period, Jupyter Viewer for Confluence will run on a combination of Atlassian-hosted and our own infrastructure.
Our goal is a complete migration to Forge, though the exact timeline depends on how quickly we can progress through the transition stages.
Questions
If you have any questions or concerns about this migration, please contact us via the Support Portal or via email.