🥇 Gold Again! Warsaw Dynamics Climbing Another High Atlassian Mountain

[#1]

Two years ago, we shared that Warsaw Dynamics had become an Atlassian Platinum Marketplace Partner. Today, we’re announcing that we’ve achieved Gold, which, admittedly, sounds a little like we’re climbing the same ladder twice.

Except we aren’t.

Strangely enough, this Gold status may mean even more to us than the Platinum badge did back in 2024. Not because Gold suddenly outranks Platinum.

Because Atlassian changed the ladder we are climbing.

Platinum then vs. Gold now

When we reached Platinum, Marketplace Partner tiers worked quite differently.

Qualification relied heavily on overall Marketplace performance, with a required portion coming from Cloud. That meant Server and Data Center business could still play a significant role in reaching the higher tiers.

Today, the Partner Program is much more firmly built around where the Atlassian ecosystem is heading: Cloud. Forge. Security. Compliance. Support.

Platinum then	Gold now
Revenue: total gross sales with a Cloud-share %	Revenue: Cloud-only gross sales
No Forge sales threshold	Mandatory Forge revenue
Security certification: none required, "participation in Atlassian Security Programs" was enough	Formal security/compliance requirements: SOC 2 Type 2 or ISO 27001:2022 (held, not merely scheduled)
Trust center: not a criterion	Third-party validated Trust Center (Drata, Vanta or SafeBase)
Review cadence: Bi-annual	Review cadence: Annual

There are more differences, but the direction is pretty clear. Today's Gold doesn't simply represent a lower version of yesterday's Platinum.

It measures a different kind of Marketplace Partner.

First Platinum. Then… Silver.

When Atlassian introduced the new Partner Program requirements, our existing Platinum badge didn't magically transfer over.

We went back to Silver.

Were we thrilled about it?

Let's go with not particularly. 🙄

But the company hadn't suddenly become weaker overnight. The benchmark had changed beneath us. It was a little like turning up for the next season of the same sport and discovering that someone had rewritten half the rulebook.

And there was quite a lot of Forge ahead

Yes. That pun was unavoidable. 🫠

Over the following year, a significant portion of our development effort focused on adapting our portfolio to Atlassian's Forge-first ecosystem. And anyone who has worked on a Connect-to-Forge migration knows that “migration” can be a wonderfully innocent word for something that occasionally looks suspiciously like re-architecting an application while people are still using it. (please quote me on this beautiful line)

At times, feature development had to take a back seat while the foundations changed. But somehow, our developers also kept shipping.

A lot. 

Macro Pack grew to more than 30 macros, including surveys, 3D content, structured data, diagrams, code, and plenty of things we probably shouldn't try fitting into this post.

External Share for Confluence received a major redesign and continues to expand beyond the external-sharing options available natively in Confluence.

External Share for Jira made external collaborators feel much more like actual participants, with assignment capabilities and improvements to dashboards and notifications.

Approval Path moved into Jira dashboards and JSM portals, while also introducing an AI-powered approval step that can analyze requests, highlight risks, and help approvers understand what they're looking at faster.

And all of that happened while we were building new apps too.

---

In conclusion, we didn't simply regain something we had lost. We had to earn back our place against a new set of expectations while changing our apps, architecture, teamwork, security practices, and product strategy alongside the Atlassian platform itself.

Back when we became Platinum, we wrote that a Marketplace tier was about more than the color next to your company name.

We still think so.

And Thank You to the Warsaw Dynamics team for baking this statement up every day. 💪