Frequently Asked Questions (FAQ) AI Apps Builder

AI Apps Builder is a free Jira app available on the Atlassian Marketplace. After installation, each user receives 50 credits to explore the product and create custom apps. Credits are used when sending messages in the AI chat. For details on the credit system, see Understanding Free Tier Usage Limits in AI Apps Builder.

Yes. AI Apps Builder has a standalone web version that lets you generate and preview apps entirely outside your Jira environment. You can build, iterate, and confirm everything works as expected, then install the finished Forge app into Jira when it's ready. This option is particularly relevant for teams with strict policies around installing third-party tools directly in their Jira instance.

You need to use your API token to deploy the app created with AI Apps Builder. The token is used only to authorize the installation of the generated Forge app to your specific Jira Cloud site.

The API token:

• Is used only for deployment

• Is not stored by AI Apps Builder

• Is not used to access Jira data

• Is not used at the app’s runtime

• Is not used for analytics or data collection

• Does not affect the app after deployment

Once deployment is complete, the app runs independently as a standard Forge app within your Jira environment. It does not rely on the API token in any way.

If the API token expires or is revoked, the deployed app will continue to function normally.

The token is simply a secure authentication mechanism required by Atlassian to authorize app deployment.

Yes. If your organization prefers to keep the deployment process fully under your own control, you can use manual deployment instead. Download the Forge installer, deploy the app yourself using the Forge CLI, and the API token never passes through the AI Apps Builder interface. This gives teams the flexibility to match their internal security policies.

No. The API token is required only during deployment. Once your app is successfully deployed, it will continue working even if your API token expires or is removed. The API token's lifetime does not affect your app's lifetime.

To deploy the Forge app generated with AI Apps Builder, you must have administrator permissions on the Jira site where the app will run.

No. When you use AI Apps Builder to generate a custom Jira app, the AI reads your prompt and generates a Forge app based on Atlassian's Forge documentation. It does not connect to your Jira issues, projects, or data. You never need to grant AI direct access to your Jira instance.

No. Neither Anthropic (the AI provider behind AI Apps Builder) nor the AI Apps Builder team uses your prompts or generated outputs for model training. What you describe to generate an app does not feed back into improving the model. This means describing your internal processes or workflows to build a custom app does not expose that information to future users of the system.

Apps generated with AI Apps Builder run on Atlassian Forge and use Forge-hosted storage. This means your data stays inside Atlassian's cloud infrastructure — not on any AI Apps Builder servers. Each Jira site gets its own isolated storage space, so one company's data is never mixed with another's. Data is encrypted at rest and backed up by Atlassian.

If your Jira instance is pinned to a specific data residency region (for example, EU or US), Forge-hosted app data follows that setting automatically.

The one exception: if an app makes calls to external services (such as third-party APIs), data that leaves Forge falls outside Atlassian's infrastructure. In that case, you are responsible for the residency, security, and deletion of that external data.

Forge uses a shared responsibility model. Atlassian is responsible for the platform infrastructure, managed storage and encryption, backups of Forge-stored data, and SOC 2 and ISO 27001 certifications at the platform level. You are responsible for writing secure app code, choosing and minimizing scopes, preventing cross-tenant data leaks in your app logic, defining any data sent to external services, and your organization's broader compliance requirements. In short: Atlassian secures and operates the Forge platform. You are responsible for how your app uses that platform.

Yes, you still have options. If you are not an administrator on the Jira site where you want to deploy the app, you can:

• Use your personal Jira site or Jira Sandbox to generate and test the app.

• Once the app is ready, you can move it to the correct production site using a shared link.

• After that, a Jira administrator can complete the installation on the target site.

For detailed steps, see our documentation: How to Move Forge Apps Built with AI Apps Builder to Another Jira Site.

Yes. You can give access to additional users by adding them as Contributors in the Atlassian Developer Console. This allows others to help manage or work with your app. To learn how to do this, see our documentation: Managing Forge Apps - Atlassian Developer Console.

Yes, you can continue improving your app after deployment. You can refine the UI, update the logic, or add new features to your existing app. Please note that any changes you make will only appear in Jira after you redeploy the app.

Yes, you can. AI Apps Builder lets you create multiple modules or pages in one app, including dashboards, configuration pages, reporting views, or any modules your workflow needs. AI Apps Builder supports 31 modules across Jira Core, Jira Service Management, and automation triggers.

You can find all the apps you created with AI Apps Builder directly in your Jira site. To learn more, please read our documentation page: How to Access the Apps You’ve Built with AI Apps Builder.

Yes. On the deployment page, you can download a ZIP file with the full source code of your generated app.

This is useful when you want to review the code, learn from the structure, or share it with a developer.

Learn how to write clearer, more effective prompts with proven techniques and practical examples in our guide: How to Write Effective AI Prompts: Best Practices and Practical Examples.

Yes. If you create and use your own Forge app, you are responsible for any costs related to Atlassian Forge usage. Here’s an overview of Forge pricing starting January 2026.