It is not ideal no, but you can migrate all modules over to Forge, and end up with a not used remote. Then you can remove the remote at the end and start instructing people in the UI to update.
Ideal no, but it is doable, at least in my case and cases others shared with me.
Would this jump from 15% to 25% for the marketplace make vendors consider dropping the Pay via Atlassian program?
Is pay via vendor (e.g. paddle.com) still viable under forge/run with atlassian?
No, it is not allowed per the Atlassian Marketplace Agreement (art. 3.1):
Paid-via-Vendor Apps may not be Cloud Apps, Data Center approved Apps, or any Apps you develop using Atlassian Connect or Forge, unless Paid-via-Atlassian Apps is not available for that product or is otherwise permitted by Atlassian in writing.
But given the recent ruling in Apple vs Epic Games, this might no longer be sustainable.
3 Likes
Hi Chris,
A honest question. Are you trying to incentivize partners to migrate to Forge today or in 2026? Because it sounds like you are trying to do first but actually doing second.
I think the most sensible option would be to set any amount earned from 1st Jan 2026 onwards to qualify for 0% incentive.
If it stays like as it is, we are definitely not hurrying to migrate to Forge this year.
5 Likes
With each new unrealistic timeline announcement it’s increasingly clear that there is severe internal miscommunication on the readiness of Forge.
The bridge is incomplete while you’re telling cars that it’s safe and they’ll be fined if they don’t drive ahead.
8 Likes
My app only use Forge modules with Forge Remote Connect backend. In our backend, we authenticate to external systems using OAuth2. Will this be eligible for Forge eligibility requirements?
FYI we have one app 100% ported to Forge and fully tested on staging environment. However, we decided to not release it. Why?
Because we do not see much upside by releasing the Forge version now and losing chunk of 0% incentives. Instead we will wait till December and hit the release button.
We are early adopters of Forge and this policy essentially penalizes us for taking risks on platform that was not ready.
10 Likes
With the current incentives I’ll be shelving any conversions to connect on forge, there is no financial benefit. We will be concentrating on full forge conversions or new Forge apps. We will be trying to release any Forge stuff as close as possible to 1 Jan as possible. I suppose any conversions could be to a connect on forge app with a single connect module that doesn’t do anything. Then on the 1st Jan, convert to full Forge
@ChrisHemphill1 If we convert a connect app to Forge and 99% of users are on the connect version (haven’t upgraded) then is all revenue (including that from the connect version) still at 0% or only those that upgrade to Forge?
3 Likes