Asset management, without the JSM tax.
Jira Assets (formerly Insight) is Atlassian's CMDB inside Jira Service Management. Assets live as custom objects in a schema you model and maintain. June is a standalone platform that pulls device, software, and access data live from your MDM, IdP, and procurement systems, then plugs into Jira without requiring JSM.
CMDB for Jira Service Management
Two tools, two jobs.
The honest read on who each platform serves best.
June
What June is built for
- Teams that want asset and software spend management as their primary IT operating layer
- Customers who use Jira for tickets but want inventory to live in a purpose-built tool
- Software discovery and license reclaim alongside asset tracking
- Helpdesk integration that works with Jira, but doesn't require JSM
Built in
- Apple Business Manager and Microsoft Entra device enrollment on day one
- Tickets auto-enriched with the reporter's devices, software access, and employee details (any helpdesk, not just Jira)
- Assign tickets to June and it triages and attempts resolution autonomously
- Slack and Teams integration for notifications and helpdesk flows
- Employee surveys for usage validation before reclaim
- Custom connectors built as part of onboarding, typically under a week
Jira Assets
What Jira Assets is built for
- Teams already deeply invested in Jira Service Management
- CMDB use cases where assets feed JSM queues, SLAs, and ITIL workflows
- Customers who want a single Atlassian vendor for ITSM and asset CMDB
- Atlassian admins who want to model assets as custom objects with rich schema
Where June takes a different approach.
The specific places the two platforms diverge in design and execution.
01
Live data, automatically
June pulls device, software, and access data live from your MDM, IdP, procurement, and HRIS. The inventory updates because the source systems do. No CMDB schema to design, no objects to model, no sync jobs to babysit.
02
Standalone platform, not an add-on
June is a primary IT operating layer with its own UI, automations, and data model. Jira Assets is a feature inside JSM that requires the JSM subscription to use.
03
No JSM required
June works with Jira (or JSM) but doesn't require it. If you use a non-Jira ITSM, or no ticketing tool yet, June still works.
04
Software spend management is built in
June discovers your apps, tracks usage, surfaces license reclaim opportunities, and preps renewals out of the box. Jira Assets is asset / CMDB only.
Side-by-side.
Feature coverage by surface. Partial means it's supported but with caveats or via a partner integration.
| Capability | June | Jira Assets |
|---|---|---|
| Asset management | ||
| Live MDM + IdP inventory | ||
| Onboarding and offboarding automation | ||
| Refresh planning and cost tracking | ||
| Audit / compliance reporting | ||
| Software spend management | ||
| SaaS discovery | — | |
| Usage tracking (web + desktop) | — | |
| License reclaim automation | — | |
| Renewal prep and contract management | — | |
| Helpdesk integration | ||
| Works with Jira / JSM | ||
| Requires JSM subscription | — | |
| Automatic ticket enrichment | ||
| Works alongside any ITSM | — | |
| Setup | ||
| Standalone platform (not an add-on) | — | |
See what June pays back in your environment.
Run the numbers on the ROI calculator, then ask us about a pilot. We'll show you the savings against your real data, in about four weeks.
Jira Assets is a trademark of its respective owner. Capability claims on this page reflect our understanding of Jira Assets's public product at time of writing and are directional rather than exhaustive. Verify against current vendor documentation before final selection.