Let’s be perfectly clear here and not beat around the bush: Forge is not an “option” for vendors. Although there might not be an end date yet, it is well known within the Marketplace Partner community that Atlassian has every intention to sunset Connect.
There is no need for a pricing model, as there is nothing to compete with. If Atlassian cannot make Forge work within the context of the revenue share model, you will seriously need to re-consider your strategy.
This particular sounds really scary and messy to me.
I get that it is tempting to say “we’ll use revenue share model to have partners collectively pay for basic infrastructure and X free tier and add a usage-based pricing model to prevent abuse” but that is just going to make it very fussy.
Also, although I fully understand that Atlassian can’t compete with other hosting solutions like Cloudflare in terms of pricing because the number of customers for Forge infrastructure is pretty limited as it is only geared towards Atlassian developers and not… like… the entire world, I have to be completely honest: that’s on you. You choose to remove alternative options from vendors by promoting (and highly likely eventually forcing) the use of Forge.
So again, please do not create a highly complex mix of revenue share and usage-based pricing. If existing revenue share and your own strategic investment into Forge cannot cover the cost, I can only say that maybe It’s time to start being open to the idea that Forge may have been a mistake