SaaSJet Apps Are Moving to Atlassian Forge
Atlassian is transitioning all new cloud app development to Forge starting September 17, 2025, and will phase out Connect apps by late 2026. To stay ahead, SaaSJet has already begun migrating our apps to the Forge platform.
What this means for you
Your apps keep working: You’ll continue using SaaSJet apps as usual during and after the migration. We’re designing the process so you won’t experience disruptions.
Better security and compliance: Forge apps run inside Atlassian’s infrastructure. This reduces data egress, strengthens security, and aligns with Atlassian’s data residency program.
Improved performance and reliability: Running closer to Jira means faster responses, fewer delays, and higher stability.
Future-proof features: Forge is Atlassian’s platform of the future, ensuring SaaSJet apps can keep up with new Atlassian features and improvements.
No extra setup: In most cases, you won’t need to grant new permissions or reconfigure anything. If a change is required, we’ll guide you clearly and early.
SaaSJet apps that are already on Forge
* Time in Status and SLA Time and Report for Jira currently use Forge Remote for specific functionality during the migration.
The “Runs on Atlassian” Badge
As part of the migration, SaaSJet apps will begin earning the “Runs on Atlassian” badge.
This badge confirms that:
The app runs directly on Atlassian’s infrastructure.
Data residency requirements are fully supported.
Data egress is minimized, ensuring stronger security.
The app meets Atlassian’s strict compliance standards.
When you see this badge on a SaaSJet app, you can be confident it delivers the highest level of trust, reliability, and compliance within the Atlassian ecosystem.
“Runs on Atlassian” SaaSJet apps
The Challenges Ahead
Large-scale migration: Moving our portfolio of apps to Forge is a major project. While this work is underway, some updates may take longer than usual as we balance migration with delivering new improvements.
Reworking complex features: Certain advanced functions built on Connect need to be reimagined for Forge. This takes extra development time but will lead to stronger, more modern solutions.
Performance tuning: Forge introduces new technical limits and usage patterns. We’re refining how resource-intensive tasks are handled to keep your apps fast and reliable.
Preparing for new cost structures: Atlassian will introduce a consumption-based pricing model for Forge apps starting in 2026. While this won’t affect your current subscriptions immediately, we’re making sure our apps remain efficient and cost-effective long term.
Frequently Asked Questions (FAQ)
Do I need to reinstall my SaaSJet apps?
No. Your apps will continue working during the migration. If any action is required in the future, we’ll let you know in advance.
Will my data move outside Atlassian?
Most processing happens within Atlassian’s infrastructure. In cases where external servers are used, they are fully owned and managed by SaaSJet, use encrypted HTTPS connections, and never share your data with third parties.
Will there be downtime?
We’re planning the migration to be seamless. If short maintenance is ever required, we’ll communicate it clearly and ahead of time.
What is the “Runs on Atlassian” badge?
This badge identifies Forge apps that run on Atlassian’s infrastructure, align with data residency, and minimize data egress. SaaSJet apps will begin earning this badge as migration progresses.
Will the way I use the app change?
No major changes to your daily use are expected. If new features or small interface updates arrive thanks to Forge, we’ll highlight them in release notes.
Who can I contact if I have more questions?
Our support team is happy to help: support@saasjet.com.