We’ve always been on a journey of growth at Revyz, and that journey has brought us to a significant milestone: the migration of our apps from Atlassian Connect to the Atlassian Forge platform. While our apps have evolved from "Data Manager" to "Command Center," this move from Connect to Forge is more than just a name change; it's a fundamental shift in our architecture that aligns with Atlassian's future and, most importantly, provides a more secure and reliable experience for you, our customers.
The Strategic Imperative: Why We're All In on Forge
Atlassian has made its position clear: Connect is a legacy framework, and Forge is the new, preferred platform for building cloud apps. The End-of-Support (EOS) for Connect is a non-negotiable timeline, culminating in the cessation of all support by Q4 2026. The most critical deadline for us and other vendors is March 2026, after which Atlassian will no longer permit updates or patches to apps that rely on the Connect framework. This means that any app still on Connect will become a technical liability, unable to receive essential security and bug fixes. For us, continuing to develop on Connect would be a disservice to our customers.
Beyond the end-of-life dates, the migration is driven by a powerful business imperative: the demand for enhanced trust and compliance from the enterprise market. Forge was specifically designed to meet the rigorous security, compliance, and performance needs of modern enterprise customers.
The Technical and Business Advantages of ForgeThe shift from Atlassian Connect to Forge represents a move from a traditional, vendor-managed hosting model to a modern, serverless, Functions-as-a-Service (FaaS) model. This change offers a host of technical and business benefits.
Unparalleled Security and Compliance:
While Forge's Zero Egress by Default architecture is a great general policy for data privacy, it is not applicable to how Revyz operates. For our data backup and restore functionality, no enterprise customer would want their backup data in the same location as Atlassian's core services. From a risk management perspective, we believe in distributing, not concentrating, points of failure.
Similarly, while Forge offers native data residency, Revyz goes a step further by providing customers with the ability to store their data in their own public cloud infrastructure, whether it's AWS or Azure, and in the specific region or data center they prefer.
Because our data handling needs require egress for backups, the "Runs on Atlassian" badge, which is predicated on a zero-egress model, is not applicable to our specific app.
Simplified Management and Operations:
Forge helps simplify and harden authentication by providing managed APIs, which eliminates the complexity of managing JSON Web Tokens (JWT) that was required with Connect. While some operational costs are shifted, this benefit is not the primary driver for our migration, which is a strategic decision for the long-term health of our applications.
Faster Development and Deployment:
Forge automatically manages development, staging, and production environments. More importantly, minor updates and patches can be rolled out automatically and quickly—often within minutes—without requiring customer callbacks or manual administrative interaction. This is a massive improvement over the Connect update process and ensures you receive fixes and new features almost instantly.
Navigating the Road Ahead: Our Migration Strategy
The migration from Connect to Forge is not a simple lift-and-shift; it required a fundamental re-architecture of our apps. We adopted an "Incremental Adoption (Connect on Forge)" strategy, a hybrid model that allowed us to leverage Forge’s immediate benefits—like simplified deployment and enhanced security—while systematically transitioning our core, complex functionality. We are happy to say that we have now achieved full feature parity with our legacy Connect apps and are now moving off the Connect on Forge interim step to fully Forge.
For you, this means a smooth transition. The application is registered as a Forge app, allowing it to receive the critical benefit of faster, non-admin-approved updates, while still retaining its full functionality. We have successfully navigated the technical challenges, such as adapting long-running tasks to Forge’s 25-second function limit and migrating our data models to the new serverless storage options.
The Future is on ForgeThe decision to migrate to Atlassian Forge is a strategic commitment to our customers and to the future of our applications. By building on Forge, we are ensuring our apps remain at the forefront of the Atlassian ecosystem. This transition allows us to continue our mission of providing you with a single, powerful "Command Center" for all your data security, compliance, and administrative needs, all while providing a more robust and future-proof platform.
