We’ve recently announced updates to Marketplace revenue share rates starting January 2026. These changes will allow partners to keep more of what they earn as they grow on Forge and better align incentives with Atlassian’s strategy and direction.
Update #1: We are introducing a new revenue share incentive to help partners establish successful apps on Forge.
Beginning 1 January 2026, partners will pay 0% revenue share for eligible Forge earnings, up to $1 million in lifetime Forge revenue. Lifetime revenue is calculated across all Forge apps owned by a partner, from the date eligible apps begin earning revenue on the Marketplace.
Update #2: We are also introducing new Marketplace revenue share rates that will go into effect 1 January 2026. Percentages reflect the commission amount retained by Atlassian, with remaining earnings paid out to the partner.
The rate for Connect apps will increase to 20% and subsequently increase to 25% on 1 July 2026.
The standard rate for Forge apps will increase to 16% and subsequently increase to 17% on Jul 1, 2026
How is a Connect on Forge app designated within this context? Is it a Connect App or a Forge app? I am asking for the purposes of both updates. Please answer each independently.
For update 1, with existing apps, does that mean all Forge apps get their NEXT 1 million free?
I understand the 0% revenue share on the first $1M is temporary, with 6 months notice before changes.
What about the standard rate (16% then 17%)?
Is it also subject to change at any time, or is there a fixed commitment period like the 2-year guarantee we had in the past?
When are you going to start counting “lifetime Forge revenue”? Is Forge revenue in 2025 and before already considered for the $1M bonus? Or will it start on 1 Jan 2026? If it starts before 2026, we will probably wait until Jan 2026 to move our Connect apps to Forge in order to utilize the full bonus.
Have you considered that Forge is still far from having parity with Connect? What are we supposed to do with apps that have a few (or even just a single) Connect module that we’re unable to move to Forge on Jan 1 2026 because of Forge limitations? It’s going to be a tough decision between taking features away and giving up on the 4% (later 8%) revenue share difference.
How do you justify raising the Forge revenue share, while at the same time charging for the pretty much mandatory move towards the Forge platform with Forge pricing?
Can you share a longer-term vision how the revenue share is going to evolve in the future? It’s probably not going to stop being increased to 17% and we’ll have to expect further increases to 20-25% in the years to follow?
What are we going to tell our customers if our apps will have more incidents on Forge than previously on Connect (search for Forge here vs. Connect)? Could you please release a blog post or other public document that summarizes all the different changes and incentives for partners regarding the move from Connect to Forge? That would make it easier for us to point out to our mutual customers why we’re making all of these changes and why there might be speed bumps along the way.
Just to be clear: the revenue share changes of Forge apps are on top of the Forge pricing which will also go in effect on Jan 1, 2026
Which means that vendors switching from Forge to Connect not only pay 2% more revenue share, but in many cases also more usage costs compared to other hosting options (GCP, AWS, Heroku, a $5 VPC, etc) for a platform that often delivers less performance and less features.
That’s one hell of a sales pitch you’ve got there!
we would love to take advantage of the revenue share incentive. We have built all our apps with Forge, but we use a single Connect module because there is no Forge alternative.
FRGE-208 (indexed content properties) is one of the feature requests with the most upvotes and has been “in progress” for more than three years. However, we haven’t received a progress update since then, and the feature is not included in the Connect Equivalence Roadmap.
At the moment, the revenue share updates are not an incentive for us, but a 5–10% penalty for using a feature that has no alternative.
I think these changes should only go into effect when more Connect capabilities are available in Forge and partners had enough time to migrate their apps.
Yes, you can use Forge Remote, but your app will not qualify for Runs on Atlassian (RoA). We have a lot of apps that are very suitable for RoA, yet will incur a lot more costs compared to our current infrastructure
Will Atlassian consider providing waivers for the increased Connect revenue share to vendors who want to move fully to Forge, but who cannot because the Forge team cannot deliver the features required to make their apps work?
Forge still has plenty of missing functionality compared to Connect, and I do not believe Forge will be ready for 100% of use cases by January 1, or even July 1.
In the absence of a waiver, Atlassian is effectively penalizing existing Connect vendors with a 10% cut to their gross revenue, for a situation that Atlassian itself controls. This scenario is more likely to apply to vendors who, in relative terms, have the most complex apps and the most integration with the ecosystem. (Is this really the set of vendors that Atlassian wants to alienate?)
The deadline is even closer than one might think: to be able to launch a new version of an app by Jan 1, vendors still need time to analyze, build and test whenever needed functionality is finally released on Forge that needs to be converted from Connect.
If it takes an average vendor two months to do this, this means that the “state of Forge feature delivery” as seen in October, five months from today, will effectively dictate who gets a revenue hit and who does not.
The Forge team is working hard, but I have a long list of missing features and I am skeptical that they will all be resolved by October.
I would go as far as saying that this is moving Atlassian a lot faster towards an EU Digital Markets Act violation complaint, and I’m also keen to hear from Atlassian legal how they look at the latest development in the Apple VS Epic Games legislation.
Atlassian is threading dangerous grounds here, and it is really pushing the envelop to a point at which it should not look surprised when Atlassian Marketplace Partners will look for legal action.
Transitioning Connect apps to Forge can require investment, and we are introducing a new incentive to stimulate innovation and offset costs. Starting 1 January 2026, partners will pay 0% revenue share on eligible Forge earnings until reaching $1 million in lifetime Forge revenue.
It does require investment, but it also requires a sense of security, which is eroding at the record pace due to Atlassian’s active expansion into the territory, which is traditionally covered by third-party apps. Imagine having your team putting months of work (while halting actual product and feature development) on migration to Forge in order to discover that Atlassian has decided to implement natively the same functionality as provided by your app.
Forge apps with revenue earned before 1 January 2026
A partner owns two Forge apps that have been on the Marketplace for 2 years. One has earned $50,000 in revenue and the other has earned $100,000 in revenue as of 31 December 2025.
The partner will pay the standard Forge revenue share on the $150,000 earned through 31 December 2025. As of 1 January 2026, the partner’s lifetime Forge revenue will be tracked at $150,000. The partner will pay 0% revenue share on $850,000 in earnings from their Forge apps after 1 January 2026, up to total partner lifetime Forge revenue of $1 million.
Is this a blunder or a mixup? Why would you consider the 150K that has revenue share paid as part of the 1M lifetime earnings at 0%?
Basically put, if the app has any revenue before Jan 1rst 2026, you’re losing out on the 0% revenue share incentive.
I would have expected the 150K of paid revenue share be excluded from the 1M, not included.
Hi all, Thank you for the questions about how the new rates will apply. Addressing those below.
How do revenue share rates apply for Connect-on-Forge apps? Are they eligible for the 0% incentive?
A: Connect-on-Forge apps receive the Connect revenue share rate because they contain Connect modules. For the same reason, Connect-on-Forge apps are not eligible for the 0% incentive.
I’m also seeing multiple questions about lifetime Forge revenue and the 0% incentive:
With existing apps, does that mean all Forge apps get their NEXT 1 million free?
When are you going to start counting “lifetime Forge revenue”? Is Forge revenue in 2025 and before already considered for the $1M bonus? Or will it start on 1 Jan 2026?
A: Lifetime Forge revenue starts being counted when your eligible (ie only have Forge modules) apps begin earning money on the Marketplace. If you have Forge apps that have already earned revenue in 2025 or before, that’s included in your lifetime Forge revenue. When the 0% incentive starts on January 1, 2026, it’ll apply to any Forge revenue you earn from that point forward, until you reach $1 million total lifetime revenue (in other words, $1 million - lifetimerevenue already earned).
Our concerns have been highlighted very well by others above. Two things I’d like to add:
Forge currently does not natively support collecting traces (something I inquired about more than a year ago). Functions run like a black-box, making us hesitant to run any code on Forge with production workloads.
Our Connect app uses OAuth2 to connect to an external system, asApp which is not available on Forge. I have talked to Atlassian about this gap since Sep 2021, when providers were launched (close to 4 years ago), and came up with workarounds that I am not comfortable shipping to production (mostly with security implications for Forge users).
To @ChrisHemphill1 and the Atlassian decision-makers who came up with this plan: I’d like to understand what led you to the conclusion that partners on Connect should be financially punished for not moving to Forge by January 2026.
To be clear on our position: We have been trying to migrate from Connect to a Forge native app for many years (3+), we are on board with this, but every now and then it feels some people at Atlassian are on a different boat.
Also, AFAIK, there is no way to run integration tests in Forge against real Atlassian product. Which is absurd thing to ignore when you have to rewrite the code base from a safer language (e.g. Java) which is covered by good amount of automated tests to a less safe scripting language with a lot quirks (technically TypeScript, but it’s essentially JavaScript).
And alternative runtime support (with a “blocker” priority FRGE-1472, ROADMAP-55) is set for EAP only in early 2026, which contradicts the unrealistic timeline set here for Forge migration to even consider it, and it doesn’t seem to address testability aspect at all.
I would only postpone the last connect module. as long as you have one connect module, you are not eligible for the Forge 0% incentive, but it does set you up to become eligible in the minimum time needed as you only have a single module to migrate.
You can even migrate all the modules on your development and staging environments. Then when its Jan 1st, deploy to production and become eligible.
This maximises the use of the 0% incentive while at the same time minimise the impact of the higher rev share fro connect-on-forge.
The problem is that if you gradually remove Connect modules, when you remove the Connect remote (finally becoming Forge app), this will trigger a major upgrade - Minor version updates (Connect to Forge) (Preview)
So it is better to go full to Forge in a single upgrade, which will not trigger a major upgrade.