Plumbworks / Instance Ledger / Jira Cloud
Find out what your Jira instance is charging you for and nobody uses.
Instance Ledger scans licences, custom fields, workflows, screens and permission schemes, then puts a number next to each finding. Most admins run it once before renewal and never argue about seat count again.
Costs are calculated from your actual Atlassian tier and currency, not a generic average.
What it checks
Nine scans, run on demand or on a weekly schedule. Results export to CSV so you can hand them to whoever owns the budget.
- licencesDormant seats. Users with no login inside your chosen window, with the annual cost of each one at your actual tier and currency.
- licencesDirectory drift. Accounts deactivated in your IdP that still hold an Atlassian seat, and users holding a product licence they have never opened.
- fieldsEmpty custom fields. Fields with no value written inside a window you set, ranked by how many screens and contexts they are attached to.
- fieldsDuplicate definitions. Fields with the same name and type defined separately across projects, which is how instances end up with four different "Customer".
- configOrphaned workflows and screens. Schemes attached to no active project, with a preview of exactly what unlinking each one touches.
- configDormant projects. Projects with no issue created, transitioned or commented on in your chosen window, and who last touched them.
- accessPermission exposure. Schemes granting browse or edit to anonymous users, "anyone on the internet" links, and groups with unexpectedly broad reach.
- accessAdmin sprawl. Everyone holding site-admin, org-admin or project-admin, and when each of them last used it.
- limitsHeadroom. Where you sit against Atlassian's per-instance ceilings on custom fields, workflows, statuses and automation rules.
Read-only until you say otherwise
The default installation requests no write permissions. Instance Ledger physically cannot change your instance, which is the answer to the first question every change board asks.
Cleanup actions — bulk-deactivating dormant users, archiving orphaned schemes, deleting empty fields — sit behind a separate permission grant you approve later, if you want them at all. Each action opens an impact preview listing every affected project, scheme, board and issue, and writes an entry to your Atlassian audit log when it runs.
Pricing
Billed by Atlassian at the same user tier as your largest Jira product, and charged on your existing Atlassian invoice. Free for instances of 10 users or fewer.
| Users | Per user / month | Monthly |
|---|---|---|
| 1 – 10 | free | $0 |
| 11 – 100 | $1.30 | $130 at 100 |
| 101 – 500 | $0.75 | $375 at 500 |
| 501 – 1,000 | $0.45 | $450 at 1,000 |
| 1,001 + | $0.28 | $515 at 1,840 |
At 1,840 users the app costs about $6,180 a year. The sample report above finds $40,800.
Questions
How long does a first scan take?
Under a minute for most instances. Very large sites with heavy issue history can take a few minutes on the first run; after that only changes are re-read.
Does "no login in 90 days" account for API and service accounts?
Yes. Accounts authenticating by API token are counted as active, and you can tag known service accounts so they are excluded from the dormant list permanently.
Can I schedule the report to someone who is not an admin?
Yes. Weekly or monthly CSV and PDF exports can go to any email address, which is usually how the finance owner ends up seeing the licence number.
What happens to my data if I uninstall?
Nothing to delete on our side, because nothing left your tenant. Forge app storage is removed by Atlassian when the app is uninstalled.