Upcoming change
Pricing takes effect on January 1, 2026. Until then, Forge is free to use within platform limits.
Read the blog post for more details.
Forge uses a consumption-based pricing model, offering most capabilities for free within generous monthly usage limits. This page is the source of truth for current Forge pricing and will be updated as needed.
Forge platform pricing is not currently supported for Atlassian Government Cloud or Isolated Cloud environments.
| Capability | Unit | Free usage allowance (monthly) | Overage price per unit ($USD) |
|---|---|---|---|
| Forge Functions: Duration | $/GB-seconds | 100,000 GB-seconds | 0.000025 |
| Key-Value Store: Reads | $/GB | 0.1 GB | 0.055 |
| Key-Value Store: Writes | $/GB | 0.1 GB | 1.090 |
| Logs: Writes | $/GB | 1 GB | 1.005 |
| SQL: Compute duration | $/hr | 1 hr | 0.143 |
| SQL: Compute requests | $/1M-requests | 100,000 requests | 1.929 |
| SQL: Data stored | $/GB-hours | 730 GB-hours | 0.00076850 |
Note: Empty KVS reads count as 1KB towards your usage, whereas non-empty reads are based on actual size. While we may consider a future update to apply this 1KB minimum to all reads under 1KB, the current policy applies only to empty reads. We will provide advance notice prior to adopting any changes.
Suppose your Forge app uses the following in a single month:
Here’s how your monthly charge would be calculated:
Compute functions (Forge Functions: Duration)
Key-Value Store Reads
SQL: Data stored
Note: SQL storage is billed based on the total amount of data stored, measured hourly and summed over the month (GB-hours). You are not billed based on the amount of data read or written, but on the cumulative storage held each hour.
At the start of each new month, your SQL storage usage calculation continues from the amount of data stored at the end of the previous month. If you have not deleted any data, your hourly storage “snapshots” will begin at this higher baseline, and your total GB-hours for the new month will accumulate more quickly. To reduce future charges, consider deleting unneeded data before the next billing cycle begins.
Total monthly charge:
$1.25 (compute) + $0.00275 (KVS reads) + $0 (SQL data stored) = $1.25275
This example shows how charges are only applied to usage above the free monthly allowance for each capability, and how multiple capabilities can contribute to your total bill.
Use the Forge cost estimator to preview potential monthly charges based on your app's projected usage.
You can monitor usage metrics and cost for your Forge apps in the Developer console. This helps you:
To view your app’s resource usage and costs:
When does billing start?
Billing starts on January 1, 2026. Before this date, any Forge usage up to platform quotas and limits is free.
What do I need to do before billing begins?
Once pricing takes effect, you’ll need to provide billing details to continue using Forge. Instructions will be shared in the Developer Console. To avoid service interruptions, ensure you add a payment method.
How does the free usage allowance work?
The free usage allowance is per app, per month. Each app receives its own quota for each billable capability. Usage above these thresholds will be billed monthly in arrears.
Can I keep using Forge for free?
Yes, if your app remains within the monthly free usage allowance, you won’t be charged.
How does billing work for multiple apps or organizations?
Billing is consolidated into a single monthly invoice for all apps managed by an individual, partner, or customer. Each app benefits from its own free usage allowance, which is not shared across other apps.
Which Forge capabilities will be charged for?
At launch, the following capabilities will be charged above the free threshold:
Other capabilities not listed here, such as using Connect on Forge modules or remote capabilities, will remain free.
What makes Forge a valuable choice for building on the cloud?
Forge pricing reflects not just raw compute/storage, but also value-added features like data residency, customer compliance features like BRIE and BYOK, support for regulated environments like Atlassian Government Cloud, and integrated billing/discovery.
Will there be differences in pricing for public vs. private apps?
No, the same thresholds and pricing apply to both public Marketplace apps and private/internal apps. However, to create a sustainable business, pricing has to be calibrated to current market conditions, and there are many variables that can change over time. These include pricing for the services Atlassian consumes to deliver Forge. We will always endeavour to price competitively and will review pricing periodically (much like Atlassian does for its flagship apps). Changes to pricing and or the introduction of new capabilities will be announced at least 3 months in advance.
What support and SLAs are available for paid usage?
Apps exceeding the free tier will be eligible for enhanced support and SLAs, including 99.90% uptime for Compute, KVS, and SQL. Service credits are available if uptime falls below thresholds. Find more details in the Forge Service Level Agreement.
Why is Forge introducing pricing?
Introducing pricing for Forge creates a sustainable economic model that enables continued investment in the platform. This approach ensures we can deliver new capabilities and features that help partners grow and strengthen their businesses.
Where can I find more information or get help?
Atlassian will continue to update partners via official communications and provide detailed documentation and support as the pricing model rolls out.
Rate this page: