How does this company make money?
Most revenue comes from annual cloud subscriptions priced by the number of user seats — the more people at a company who use the tools, the higher the bill. Companies that want to run the software on their own servers instead can buy a Data Center perpetual license. Atlassian also takes a share of sales made through its Marketplace, where third-party developers sell apps and connectors that plug into Jira and Confluence.
What makes this company hard to replace?
The custom Jira workflows each company builds — with their own field names, permission rules, and business logic — cannot be exported and dropped into a competitor's system. Recreating them from scratch takes months. Confluence makes this harder: pages are full of links to other pages and embedded Jira queries, so the documentation cannot be moved cleanly without also moving the tickets it references. And any Marketplace apps the team relies on are built for Atlassian's APIs specifically — they stop working on any other platform.
What limits this company?
Adding a new large enterprise customer is not as simple as copying a template. Each big deployment needs its own dedicated compute resources and its own partitioned PostgreSQL database that cannot be shared with other customers. That provisioning work is the hard ceiling — not the workflow templates themselves, which can be duplicated at almost no cost.
What does this company depend on?
The company cannot run without Amazon Web Services for cloud hosting, Kubernetes for scaling that infrastructure, PostgreSQL for storing every ticket and page, Lucene for powering content search, and GitHub and GitLab integrations that connect Jira to where developers actually write code.
Who depends on this company?
DevOps teams at software companies would lose the ability to plan sprints and track releases. IT service desk teams would lose the system that routes incident tickets and monitors response-time targets. Product managers would lose the shared space where roadmaps are documented and coordinated across teams.
How does this company scale?
Workflow templates and Marketplace integration connectors can be copied across new customer accounts at almost no additional cost. What does not scale cheaply is onboarding large enterprise customers — each one requires dedicated compute resources and a partitioned PostgreSQL database, so that provisioning work stays the bottleneck even as the rest of the platform grows.
What external forces can significantly affect this company?
European GDPR rules on where data must be stored force the company to build and maintain separate regional cloud infrastructure, which adds cost. Economic downturns push enterprise customers to cut software budgets and take longer to sign new contracts. On the other side, the broad shift to remote work increases demand for tools like Confluence that let teams collaborate without being in the same room.
Where is this company structurally vulnerable?
If a competitor — or even a large company's own internal team — built a tool that could faithfully read Jira's custom field schemas, transition rules, and Confluence macro dependencies and reconstruct them in a different system, the months-long migration cost would disappear. That would remove the main reason customers stay, regardless of price.
CompanyGraph