SaaS management, plus the device side.
Torii is a SaaS management platform focused on app discovery and license optimization. June covers SaaS at parity, plus everything on the device side and helpdesk integration, in one product.
SaaS management platform
Two tools, two jobs.
The honest read on who each platform serves best.
June
What June is built for
- IT teams that own both device fleets and software
- Mid-market organizations that want one platform for asset and software lifecycle
- Helpdesk integration that ties tickets back to both devices and software access
- Onboarding and offboarding that covers both software access and device assignment
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
Torii
What Torii is built for
- SaaS-only management teams (often Finance, FinOps, or procurement-led)
- Companies that have device management solved elsewhere or out of scope
- Heavy automation requirements specifically for SaaS workflows
- Organizations with a dedicated SaaS ops function separate from IT
Where June takes a different approach.
The specific places the two platforms diverge in design and execution.
01
Unified asset + software, one platform
Torii is SaaS-only by design. June covers SaaS at parity, plus the device side (MDM, IdP, refresh, audit) in the same UI.
02
Helpdesk integration that knows your devices
Because June has device data, ticket enrichment includes the reporter's assigned devices, encryption status, OS version, and warranty. A SaaS-only tool can't surface that context.
03
Onboarding and offboarding cover both worlds
When an employee joins, June provisions software access and device assignment in one workflow. When they leave, both are reclaimed. Torii handles the SaaS half.
04
One vendor, one contract, one place to look
IT teams running Torii alongside a separate asset platform have two tools to keep in sync. June removes that.
Side-by-side.
Feature coverage by surface. Partial means it's supported but with caveats or via a partner integration.
| Capability | June | Torii |
|---|---|---|
| Software spend management | ||
| SaaS discovery (IdP + browser + procurement) | ||
| Usage tracking (web + desktop) | ||
| License reclaim automation | ||
| Renewal prep and contract management | ||
| Department-level spend reporting | ||
| Asset / device management | ||
| Live MDM + IdP inventory | — | |
| Device refresh planning | — | |
| Onboarding and offboarding device automation | — | |
| Audit / compliance device reporting | — | |
| Helpdesk integration | ||
| Automatic ticket enrichment | ||
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.
Torii is a trademark of its respective owner. Capability claims on this page reflect our understanding of Torii's public product at time of writing and are directional rather than exhaustive. Verify against current vendor documentation before final selection.