This article is based on reporting originally published by diginomica.com, drawing on a pre-briefing with Atlassian’s Enterprise Cloud Lead, Harsh Jawharkar, at Atlassian’s San Francisco headquarters in September 2019.
Overview: A Cloud-First Pivot
Atlassian announced a broad set of cloud-focused initiatives for its Jira and Confluence product lines, including new free-tier plans, enterprise security enhancements, an upgraded administration console, and expanded cloud migration tooling. The announcements represented a clear strategic signal: with 90% of new customers starting in the cloud at the time, Atlassian was doubling down on cloud as its primary platform while continuing to support existing on-premise customers who were not yet ready to migrate.
Harsh Jawharkar, Atlassian’s Enterprise Cloud Lead, framed the company’s position on on-premise customers carefully:
Different customers are in different journeys, different states of maturity, in terms of cloud adoption. We don’t want to be forceful in terms of what our point of view is. There are people who are cloud-native, cloud-first. They will jump right in. Other folks — we have a history with them, we go back at least 17 years helping people collaborate — are on the on-prem side. They may or may not want to do a lift-and-shift. We understand.
What Was Announced
The announcement package covered four main areas:
- New cloud pricing tiers: Four plans, including Cloud Premium aimed at enterprise and business customers, heavily discounted academic and non-profit plans, and — most notably — free editions of Jira Software, Confluence, Jira Service Desk, and Jira Core.
- Enterprise security and data privacy: Data residency controls to let organizations choose where their data is stored, custom domain support, and a Trust Center providing transparency around security practices.
- Upgrades to the Atlassian Access admin console: Integration with SSO providers from Microsoft and Google Cloud, support for cloud access security brokers (CASBs), a cross-product audit log, and analytics dashboards covering product adoption and usage patterns.
- Cloud migration support: Migration assistance tools, free cloud trial licenses for existing on-premise customers, greater transparency around cloud product roadmaps, and new cloud-focused sales incentives for channel partners.
Democratizing Team Collaboration
The free plans were positioned as a way to lower the barrier to entry for startups, small businesses, and teams in emerging markets — returning to an early Atlassian ethos of making professional-grade collaboration tools widely accessible. Jawharkar explained the thinking:
With our free plans, any startup or small business can immediately get the essentials of project management and knowledge sharing through the combination of Jira and Confluence. They may even be graduating from basic spreadsheets and unstructured methods.
With customers in nearly 200 countries, Atlassian saw an opportunity to tap demand in markets where price had previously been a significant barrier:
Regardless of industry or geography, every small business needs the same fundamental methods to organize their work and collaborate to be productive. We believe that we’re meeting latent yet growing demand across the world — including underserved and emerging market segments — by introducing our free plans, so that literally anyone can organize and manage their work to accomplish any purpose they choose.
Enhancements for Larger Enterprises
At the other end of the market, Atlassian was equally focused on removing friction for enterprise adoption. The enhancements to the Access admin console were targeted directly at the operational realities faced by large IT organizations — audit logging, SSO integration, and CASB support are table-stakes requirements for enterprise security teams evaluating any SaaS platform.
These are very mundane, but real world challenges that admins have to live with. It does ultimately affect whether they feel confident in how they can use [the products] at scale, given that their scope is pretty massive.
Cloud migration for large enterprises is inherently complex, and Atlassian acknowledged that tooling alone is not sufficient. Jawharkar described the challenge in terms that resonate with any DevOps team that has managed a phased infrastructure migration:
It’s not just about moving users and groups, projects, instances, content. It’s also about how do you programmatically help a big company, or even a midsize company, manage change over time in a phased program.
The underlying business case matters too, he added:
When we talk to customers, cloud is a means to an end. The real question is, how do we help a particular company or industry solve existential business problems or business goals with cloud as a catalyst?
Expanding Beyond Engineering Teams
One of the more strategically significant observations from Atlassian at the time was the organic spread of Jira and Confluence usage outside software engineering — into product management, marketing, sales, and customer service teams. This cross-functional adoption was being driven not by top-down mandates, but by the natural gravity of tools that adjacent teams were already using:
We’re in that space with the technical audience. They’ve embraced this as an operating methodology. But because they work with so many other constituents, it is so intermingled, that everybody is exposed to Jira Software. Marketers are using Jira Software to request design assets from the designers. PMs are asking marketers about when campaigns are going to ship. So inevitably, we’ve already crossed that bridge into other teams that are adjacent to engineering.
It can be manipulated by literally any team — it could be even customer service — to use it for whatever purpose. It gives you, essentially, a relational database, workflows, and the mechanisms to literally mold it to any workflow you want.
This observation foreshadowed a broader industry trend: work management platforms originally built for software teams becoming general-purpose operational tools across the enterprise.
Distributed Work as a Structural Shift
Jawharkar drew a compelling parallel between the microservices architectural pattern and the way enterprise work itself was becoming more distributed:
I almost think that if you take the concept of microservices and apply it to organizational work, that has happened. We are now very distributed, there are many remote teams — not just here, but around the world — different companies that are much more comfortable with those flexible work schedules.
I think when the cultural forces align with technology, there’s a different curve, and I think we’ve hit that curve. And that’s why we’ve seen Slack, Atlassian, a whole bunch of other folks, Zoom, Okta, growing really fast, because they’re serving these latent needs.
The broader business imperative, as Jawharkar framed it, is organizational agility:
Gone are the days where you were asked to build to last. Today it’s really about, can you build for change? You have to build and organize business to be so nimble and flexible, that they can adapt to new disruptive forces, to changing consumer trends, very quickly.
Strategic Context: Divestiture, Acquisition, and Focus
These announcements took place against a broader strategic backdrop. Atlassian had previously divested its HipChat and Stride messaging tools to Slack, effectively ceding the real-time chat space in order to concentrate on work management. The move was a deliberate narrowing of scope — Atlassian was no longer trying to own the entire collaborative canvas for the enterprise; instead, it was focusing on structured work management as its core differentiator.
Complementing this focus, Atlassian’s acquisition of AgileCraft — rebranded as Jira Align — added portfolio-level planning and visibility capabilities, giving enterprise customers a way to connect team-level execution in Jira to broader business objectives. This positioned Atlassian more directly against tools like Asana in the broader work management market, while strengthening its value proposition for large engineering organizations practicing scaled agile frameworks.
Key Takeaways for DevOps and Platform Teams
- Free tiers lower adoption barriers: The free editions of Jira Software, Confluence, Jira Service Desk, and Jira Core make it easier for small teams and startups to adopt standardized tooling without upfront cost — reducing one of the traditional objections to Atlassian’s platform in price-sensitive environments.
- Enterprise readiness is increasingly cloud-native: SSO integration, CASB support, data residency controls, and cross-product audit logging address the core concerns that have historically kept enterprise customers on-premise.
- Migration is a program, not a project: Atlassian’s framing of cloud migration as a phased, programmatic effort — rather than a single cutover — reflects a mature understanding of what large-scale SaaS migrations actually involve in practice.
- Non-engineering adoption is accelerating: Teams outside software development are increasingly using Jira and Confluence as general-purpose workflow and knowledge management tools. Platform and DevOps teams should anticipate growing cross-functional dependencies on these platforms.
- Jira Align extends the value chain upward: For organizations practicing SAFe or similar scaled frameworks, Jira Align connects team-level agile execution to enterprise portfolio planning — a capability gap that previously required third-party tooling.