With Atlassian’s upcoming usage-based pricing model for Forge taking effect in January 2026, our team in TNG is evaluating how to adjust our apps’ pricing structures accordingly. While our current costs remain under control, we anticipate increases as more customers migrate to Cloud and want to establish a sustainable pricing approach proactively.
We’d appreciate insights on how other developers are approaching this transition:
- Are you implementing preemptive price adjustments based on projected usage increases?
- Are you following a “wait-and-see” approach and updating your prices accordingly later on?
- Are you developing more sophisticated pricing models that directly correlate with Forge resource consumption?
A particular challenge we’re facing is cost distribution fairness. Our Developer Console metrics reveal that evaluation licenses account for over 50% of our Forge Functions-compute costs, despite generating zero revenue. We’re hesitant to pass these free-tier costs to paying customers. We really value discussing strategies to decouple evaluation license costs from paid user pricing and strategies for maintaining profitability while offering evaluative access.
We welcome perspectives from teams navigating similar challenges as we collectively adapt to this pricing shift.