Josys sits in the space where device management and SaaS management meet. The pitch is that your people, their machines and their applications belong in one record rather than three, and for a lot of IT teams that is exactly the problem they have.

TL;DR

  • Josys manages devices and SaaS applications together, joined by the person who uses both.
  • It publishes no rate. The pricing page routes to a quote and describes custom pricing.
  • The joined view is the differentiator, and it is most valuable at joining and leaving.
  • Offboarding is where this category earns its cost, because that is where leaks happen.
  • It is a management and record platform, not a logistics one. It ships nothing.
  • Judge it on which of your systems it reads automatically, not on the feature list.

What the joined view actually buys you

Most companies run three disconnected lists. A device list somewhere in IT. An application list that finance can partly reconstruct from card statements. And an employee list in the HR system, which is the only one that is reliably current.

Each is maintained by different people on different rhythms, and the questions that matter sit across all three. Who has a laptop and a design seat and left in August. Which applications are paid for per seat and have seats attached to nobody. Which machines went to contractors whose engagement ended.

Those questions are tedious rather than hard. That is exactly why nobody answers them, and why they compound quietly. A platform that joins the three lists turns a half-day of cross-referencing into a filter, and the first time you run it is usually the moment somebody in finance gets interested.

What it publishes

Read on 29 October 2026 with scripts and styles stripped out first, because minified code reliably produces fake currency matches in this category.

No rate survives that strip. The page describes custom pricing and routes to a quote request and a demo. No tiers with numbers, no per-user figure, no stated minimum.

That is the category norm now rather than an outlier. Of the asset and SaaS platforms checked on the same day, only one published an entry figure. So the absence tells you to plan for a sales cycle, and not much else.

What it does mean practically is that you cannot sanity-check a proposal against a public list. Ask for the quote broken into components, usually asset count, user count and integrations, so that you can see what drives it and forecast year two.

Offboarding is where this earns its money

If you buy a platform in this category and only use it for one thing, use it for leavers.

A departure touches a device, a set of application seats and an identity, and in most companies those three are handled by three people who do not talk on the same day. The seat keeps billing. The machine stays in a drawer. The account stays live longer than anybody intends.

What to do:

  • Take your last twenty leavers and check all three dimensions for each.
  • Count seats still billing more than thirty days after a departure.
  • Count devices with no confirmed return.
  • Multiply the first number by twelve months to see the annual leak.
  • Use that figure as the budget case, because it is real and it is yours.

That exercise takes an afternoon and it is the most honest business case you can build for this category. It also tells you whether you need a platform at all, because a company with tidy offboarding and forty people probably does not.

How the category lines up

VendorPrimary jobPublished rateWatch for
JosysDevices and SaaS joined by personQuote onlyRegional depth varies
ToriiSaaS management and spendQuote onlyLight on hardware
SetylAsset and spend recordsEntry tier publishedPublished figure is a floor
OomnitzaAsset workflows and automationQuote onlyEnterprise shaped
LansweeperNetwork discoveryQuote onlyFinds devices, no spend view
RemoAssetLogistics with a tracked registerOne tier publishedNo discovery, no licence management

Disclosure next to the row it concerns. RemoAsset is our own product, built by the people who publish this site, and it sits last in that table deliberately. This article is about knowing what you own and what you pay for, and RemoAsset does no network discovery and no software licence management, so it cannot find an unenrolled machine and it will not tell you about a duplicate seat. Those are the two jobs the rest of this table exists to do. What RemoAsset covers is the physical side: buying, renting, leasing, shipping, retrieval and wiping, with a register of what it handled. Its Subscription tier is the only tier that publishes a figure, from $1,499 per year. For the problem this page describes, Josys is the closer fit.

Where it is likely to struggle

The joined view is only as good as the integrations feeding it, which is true of everything in this category and is the single question worth most of your evaluation time. A platform wired into your identity provider, your device management and your finance system is accurate. One fed by periodic uploads looks identical in a demo and drifts within a month.

Ask for the integration list and compare it against your actual stack, including the awkward internal tool nobody mentions. The gaps are where manual work lives forever.

Regional depth is the second thing to probe. Vendors in this space often have deeper coverage in their home market, and that shows up in support hours and in which local applications are recognised automatically. Worth asking directly if your team is spread wide.

Checklist before the demo

Checklist:

  • Your leaver-leak number from the exercise above.
  • Your real integration list, including the awkward ones.
  • Asset count and user count, since both drive the quote.
  • Where your team sits, for a question about regional support.
  • Implementation effort in working days, not elapsed weeks.
  • Whether your problem is actually physical, in which case this is the wrong aisle.

Final thoughts

Josys is a reasonable candidate if your pain is that devices, applications and people live in separate lists that nobody reconciles. That is a common and genuinely expensive problem, and the joined view is the right shape of answer to it.

Do the leaver exercise before the first call. It gives you a number, it tells you whether you need this at all, and it stops the evaluation being decided by whichever demo was most polished.

How much does Josys cost?

It does not publish a rate. As of 29 October 2026 the pricing page describes custom pricing and routes to a quote request, with no tiers, no per-user figure and no stated minimum. Ask for any quote to be broken down by asset count, user count and integrations, which makes the drivers visible and lets you forecast the second year rather than being surprised by it.

Does Josys ship or retrieve laptops?

No. It manages and records devices and applications, which is a different job from the physical logistics of buying machines, delivering them to people and getting them back afterwards. If your main difficulty is getting a laptop to somebody in another country, or recovering one from a person who already left, that needs an equipment lifecycle vendor instead.

What is the difference between Josys and a SaaS management tool?

Scope. A pure SaaS management product concentrates on applications, seats and spend. Josys covers applications and devices together, joined by the person using them. Whether the extra hardware dimension is worth it depends on whether your device record is already reliable, because if it is then a software-only tool may cover the gap more cheaply.

How do we build a business case for this?

Take your last twenty leavers and count two things: software seats still billing more than a month after the departure, and devices with no confirmed return. Multiply the seat number by twelve to get an annual figure. That number is specific to you, it is defensible in a budget conversation, and it frequently turns out to be larger than the platform costs.

What should we check about integrations?

Compare the vendor’s integration list against your real stack rather than your idealised one, and include the internal tool nobody puts on the architecture diagram. Anything not covered becomes permanent manual work, and manual work is what makes these records drift. A platform fed automatically stays broadly honest, while one fed by uploads looks identical in a demo and decays quickly.

Is this worth it under a hundred people?

Often not. Below about a hundred people the cross-referencing is still tractable by hand, and a maintained spreadsheet plus disciplined offboarding will catch most of the leakage. The case strengthens when the number of joiners and leavers outgrows what one person can track alongside their actual job, or when somebody starts asking for evidence rather than estimates.