A Developer Space is your team’s shared space for building, managing, and billing Forge apps. This page explains how billing works for a Developer Space, how to add a payment method, how automatic payments and invoices work, and what happens if you don’t add a payment method.
Developer Spaces and Forge platform pricing are not currently supported for Atlassian Government Cloud or Isolated Cloud environments.
Read our docs for an overview of Developer Spaces. For pricing details and free thresholds, visit Forge platform pricing. To understand space-level roles and permissions, review Developer Space roles.
Billing for Forge usage is managed at the Developer Space level:
Key points:
One transaction account per Developer Space: Each Developer Space is linked to a billing (transaction) account that lives in the Billing Console. Space admins can see the billing status from the Developer Space Settings page.
Monthly billing cycle and autopay: Invoices are generated on the first day of each month, covering usage from the previous month. If you’ve added a valid payment method, an automatic payment (autopay)- is attempted on the first of each month for the total invoice amount.
Free usage threshold: If your total usage for all apps in the space stays within the free threshold, your total monthly cost is $0. Learn how the free threshold works and what’s included in the Forge platform pricing.
To be charged for Forge usage above the free threshold, your billing account needs a valid payment method.
You’ll need:
Billing administration is managed in the Billing Console. From a Developer Space, you’ll use shortcuts to open the relevant billing account.
To learn how to set up your Developer Space before configuring billing, read our docs on how to create and manage Developer Spaces.
In the Developer Console, open the Developer Space you want to manage.
If billing has not been set up, follow the prompts in the developer console to review terms if applicable and add the payment method.
You can also go to Settings for the space, and select Go to Billing Console. Next, in the billing account:
a. Go to the Payment methods section in the left navigation.
b. Select Add payment method.
c. Choose one of the supported options (for example, credit card, debit card, PayPal, or ACH, depending on your region).
d. Enter your billing details and save.
After you’ve successfully added a payment method:
You can open the billing account that backs your Developer Space directly from the Developer Console.
From the Developer Console:
In the billing account, you can review subscriptions, usage, invoices, and payment methods for the apps in that Developer Space.
The billing account (Billing Console) provides a left navigation to manage and review your charges.
| Left-hand nav sections | Description |
|---|---|
| Subscriptions | See all active subscriptions related to your Forge usage and related products. From here, you can open a subscription to see detailed usage and charges. |
| Billing profiles | Update your organization name, billing address, and (where applicable) shipping address used on invoices. |
| Payment methods | Add, update, or remove payment methods used for auto-payment. Only billing admins can change payment methods and billing profile details. Other roles may have read-only access, depending on your organization’s configuration. |
| Addresses | View or edit your billing address and sold-to address. |
| Billing permissions | Add another billing admin. |
| Invoices | Download invoices, review previous charges, and confirm whether an invoice has been paid. |
Once you’ve opened your billing account, you can drill into subscriptions and usage.
To see how your usage changes over time:
Learn more about usage metrics and charts.
Once a payment method and billing details are set up:
What happens next depends on your usage and payment setup:
Billing admins can download invoices and see payment status in the billing account.
You may choose not to add a payment method right away. The impact depends on whether your apps stay within the free threshold or exceed it.
Scenario 1: Apps stay within the free threshold If the combined usage of all apps in your Developer Space stays within the free threshold:
No payment is required. Your total charge for that billing period is $0.
Invoice behaviour:
You can continue to use your apps in the Developer Space as long as your total usage remains within the free threshold.
Scenario 2: Apps in the developer space exceed the free threshold (cost > $0). What happens then depends on your billing setup.
When required billing details are missing If there’s no valid payment method or required billing details (for example, missing billing address) in the billing account:
Invoice generation can fail. The system attempts to generate an invoice, but if required billing information is missing, invoice creation or payment can fail.
Dunning is triggered. When invoice generation or payment fails, the billing system moves the apps into a dunning state:
After the dunning period If the issue is not resolved after the dunning period:
To avoid dunning and enforcement:
Add a valid payment method and required billing details before your usage exceeds the free threshold.
Keep your payment method up to date so automatic payments can succeed on the first of each month.
To reduce billing friction for your team and your customers:
Set up billing early Add a payment method and billing details when you first create or start using a Developer Space, even if you expect to stay within free thresholds.
Learn how to monitor usage, and utilise the View usage charts in your billing account to track how close you are to thresholds.
Review invoices and payment status Make sure billing admins check new invoices and payment status each month, especially after significant increases in app adoption.
Keep billing admins up to date Ensure the right people are assigned as billing admins in the Billing Console, and that contact details and email addresses are correct, so they receive billing and dunning notifications.
Rate this page: