For Jira Cloud administrators

You are paying for apps nobody opens.

Someone installed a Marketplace app for a project in 2023. The project ended. Nobody uninstalled it. The subscription renews every year, quietly, forever.

Jira Cloud gives you no way to see which apps are actually being used. The request for it — ECO-470 — has been open more than four years with 383 votes, and the equivalent tool that exists for Data Center has no Cloud version. So admins audit by hand, or don't audit at all.

Ask for early access Free while in early access. No card, no signup form.

What it gives you

It reads every part of your Jira configuration that records which app put it there — custom fields, dashboard gadgets, workflow rules — and attributes each element back to its owner. Then it cross-references your billing list. Apps that appear nowhere are the ones worth questioning.

Footprint report — example 4 of 9 apps flagged

App key	Config elements	Footprint	Annual cost
com.onresolve.jira.groovy.groovyrunner	147	in use	12,400
com.tempoplugin.tempo-accounts	38	in use	9,900
com.acme.roadmap-planner	0	none found	7,200
com.vendor.legacy-reports	0	none found	5,600
com.vendor.survey-toolkit	0	none found	3,150
com.oldvendor.issue-templates	0	none found	2,480

Flagged for review, per year 18,430

Illustrative figures. App keys are real Marketplace and placeholder vendor keys, shown in the format the report uses.

Three steps, in this order

STEP 1

Scan

Install and press one button. No configuration, no setup wizard. You see the attribution table before you give it anything.

STEP 2

Import your list

Jira won't let an app see what's installed, so you paste your app list and renewal costs from Atlassian Billing. That's also where the money figures come from.

STEP 3

Review before renewal

You get apps with no footprint, ranked by what they cost, plus a separate list of everything the scan could not judge.

What it will not tell you

This product asserts a negative — "nothing uses this" — and a wrong answer means someone cancels software their team depends on. So it is built to say "cannot judge" rather than guess:

An app used only through its own screens leaves no trace in Jira configuration. No footprint is evidence, not proof, and the report says so on the same screen as the number.
If any part of the scan fails, it withholds all cancellation advice rather than under-reporting and inventing savings.
Forge apps are identified internally by installation ID, which billing exports don't contain. Those are listed as needing review, never as unused.
It reads your configuration and nothing else. No issue content, no personal data, and nothing ever leaves Atlassian's infrastructure.

Where this actually is

Early access, and honest about it. The app runs and has been tested against a live Jira site. It is not yet listed on the Atlassian Marketplace, and it has no paying customers, because it hasn't been offered to any.

Right now the useful thing is not a sale. It's finding out whether the report tells you something you didn't know, and whether the import step is worth the two minutes it costs you. If it isn't, that is the most valuable thing you could tell me.

Get it on your site Installed by direct link. No Marketplace listing required.