Disclosure first. I am Fabian Aguilar from Maplesprint, a new Marketplace partner. I read the public Marketplace catalog every day and keep the history, and the numbers seemed worth sharing on their own, so this article is the data, the method and a checklist.
What Atlassian has said
- Since March 2026, Marketplace apps with a Connect descriptor can no longer receive updates.
- On 31 January 2027 (extended from December 2026), Connect reaches end of support. After that date Atlassian addresses only critical security vulnerabilities, deprecation windows get shorter, and Atlassian expects breakages to become more frequent. (Source: Atlassian's "Getting ready for Connect end of support" post.)
- Nothing switches off on that date. Apps keep running; the risk moves to you.
The numbers (as of 23 October)
Counting only apps for Jira and Confluence:
- 6,674 cloud apps are listed, and 919 of them (13.8%) are still flagged as Connect: 628 for Jira only, 274 for Confluence only, 17 for both.
- That is down from 1,247 on 23 September and 955 on 15 October (earlier manual counts of the same scope, so read the trend as indicative), and from 923 two days ago.
- Together they hold 245,627 installations, 12.8% of all installations in that slice of the catalog. Installations are added up per app, so an organization with ten apps counts ten times.
- Concentration is high: the ten most installed Connect apps hold 48.6% of those installations.
- 35 Connect apps have 1,000 or more installations, and 23 of them have not published a release in 12 months.
- 16 Connect apps with 500 or more installations have not published since 2022 or earlier.
- For release dates, I only trust the 265 Connect apps with 100 or more installations, because I re-read each of those one by one. Of them, 188 (71%) have no release in the last 12 months, and 49 have a release dated 1 March 2026 or later.
A note on another count
Mikhail "in Peru" published a Connect check for Confluence admins earlier this week and counted from the same public API: 6,723 cloud apps, 999 on Connect, and 952 of those with no release since March. I think we agree more than the headline numbers suggest. His first two figures match mine when I count all products rather than only Jira and Confluence (6,740 cloud apps and 998 on Connect on 19 October; 6,795 and 993 on 21 October, including 70 Bitbucket apps). The scope and the day explain the gap. On releases, his 47 apps with a release since March is the same number I found on 21 October among the apps with 100 or more installations (49 today); my count across all Jira and Confluence Connect apps is 70 today because smaller apps add 21, and their dates are less reliable in the bulk listing, which I found carries outdated version data for about a quarter of apps until each one is read individually. I do not know his method, so take this as a question, not a correction; I would be glad to compare notes. What matters is that both counts say the same thing: almost all Connect apps are quiet, in line with Atlassian's statement about descriptors. About 30 apps show a release dated April or later; public data does not tell me why.
What this does and does not mean
A quiet app is not necessarily abandoned, and a Connect app will not stop working on 31 January. Migrations are also incremental: an app can be flagged as Forge in the Marketplace and still carry Connect modules, which is why an admin banner may keep showing for it. One detail that surprises admins: even when the vendor has already shipped a Forge version, your site keeps running the old version until an admin accepts the update.
What admins see in Connected apps
According to Atlassian's "What admins see" page, and as Sami Shaik laid out in an earlier article (Atlassian is rolling the banners out gradually, so your site may not show them yet):
What you see | What it means | What to do |
|---|
No banner | A Forge-only app (or the rollout has not reached your site yet) | Nothing |
Yellow, "update your app now" | The vendor already shipped a Forge version; your site runs an older one | Review the new permissions and accept the update |
Yellow, "unsupported after January 2027" | Still Connect, no migration plan declared | Contact the vendor through its Marketplace listing |
Blue, with the vendor's plan | The vendor declared that it will migrate | Read the plan |
Yellow, with the vendor's plan | The vendor declared "undecided" or "no" | Read the plan and ask the vendor |
What an admin can do this week
- Open Connected apps in Atlassian Administration and note every app with a banner or an update prompt.
- List every Marketplace app installed on each site, including the ones nobody remembers installing.
- Accept the pending updates that your review allows.
- For each app still on Connect, ask the vendor for a Forge migration date, in writing for anything business-critical.
- For vendors that cannot commit, shortlist alternatives now. A replacement takes weeks to evaluate and roll out.
- Re-check every week; the numbers change fast.
The data in detail (as of 23 October)
Apps still on Connect (Jira and Confluence) | Apps |
|---|
Jira only | 628 |
Confluence only | 274 |
Both | 17 |
Total | 919 |
Most installed apps still on Connect | Vendor | Installs | Last release |
|---|
Figma for Jira | Figma | 48,351 | 2025-08-19 |
Sentry for Jira | Sentry | 16,302 | 2026-03-30 |
Miro for Jira Cloud | Miro | 12,250 | 2024-03-08 |
Google Chat for Jira Cloud | Google LLC | 11,008 | 2021-11-11 |
Clockify: Time Tracking & Timesheet | CAKE.com | 8,748 | 2023-05-18 |
Azure DevOps for Jira (Official) | Atlassian | 6,889 | 2025-11-28 |
Zeplin for Jira | Zeplin | 4,653 | 2023-01-03 |
Statuspage for Jira Service Management | Atlassian | 3,930 | 2025-09-23 |
Render Markdown | StreamlineSoft | 3,853 | 2021-10-26 |
Adobe XD for Jira | Adobe | 3,501 | 2021-09-28 |
A last release date is not a verdict. It is a reason to ask the vendor.
How I counted (so you can check your own apps)
The public Marketplace REST API returns, for each cloud app, the deployment details of its latest version, including whether it is a Connect app. I read the whole Jira and Confluence cloud catalog once a day, and for every app with 100 or more installations I re-read the app individually, because the bulk listing can carry outdated version data. To check one app by hand, open its Marketplace listing and look at the release history, the "Runs on Atlassian" badge (Forge only, although not every Forge app qualifies), or ask the vendor. Three caveats: the flag describes the vendor's latest version, not necessarily the one installed on your site; hybrid apps (a Forge manifest that still carries Connect modules) are flagged as Forge; and installations are added up per app.
I will share the next snapshot at the 90-day mark. If any number looks wrong, tell me in the comments and I will correct it.
