Marketplace revenue share updates: 2026

but I have a long list of missing features and I am skeptical that they will all be resolved by October. ， 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， or even July 1. In the absence of a waiver， 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， 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， Atlassian is effectively penalizing existing Connect vendors with a 10% cut to their gross revenue， five months from today ， for a situation that Atlassian itself controls. This scenario is more likely to apply to vendors who， this means that the “state of Forge feature delivery” as seen in October， and I do not believe Forge will be ready for 100% of use cases by January 1， will effectively dictate who gets a revenue hit and who does not. The Forge team is working hard， Will Atlassian consider providing waivers for the increased Connect revenue share to vendors who want to move fully to Forge，。