Companies that use Jira

We dug into our own data to find out how some companies are using Jira in sophisticated, interesting ways. We also corroborated our data by asking employees who worked in each of these companies.

Cloudflare

Computer and Network Security — San Francisco, California

Cloudflare runs one of the world's largest networks, with servers in more than 335 cities across 120+ countries. The company protects and accelerates roughly 20% of all web traffic, handles DNS for tens of millions of websites, and blocks billions of cyberattacks every day.

Cloudflare is one of the few companies that's still actively migrating from self-hosted Jira Data Center to Jira Cloud. Most companies are either on one or the other. Cloudflare is in the middle of the move, which is why they're hiring senior Atlassian admins who have experience running both. The team uses ScriptRunner with Groovy scripting to extend Jira well beyond its out-of-the-box capabilities, writing custom logic that talks to Jira's APIs and automates business rules.

The most interesting thing about how Cloudflare uses Jira has to do with their network. When an engineer needs to push a configuration change to a server in one of those 335 cities, there's real risk. A bad config can take a chunk of the internet offline for millions of people. So Cloudflare built a workflow where AI validates the Jira ticket data before the change actually goes live. The AI cross-checks the deployment records, confirms the data is accurate, and flags any gaps before the engineer clicks deploy. Jira isn't just tracking the work. It's the source of truth that the automation is verifying against.

That same pattern shows up in other places. When Cloudflare is preparing for government security certifications like FedRAMP and DoD IL4, Jira is where auditors look to see how vulnerabilities got tracked and resolved. When the deployment team is spinning up a new data center, Jira holds the install checklists and the coordination between remote contractors. The tool ends up being load-bearing infrastructure for the infrastructure itself.

---

Databricks

Software Development — San Francisco, California

Databricks is the data and AI platform used by more than 20,000 organizations worldwide, including over 60% of the Fortune 500, for building and scaling data pipelines, analytics, and AI applications.

When a company grows as fast as Databricks, keeping thousands of engineers coordinated becomes its own engineering problem. Databricks treats Jira as the solution. It connects to HR systems like Workday so headcount changes flow through automatically, plugs into incident management so outages trigger the right workflows, integrates with Salesforce so sales activity feeds into engineering work, and ties into messaging and monitoring tools so nothing falls through the cracks.

On top of that, Databricks builds custom automation on top of Jira using scripting in languages like Python, SQL, and Scala rather than accepting default configurations. The result is a Jira environment that actively reflects how Databricks operates, not just a generic project tracker the company happens to use.

What's less obvious from the outside is how much investment goes into running Jira itself. Databricks has dedicated Jira administrators spread across San Francisco, Bengaluru, São Paulo, and Costa Rica, with the work sitting inside a Corporate Engineering team that's part of the CIO's organization. That global footprint means Jira gets supported around the clock, and the admins in places like Costa Rica and Brazil handle not just day-to-day administration but also software release management, coordinating builds and deployments through Jira across multiple environments.

---

EXANTE

Capital Markets — Malta

EXANTE is a global prime broker giving institutional and individual investors access to more than 2 million financial instruments across 50+ markets through a single multi-currency account.

EXANTE uses Jira as the central system where work gets tracked, planned, and automated across the company. But they haven't just turned it on and left it. They've built custom code on top of it using a tool called ScriptRunner, which lets engineers write scripts that automatically trigger actions when certain things happen in Jira. For example, when a ticket moves to a certain status, a script might automatically notify a team, update another field, or kick off a process elsewhere. That kind of automation runs throughout how EXANTE operates.

They also use Jira's Assets module, which lets you store structured data inside Jira, things like which systems exist, who owns them, and how they're connected. And they use Advanced Roadmaps and Structures for planning and reporting across multiple teams at once.

On top of that, EXANTE has wired Jira into the other tools they run. HR data flows in from BambooHR, time tracking comes from Tempo, and even their secrets management tool Vaultwarden is connected. The result is that Jira sits at the center of how the company tracks not just engineering work, but people, time, and security operations too.

What's particularly interesting is how EXANTE treats the Jira automation code itself. Rather than just writing scripts and hoping they work, the team stores their automation code in Git with proper branching and version control, and deploys new scripts through CI/CD pipelines, the same way software engineers ship production code. They also build monitoring dashboards in Grafana and Kibana that track whether the automations are actually firing correctly, so broken scripts get caught quickly instead of silently failing.

---

BTG Pactual

Financial Services — São Paulo, Brazil

BTG Pactual is Latin America's largest investment bank, operating across investment banking, trading, wealth management, asset management, and digital banking, with offices spanning Brazil, the Americas, Europe, and the UK.

At BTG, Jira isn't just used out of the box. The bank's engineers actually write their own code to extend Jira with new features that don't exist by default. They also wire it up to the other tools the company uses, things like Confluence for documentation, Slack for messaging, and GitHub for storing code, so information flows between all of them without anyone having to copy and paste.

Interestingly, BTG has a whole team inside the bank whose job is to find things that humans are doing manually and build software to do it for them instead. They call it the Automation team, and it sits inside the bank's Data & AI group. The team uses Jira alongside Azure DevOps to keep track of which manual processes they're tackling next, what's in progress, and what's been shipped. So when you hear that the bank has gotten faster at something over time, there's a good chance this team was behind it.

There's also a governance side to how BTG uses Jira. The bank has a lot of big, important projects running at any given moment, things like launching new products, meeting new regulations, or rolling out new systems across the bank. Keeping track of all of that is its own job, and Jira is where it happens.

A dedicated Project Governance team uses Jira to pull together status updates, flag risks, and build the reports that senior leaders rely on to see what's going on across the bank. That way, instead of information being scattered across emails and spreadsheets, everything lives in one place where the people running the bank can actually see it.

---

Temenos

Software Development — Geneva, Switzerland

Temenos is a global banking software company serving more than 3,000 financial institutions across 150 countries, from the largest global banks to community lenders.

What's particularly interesting about Temenos is the scale at which they run agile development. Most companies have a few scrum teams. Temenos has organized its entire engineering organization into something called Agile Release Trains, or ARTs, which are basically large groups of scrum teams all working together on a single product area, like core banking or digital banking or payments.

Each ART has its own Scrum Masters running the day-to-day team ceremonies, Release Train Engineers coordinating across teams, and Quality Engineers tracking testing and defect metrics, and every one of those roles lives inside Jira.

The thing that makes this setup work at Temenos's scale is that Jira doesn't just track individual tickets. It also holds the quality metrics, the OKR compliance reports, the release readiness checks, and the end-to-end test coverage data for each ART. So when leadership wants to see whether a particular banking product is on track to ship, or whether quality has been slipping across a specific train, they pull that information out of Jira rather than waiting for someone to compile a deck.

On top of Jira, Temenos also uses Jira Align, which is Atlassian's higher-level planning product, to give executives a portfolio view across all the ARTs at once. That combination of Jira at the team level and Jira Align at the portfolio level is what lets a company with thousands of engineers across multiple countries actually keep everyone pointed in the same direction.

---

Hard Rock Digital

Software Development — Hollywood, Florida

Hard Rock Digital is the online sportsbook and casino platform behind the Hard Rock brand, headquartered in Hollywood, Florida with offices in New Jersey, Austin, and Toronto.

Because online gambling is one of the most heavily regulated industries in the world, Hard Rock Digital uses Jira as the backbone for how they prove to regulators that their platform is actually working the way their documented policies say it should. Quality engineers use Jira together with a testing tool called Jira Xray to run thousands of test cases against the platform before every release, making sure things like deposits, payouts, and player verification behave correctly. On top of that, dedicated compliance analysts use Jira and Confluence to collect evidence that business processes are being followed in practice, not just on paper, so that if an auditor ever asks how the company handles a specific requirement, the answer is already documented and traceable.

Hard Rock Digital also has a senior leader whose entire job is making sure Jira stays the single source of truth for how projects are going. The Senior Director of PMO Assurance owns the delivery toolset, builds the dashboards that leadership uses to check project health, and runs the frameworks that keep teams consistent in how they use Jira across the company. Most companies have project managers who happen to use Jira. Hard Rock Digital has someone whose whole mandate is treating Jira as the operating system of the business, with reporting clean enough that executives can trust what it says without asking anyone to pull together a deck.

---

WEX

Software Development — Portland, Maine

WEX is a global payments company that simplifies complex payment ecosystems for fleet operators, healthcare organizations, and corporate travel programs, processing transactions for millions of users worldwide.

Jira Service Management runs as an enterprise service platform at WEX, handling requests and workflows across Technology, HR, and Facilities. Think of it like an internal help desk, but one that covers the entire company. If someone in HR needs to process an onboarding request, or Facilities needs to track a maintenance job, or IT needs to resolve an incident, all of that flows through the same system with custom workflows and SLA tracking built for each department's specific needs.

Most companies run JSM for IT support and stop there. WEX extended it into HR and Facilities, which means teams outside engineering rely on it for their day-to-day service delivery too. That's a meaningful commitment to Jira as organizational infrastructure, not just a developer tool.

WEX also has an entire office inside the company whose job is to make sure Jira is used well. It's called the Technical Program Management Office, and its stated mission is to speed up how fast WEX ships new products by making delivery itself a competitive advantage. The people in this office are responsible for something called Jira stewardship, which is a fancy way of saying they care about whether the data inside Jira is accurate, consistent, and trustworthy. When leadership wants to know how a project is going or where the bottlenecks are, the answer comes out of Jira rather than a hastily built spreadsheet.

There's one more detail that's genuinely unusual. WEX uses Jira data to help with accounting. When engineers build new software, some of that work counts as a capital investment on the company's books rather than a regular expense, and the finance team relies on well-organized Jira tickets to figure out how much. That's why the program management office puts so much effort into clean Jira data. When a public company is using Confluence and Jira to help build its quarterly financial reports, that's a higher bar than most teams ever hold themselves to.

---

Coralogix

Software Development — Tel Aviv, Israel

Coralogix is a full-stack observability platform used by more than 4,000 organizations worldwide to monitor logs, metrics, traces, and security events without relying on expensive data indexing.

Jira sits at the center of how Coralogix connects its internal operations. EazyBI pulls data out of Jira and turns it into dashboards and reports. Xray lives inside Jira and handles test case management, so QA work happens in the same place as engineering work. Salesforce connects via API so that customer and deal context flows into engineering workflows automatically, rather than someone having to copy information between systems. ScriptRunner with Groovy scripting ties it all together with custom automation.

The practical effect is that product, engineering, sales, and QA all work out of one connected system. When a customer issue needs to move from a sales conversation to an engineering fix to a QA test, the context travels with it instead of getting lost between tools.

Coralogix also has a dedicated Jira expert role inside the product organization whose entire job is keeping the Jira setup in good shape. They write custom scripts, build integrations with Jira's REST APIs and webhooks, and make sure the workflows and permissions match how teams actually work. They also own how the product org uses other tools that sit alongside Jira, like Mixpanel for analytics, Miro for whiteboarding, Figma for design, Mkdocs for documentation, and Git for code. So Jira isn't just a ticket system at Coralogix. It's the spine that every other product tool hangs off of.

---

Deutsche Funkturm

Telecommunications — Münster, Germany

Deutsche Funkturm operates more than 34,600 radio sites across Germany. It's the infrastructure company that makes mobile phone calls, 5G data, television broadcasts, and emergency services radio work for pretty much everyone in the country. Originally a subsidiary of Deutsche Telekom, it's now jointly owned with DigitalBridge and Brookfield and generates around a billion euros in annual revenue.

The most interesting part about their usage is that Jira sits in the middle of the physical tower operation itself. Field planners handling sites across northern Germany use Jira alongside specialized telecom tools like NexSysOne and MicroStrategy to coordinate site handoffs, track defects, maintain access documentation, and hit construction milestones. When a new cell tower needs to go live or an existing site needs changes, the workflow lives in Jira.

DFMG also runs a 1st Line incident team whose job is coordinating problems across all 34,600 tower sites. When an incident comes in, it lands in Jira, gets tracked against an SLA, and flows through escalation handling and reporting, all inside the same system. The team uses Jira to coordinate with the property owners who host the towers, because DFMG rents the land its towers sit on from tens of thousands of different landlords and property deals and complaints have to be tracked somewhere. That somewhere is Jira.

So the same tool that a software company might use to track bug tickets is being used here to keep Germany's mobile phone network running. It's a nice reminder that Jira's reach goes well beyond the software industry it was built for.

---

Klaviyo

Marketing Services — Boston, Massachusetts

Klaviyo is the marketing automation platform that powers email and SMS campaigns for more than 176,000 brands, including Mattel, Glossier, and Liquid Death. The company went public in 2023 and has grown to around 2,800 employees.

The most interesting thing Klaviyo is doing with Jira has to do with a project they call ARIA. Think of ARIA as an AI assistant that works for the whole company. When an employee needs something done, like getting a new vendor approved or kicking off a sales process, ARIA tries to handle it in the background instead of making the person chase down five different tools and fill out forms.

For ARIA to actually do useful work, it needs to reach into the systems where the real action happens. Jira is one of the big ones. A lot of internal processes at Klaviyo already live there, from engineering tickets to procurement requests to finance workflows. ARIA reads information out of Jira to understand what's going on, and writes new tickets into Jira when something needs to get done. The AI basically uses Jira the way a human employee would, just much faster and without getting tired.

There's also a person at Klaviyo whose entire job is making Jira work well for the engineering org. They design how teams track their work, how dependencies between teams get mapped, and how leadership gets a clear picture of what's happening across R&D. The idea is that planning decisions should come out of real data in Jira, not just gut feel from team leads in meetings.

---