The Atlassian ecosystem has been changing quietly but decisively.
Over time, the direction became clear: Cloud-first, security-first, platform-led.
At Atlassian, that direction has a name — Forge.
Today, we want to share where Getint stands in that shift.
Getint connectors are now built on Forge and available on the Atlassian Marketplace.
This isn’t a cosmetic change or a one-off technical update. It’s a structural decision about how our integrations should live, operate, and evolve inside Atlassian Cloud.
A short story about why Forge matters
For years, Marketplace apps grew fast — sometimes faster than the platform beneath them. That worked for a while, but as Atlassian Cloud matured, expectations changed. Customers started asking deeper questions:
Where does the app run?
How is data isolated?
Who is responsible for security at the platform level?
Forge is Atlassian’s answer to those questions.
By design, Forge apps run within Atlassian’s infrastructure. Security controls are no longer optional add-ons; they are part of the platform itself. Deployment, permissions, and data handling follow a shared, transparent model defined by Atlassian.
This shift isn’t about restricting vendors. It’s about creating a foundation that scales safely — especially for enterprise teams that rely on Marketplace apps as part of their core workflows.
Why Getint moved all connectors to Forge
Getint has always operated close to the heart of Atlassian workflows. Our integrations connect Jira with systems that often sit just as deep in an organization’s operating model — development platforms, service management tools, work management software.
When Atlassian made its direction clear, the question for us wasn’t if we would move to Forge, but how comprehensively.
We chose to move all Getint connectors available on the Atlassian Marketplace to Forge, so customers wouldn’t have to guess which apps follow Atlassian’s newest standards and which don’t.
Today, our Forge-based connectors include integrations between Jira and tools such as Azure DevOps, GitHub, Notion, Monday.com, Asana, and Trello — as well as Jira-to-Jira synchronization across multiple instances.
Each of these connectors is live on the Atlassian Marketplace, running on Forge, and used daily by teams synchronizing work and migrating data across systems.
What this changes — and what it doesn’t
If you already use Getint, this transition doesn’t require action on your side. Your integrations continue to work as before.
What changes is the foundation underneath them.
Forge gives Getint a clearer, more stable contract with the Atlassian platform. It aligns our apps with Atlassian’s Cloud roadmap and reduces long-term risk for customers who depend on integrations as part of their operational backbone.
From a customer perspective, that means fewer surprises, stronger guarantees around security, and confidence that the tools connecting your systems are built the same way Atlassian expects the ecosystem to evolve.
Building for the platform, not around it
One of the reasons teams choose Getint is that our integrations are designed to fit into real, often complex environments — multiple tools, multiple teams, and no appetite for fragile connections.
Moving fully to Forge reinforces that philosophy. Instead of working around the Atlassian platform, we’re building directly on top of it, using the same assumptions Atlassian uses when shaping the future of Cloud.
That alignment matters. Especially for organizations that see integrations not as experiments, but as long-term infrastructure.
Where this leaves us today
Getint is fully Forge ready across its Marketplace connector portfolio.
Our integrations meet Atlassian’s platform standards and are prepared for the Cloud-first future Atlassian is building.
For teams planning new integrations, migrations, or cross-tool workflows, this means one less thing to worry about — and a clearer path forward inside the Atlassian ecosystem.
