Atlassian has always given customers the tools to extend Jira, Confluence, and other products through plugins and apps. Over time, the extensibility framework has grown from Plugin2 (P2) for on-premise Server/Data Center, to Atlassian Connect for Cloud, and most recently, Atlassian Forge, their modern cloud app platform.
With Atlassian announcing the end-of-life timeline for Connect, many customers and developers are understandably anxious about what comes next. In this article, we’ll walk through a brief history of these frameworks, the features of Forge (architecture, hosting, security, extensibility, and developer experience), and how they compare to Connect. We also offer guidance on preparing for the transition and how to make it a positive experience for both customers and app developers.
From Plugin2 to Forge: A Brief History
Atlassian’s app extensibility has come a long way, starting with the Plugin2 (P2) for Jira and Confluence Server (and Data Center) apps. These apps allowed deep customizations but were limited to local deployments.
When Atlassian moved to the Cloud, they introduced Atlassian Connect, enabling developers to create apps that seamlessly integrated with Jira and Confluence Cloud through APIs, even though the code ran on external servers. Connect opened the door to a new way of extending Atlassian’s cloud products, offering flexibility for developers and businesses alike.
As customers and developers began to prioritize security, data privacy, better performance, and ease of use, cloud adoption increased. To meet these evolving needs, Atlassian reimagined its approach to cloud-native extensibility, and the result was Atlassian Forge.
Built with security, performance, and simplicity in mind, Forge lets developers focus on innovation while Atlassian takes care of hosting and infrastructure. Forge features built-in safeguards like tenant isolation and a streamlined development process, paving the way for better, safer apps.
While Connect has served us well, Forge is designed to meet the needs of today’s cloud-first world, offering an exciting new chapter for developers and customers alike. Now, let’s take a closer look at the features of Forge and how they compare to those of Connect.
Forge vs. Connect
Architecture and Hosting
Forge uses a serverless, Atlassian-hosted architecture. This means that when you build a Forge app, Atlassian takes care of hosting, scaling, and monitoring the app code. You deploy your app to Atlassian’s cloud, which is powered by AWS services behind the scenes, and they keep it running smoothly. With Forge, you can focus entirely on building functionality without worrying about servers or infrastructure. For your app’s UI, you can use Atlassian’s UI Kit for a streamlined experience or create a custom UI that Forge serves via Atlassian’s CDN.
On the other hand, Connect apps operate using a distributed architecture. They’re hosted externally (by you or your customers), which gives you the freedom to use any programming language or framework. However, with that flexibility comes responsibility. You’re in charge of hosting, scaling, maintaining high performance, and ensuring uptime. If your service faces issues, it impacts the app’s users within Atlassian Cloud.
Essentially, the biggest difference is that Forge shifts the infrastructure and operations burden to Atlassian. No need for load balancers, regional deployments, or multi-tenancy setup–it’s all handled for you. With Forge, development becomes faster, more secure, and all-around simpler. It takes care of the heavy lifting so you can focus on building great apps.
Security and Compliance
Security has played a big role in the move from Connect to Forge, and with good reason. Connect apps rely on external services to access your Atlassian Cloud through REST APIs and iframes. While secure when done right, the developer shoulders most of the security responsibility. Plus, Connect apps operate through a single access point, which, if compromised, could put customer data at risk. Multi-tenant Connect apps especially require careful design to safeguard customer data.
Forge takes a fresh, security-first approach. Built with a “zero-trust” philosophy, Forge apps run in a restricted sandbox within Atlassian's infrastructure. Each app installation is automatically isolated, meaning one customer’s data is completely separate from another’s. Authentication is handled via Atlassian’s hosted OAuth 2.0 integration, adding another layer of security.
Forge also comes packed with extra security and privacy features, like limited network egress, configurable data residency, and built-in marketplace security scanning. It simplifies security for developers and protects users at every step. While Connect has been a solid framework, Forge brings peace of mind with stronger, built-in protections.
Extensibility & UIs
Both Connect and Forge provide plenty of modules (extension points) to customize Jira, Confluence, and other Atlassian products, with things like Jira issue panel tabs, custom fields, workflow post functions, Confluence macros, content byline items, and more. However, there are differences in what you can extend and how.
While Connect has historically provided more extension points due to its longer lifespan, Forge is quickly closing the gap. It now supports most key modules, including issue panel tabs, custom fields, workflow functions, and more, with new features being developed exclusively for Forge.
While Connect has historically provided more extension points due to its longer lifespan, Forge is quickly closing the gap. It now supports most key modules, including issue panel tabs, custom fields, workflow functions, and more, with new features being developed exclusively for Forge.
One standout feature of Forge is its ability to create rich, dynamic UIs that feel native to Atlassian products. While Connect apps rely on iframes and external services, Forge focuses on a modern, cloud-native approach with enhanced security. Forge also simplifies development by managing infrastructure and authentication, letting you focus on building great apps. While some legacy or niche Connect modules may not make it to Forge, Atlassian is prioritizing the most valuable capabilities for developers.
Advanced Automation
Another impressive feature is Forge’s ability to create advanced automation tools, like Rovo agents. These agents can handle complex workflows, respond to events in real-time, and integrate with external systems, all while running securely in Forge’s serverless environment. Rovo agents are a great example of how Forge’s advanced tools can boost efficiency and spark innovation by automating tasks across the Atlassian ecosystem.
External Integrations
Regarding external integrations, initially, Connect had the upper hand, thanks to the freedom to call APIs or databases directly from your app server. But Forge has caught up with features like web triggers, Forge Fetch for calling third-party APIs, and Forge Remote, which lets your app connect to external services or use an existing backend. If you’ve built a complex service for a Connect app, you don’t have to abandon it; you can transition parts of your app to Forge while still leveraging your existing setup. Atlassian also shares a public Forge roadmap to keep developers updated on upcoming features, including those aimed at bridging gaps with Connect.
Marketplace Apps
For Marketplace vendors, Forge makes life easier by cutting costs and reducing DevOps work. Atlassian covers infrastructure expenses (Forge is free for now, with any future pricing expected to be tied to usage) and handles app distribution, including data residency and compliance. It’s like having Atlassian as your Ops team, so even small developers can build apps without needing a full cloud setup.
Atlassian Connect End-of-Life Timeline and Phases
In early 2025, Atlassian announced a phased End-of-Support timeline for Atlassian Connect. Here’s a breakdown of key milestones and dates leading up to Atlassian sunsetting Connect:
- Starting today: 95% of Connect apps can start moving to Forge (including only functionality that is supported by Forge).
- September 17, 2025: You can no longer deploy new Connect apps to the Atlassian Marketplace (private apps not affected).
- End of 2025: Goal is that 100% of Connect apps should be able to be supported by Forge.
- March 2026: No new updates to Connect apps will be allowed in the Atlassian Marketplace. Installing new Private Connect apps will no longer be allowed.
- Q4 2026: Atlassian will officially end support for Connect. Connect apps will continue to run, but will be “use at your own risk.” After this date, no new app versions will be released using Connect.
Image Source
Moving Forward with Forge
The transition from Atlassian Connect to Forge is a big step, but it’s packed with opportunities to enhance your apps and streamline development. Forge brings simplicity, security, and innovation to the forefront, making it easier than ever to build powerful solutions.
If you’re unsure about the next steps or how to prepare, Praecipio is here to support you. Reach out to our team, and we’ll help you make the move to Forge smooth and successful.
