If you are looking for Snow Software, the brand is gone. Every version of its old domain now returns a redirect to Flexera, and Flexera’s own homepage does not mention the name at all. This is a short, practical guide to what we verified, what still works, and what to check in your own documentation.
TL;DR
- The old domain and its pricing page both resolve to Flexera’s homepage, not to a product page.
- Flexera’s homepage names the retired brand zero times, so this is an absorbed brand rather than a co-branded one.
- The one surviving string on that page is the platform name Snow Atlas, which is worth knowing if you are searching internally.
- Flexera publishes no price either. Its pricing URL routes to a contact page with no figures.
- Nothing about your licence position changed. A brand retirement is a procurement and documentation event, not a technical one.
- The real work is finding the dead name in your own runbooks, contracts and dashboards before somebody follows a link that no longer means anything.
What we verified about Snow Software
Checked on 30 October 2026, with a browser user agent so that bot blocking could be ruled out as a cause:
| What was checked | Result | What it tells you |
|---|---|---|
| The old root domain | 200, resolving to Flexera | Redirect, not an error page |
| The same domain with the www prefix | 200, resolving to Flexera | Both hostnames behave identically |
| The old pricing page | 200, resolving to Flexera’s homepage | Lands on a homepage, not an equivalent page |
| Flexera homepage, retired brand name count | Zero | Fully absorbed rather than co-branded |
| Flexera homepage, the string Snow Atlas | Present | The platform name survives where the brand does not |
| Flexera pricing URL | Routes to a contact page, no figures | Quote-based on both sides of the change |
Two details in that table are worth separating out, because they are the ones that catch people.
First, the old pricing page returns a success code. It does not 404. A link checker pointed at your documentation will report that URL as healthy, because it is: it successfully delivers a homepage that has nothing to do with what the link promised. This is the most common way a dead reference survives an audit.
Second, the redirect goes to a homepage rather than a matching product page. A redirect to an equivalent page means somebody mapped the old structure onto the new one. A redirect to the front door means that mapping was never done, and anyone following an old deep link starts from the top.
What this does not change
Be clear about the limits of a brand retirement, because the instinct is to treat it as bigger than it is. Your entitlements, contract, renewal date and installed data all sit where they sat. What changed is a name and a set of URLs.
That has happened repeatedly in this corner of the market and the pattern holds each time. When Kandji became Iru, the org-level setup, the enrolment requirements and the advice were all still correct, and the correction was a rename plus a paragraph rather than a rewrite. The cheap fix is cheap precisely because the underlying advice survives.
So resist the urge to re-evaluate your licence tooling because a logo changed. Re-evaluate it at renewal, on the merits, like anything else.
What it does change: your own documentation
The actual cost of a rename lands wherever you wrote the old name down. Those places are easy to list and tedious to check, which is why they get skipped.
What to do:
- Search your runbooks and onboarding docs for the old product name, not just the old domain, because most mentions are prose rather than links.
- Search your contract and renewal calendar for the old entity name, and confirm with your account contact which legal entity you now deal with.
- Check any dashboard, report title or saved search that carries the old name in its label.
- Check your own internal wiki for deep links to the old site, since those now land on a homepage.
- Leave exactly one deliberate bridge mention per document, so a colleague who only knows the old name can still find the page.
That last point matters more than it sounds. A global find-and-replace that removes every trace of the old name makes your documentation accurate and unsearchable at once. Somebody will search the old name in eighteen months. Give them one hit that explains the change.
The rename trap worth knowing
There is a specific way these clean-ups go wrong. If you run a global rename across a repository or a wiki, the pass will also rewrite the one document whose job is to record the change. The note explaining that the old name is retired gets its own subject renamed out of it, and the explanation stops making sense.
The fix is mechanical. Park the passages you are deliberately preserving behind a placeholder token, run the global rename, then restore them. Do the exclusion before the rename, not after, because afterwards you are trying to reconstruct which mentions were intentional.
Same principle applies to a link audit. Before reporting a reference fine because it returns a success code, follow it and look at where you land.
A worked example
A 400 person company with a software asset management practice built over four years. Three runbooks name the old product, an onboarding checklist links to the old documentation site, two dashboards carry the old name in their titles, and the finance calendar’s renewal reminder uses the old entity name.
None of those stops work today. All of them will confuse somebody. The onboarding link is the worst, because a new starter following it lands on an unfamiliar homepage with no way of knowing they are in the right place. That is an hour of somebody’s first week, repeated for every hire.
Total effort to fix properly, including the deliberate bridge mentions, is an afternoon. Total effort to fix badly, by renaming everything including the explanation, is twenty minutes and creates a different problem.
The adjacent problem nobody renamed
Licence management tells you what software you are entitled to and what is installed. It does not tell you where the laptop is, get it to a new starter in another country, hold a spare, or recover it from someone who left. Those are physical jobs, and they are unaffected by anything a vendor does to its brand.
Disclosure: RemoAsset is our own product, owned by the same people who publish this site. It covers procurement, international shipping, tracking, retrieval and wiping. It belongs in this article because an asset practice usually has both halves and only one of them just changed names.
Its limits deserve the same plainness. RemoAsset is not an MDM, so it enrols devices but does not configure or secure them, and you would run a management tool as well. It is also not a certified ITAD, meaning it wipes machines but is not the answer when you need certified destruction with documentation. And its coverage is not every country, so check the market list against your own first.
The verdict
There is no review to write here, because the product you were searching for no longer carries that name. Flexera, formerly Snow Software, is where the capability lives now, and neither side of the change publishes a price, so your evaluation runs through a sales conversation exactly as it did before.
The work worth doing this week is the documentation sweep, because it is small, it is cheap, and it stops a colleague wasting an afternoon. Start from the Flexera site and confirm the current state yourself, since brand consolidation in this market tends to arrive in stages rather than all at once.
Checklist:
- Runbooks and onboarding docs searched for the old product name as prose, not only as a link.
- Contract and renewal calendar checked for the old entity name, and the current entity confirmed.
- Dashboard and report titles updated.
- Deep links to the old site replaced, since they now land on a homepage.
- Exactly one deliberate bridge mention left per document.
- Link audit repeated by following redirects rather than reading status codes.
Does Snow Software still exist?
Not as a brand. Checked on 30 October 2026, the root domain, the www version and the old pricing page all return a success code and resolve to Flexera, and Flexera’s homepage does not mention the retired name once. The capability has been absorbed rather than co-branded, so there is no transitional landing page explaining the change to anyone who follows an old link.
What happened to the old website?
It redirects, and the detail that matters is where to. The old pricing URL lands on Flexera’s homepage rather than an equivalent pricing page, which means the old site structure was not mapped onto the new one. Anyone following a saved deep link arrives at the front door and has to navigate from there, so your internal links need updating rather than trusting.
Will a link checker catch my dead references?
No, and this is the main practical risk. The old URLs return a success code because they successfully deliver a homepage, so an automated audit reports them as healthy. The only reliable check is to follow each one and look at the page you land on. A redirect to a homepage is a broken reference wearing a working status code.
Does this change my licence position?
No. Entitlements, contract terms, renewal dates and installed data are unaffected by a brand retirement. What changed is a name and a set of URLs. The same pattern held when Kandji became Iru, where the underlying setup requirements and advice were all still correct and the correction amounted to a rename plus a paragraph. Re-evaluate the tooling at renewal, on the merits.
Does Flexera publish pricing?
No. Its pricing URL routes to a contact page carrying no figures, so the purchase is quote-based on both sides of the rename. That is now normal across this category rather than a warning sign, but it does mean budgeting requires a conversation. Go in with a module list and a maximum commitment term, because those are what the number will turn on.
What is Snow Atlas?
It is the one string from the old brand still present on Flexera’s homepage, where the product name itself is absent. That is useful mainly as a search term: if you are hunting through your own documentation or a vendor portal for the old capability, the platform name may find things the product name no longer does. Treat it as a breadcrumb rather than confirmation the old brand survives.