Built inside the platform, not beside it.
Forge is Atlassian's platform for running custom applications on Atlassian infrastructure, with the app operating inside the same permission and identity model as the rest of the estate. Our work is custom applications and agents built inside the permission model you already govern.
Forge runs custom applications on Atlassian infrastructure, inside the permission model you already govern. That is the whole reason we build there rather than on a connector with credentials of its own.
What it is
Forge is Atlassian's platform for running custom applications on Atlassian infrastructure, with the app operating inside the same permission and identity model as the rest of the estate.
It is for organizations whose requirement genuinely is not met by configuration, and who would rather not add another integration account nobody owns to solve it.
What it does
It runs on Atlassian infrastructure
No separate hosting, no separate credentials, and no separate thing to patch.
It inherits the permission model
What the app can reach is decided by the identity model you already govern, not by a token in a configuration file.
It is reviewable
Scope is declared, which means what an app is entitled to is a question with a written answer.
Where it fits
L4, agents and automation, with a direct dependency on L1. An app built here inherits your permission model instead of holding credentials of its own, which is the difference between something you can review and one more account on a list nobody can explain.
What we do with it
Design and build
Solution design approved before build, then the application itself, tested and documented so your team can extend it.
Reviewing what already exists
Where an app was built by someone else, the first question is whether the permission model underneath it is sound.
Scoping non-human identity
Anything that runs gets an owner, a scope, and a review date, on the same terms as a person.
Maintaining it
Maintenance is where most custom work fails, so it is scoped explicitly rather than assumed.
Where it earns its place
A manufacturer with a calibration model
Equipment records with due dates, intervals, and ownership moved out of a spreadsheet into the platform, where the audit already looks.
An organization replacing scripted synchronization
A scheduled connection inside the platform, replacing a script that runs on somebody's machine with credentials nobody has reviewed.
A team that needs one workflow the product does not have
A single well-scoped extension is a better first engagement than a broad program, and it creates the internal pattern.
Proof
Cloud users on the Forge applications we build and maintain in production.
Atlas Bench, Forge apps in production, September 2026.
World Class Software Development Finalist, 2024-2025
Atlassian Partner Awards, 2024-2025
Questions we get
Why not a connector or a script?
Can you work on an app another partner built?
Do you maintain what you build?
Licensing
Forge apps run against your Atlassian entitlement rather than as separate licenses, but the platform edition can change what an app is permitted to do. That reconciliation sits with the rest of the estate in licensing and renewals.
The Atlas Bench team provided valuable insights and resources that accelerated our Forge development. Their expertise helped us build custom solutions faster and engage more deeply with the Atlassian ecosystem.
Jason Mueller
Sr. Atlassian Systems Engineer