Forge Migration

Jupyter Viewer for Confluence is built on the Atlassian Connection framework, which requires the app to be hosted on our (Mibex Software) 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 data residency. 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 March 2025, we will begin a staged migration to Forge, releasing several updates along the way. We expect most updates to be minor and we will strive to maintain a similar permission footprint.

This means that during the updates no action is expected from the Administrator or from users of the app. However, we will communicate any action that may needed as we progress through the transitional stages to Forge.

Timeline

The migration will begin in March 2025 and continue throughout the 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.