---
title: "Macro Toolkit: Forge Native/Runs on Atlassian"
canonical: "https://help.refined.com/space/MACROTOOLKIT/6828064785/Macro%20Toolkit%3A%20Forge%20Native%2FRuns%20on%20Atlassian"
format: markdown
---
## What is Forge Native and Runs on Atlassian?

Atlassian is evolving its cloud platform to deliver stronger security, simplified administration, and deeper product integration. As part of this shift, apps are moving toward **Forge Native (****[Runs on Atlassian](https://developer.atlassian.com/platform/forge/runs-on-atlassian/)****)**. This is a model where apps run entirely on Atlassian’s infrastructure rather than relying on external services. This approach is designed to reduce complexity, increase trust, and align with the needs of modern, security-conscious organisations.

### Why it matters

- **Stronger security and compliance by default**

Forge Native apps process and store data within Atlassian’s environment. This platform reduces exposure to external systems and supports enterprise requirements around data residency, compliance, and vendor risk—often simplifying security reviews and procurement.

- **Lower operational complexity and higher reliability**

Because apps run on Atlassian’s infrastructure, there is no dependency on external hosting or services. This reduces potential points of failure, improves stability, and ensures consistent performance without additional infrastructure overhead.

- **Built for Atlassian’s future platform**

Forge is Atlassian’s strategic direction for cloud apps. Apps built on Forge Native are aligned with ongoing platform investments, ensuring compatibility with new capabilities and long-term support within the Atlassian ecosystem.

## Impact on Macro Toolkit

We’ve worked to preserve the existing experience as closely as possible, and in most areas the functionality remains unchanged. However because Forge Native apps run entirely within Atlassian’s infrastructure, certain capabilities (particularly those relying on external services) are more limited. Due to Atlassians choices in platform structure, it also limits what options we have in offering you an a fully seamless experience. Currently this impacts:

- **Restrictions for nested bodied Macros**
  - Previously created pages will continue to work as expected. However, third-party macros will display an error indicating that they are not supported when nested inside any of our bodied macros, such as  Panels, Tabs, Expands or Steps. The content is not lost and will function normally once the macro is moved outside of the panel or tab.
  - No Connect-on-Forge macros will be possible to nest in a Forge application macro. See Atlassian’s documentation on the topic [here](https://developer.atlassian.com/platform/forge/apis-reference/ui-api-bridge/view/#limitations).
  - Majority of third-party macros will not be possible to nest under our macros
  - Majority of native Atlassian macros will not be possible to nest.

> Macro (refined-panel)
> 
> *This means that until Atlassian has enabled proper nesting of all types of Macros - migrating to the Forge version of the application might break your nested macros that contain native Atlassian macros or other third-party macros. The content will not be lost - but not visible on published pages.*

- **External image URLs**
  - You will no longer be able to upload image URLs to image macros. Images you have previously added will be available to download in the macro editing interface post-upgrade. These can then be re-uploaded via a new local upload functionality instead.

> Macro (refined-panel)
> 
> *The upcoming 8.x Forge Native version is a major release and will not be applied automatically. Your Confluence admin must manually upgrade the app.*

## Need support?

If you have any questions around the Forge Native upgrade, please reach out to our [Support team](https://help.refined.com/page/contact-us).