Optimizory is now on Atlassian Government Cloud Marketplace, yes, really

[#1]

Government teams do not need “more tools.” They need fewer surprises, clearer compliance paths, and apps that behave like adults in a regulated environment. So here’s the update from @Optimizory Technologies :

Our Forge-based apps, Links Explorer, Pact, Baseline X, Report X, and RMview, are now published for Atlassian Government Cloud (AGC) and are publicly visible in the Atlassian Government Cloud collection in the Marketplace. That means the listing is out there, discoverable, and ready for the next step: installation for AGC customers as the rollout opens up.

Why does this matter?

Atlassian Government Cloud is built for mission-critical work where security and compliance are the baseline, not bonus features. Atlassian positions AGC as a secure, compliant environment for government workloads, and the Marketplace collection is specifically curated for apps trusted in that context.

For Marketplace partners and builders, AGC also comes with some very particular rules of the road:

• AGC Marketplace versions must be built with Forge (including incremental migration to Forge).
• Installation today is controlled, with Atlassian support teams installing apps for AGC customers in production, and customers typically following an assessment and vendor coordination path.

So if you’re wondering “why is listing a big deal if installs are gated?” it’s because publishing is the hard milestone that unblocks everything else: discovery, evaluation, procurement conversations, and internal readiness.

What “available” looks like in Government Cloud

Here’s the practical view of how this tends to work:

1. Customers find and shortlist apps from the AGC Marketplace collection.
2. They do their due diligence (security and compliance checks, internal approvals).
3. Installation in production is currently handled via Atlassian support, so enablement is real, but not the usual one-click flow yet.

What you can expect from us

Because the community always asks the useful questions (and also the chaotic ones):

• Support readiness: clear support channels, response expectations, and documentation that does not assume you are reading it at 2 a.m.
• AGC-compatible behavior: built on Forge, aligned to the AGC compatibility approach Atlassian lays out for vendors.
• Transparency: we’ll share learnings as we go, what changed for AGC, what surprised us, what we’d do differently.

If you work with government customers (or you are one), I’m curious:

• What’s your biggest blocker when evaluating Marketplace apps for regulated environments?
• What’s one thing vendors consistently underestimate about “enterprise trust”?
• If you’ve shipped to AGC already, what was the hardest part: compatibility, review, listing, or customer onboarding?

Drop your take below. If enough people answer honestly, we all ship better software.