Instead of Snow License Manager
Stop renting Snow License Manager. Own your software licence desk.
We build your version around how you buy, assign and review software, bring your Snow records across and run it for you. Start with the evidence your licence owner needs each week.
Snow License Manager pricing is quoted privately. Its legacy base package is licensed by end-user and datacentre devices. Bring your contract so we compare the work you need with the bill you actually pay.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
The bill and the work behind it
Separate the licence desk from the wider platform
Snow combines inventory, licence rules and reporting. Your contract determines which parts you pay for. Its published legacy terms describe the device-based base package; no current public price is used here.
End-user devices
The legacy base package counts end-user devices. A growing computer estate changes the scale of the licence you need.
Datacentre devices
Servers and virtual servers sit within the datacentre definition. Check that part of the agreement separately from staff computers.
The base package
The listed base package includes Snow License Manager, Snow Inventory, the integration connector and the virtual management option.
Publisher-specific calculations
Snow supports licensing adjustments such as upgrade and downgrade rights. Identify which of those your own estate actually needs before planning a switch.
Reports and evidence
Licence purchases, required quantities and coverage appear in Snow reports. Those records also provide the starting point for a licence desk you own.
Taking the history with you
Snow documents report exports and separate downloads of related documents. Keep both the figures and the evidence behind them when you move.
Your own licence desk
Keep the weekly decisions beside their evidence
Reconciliation
See the gap between assignments and checked rights
Compare recorded demand with current purchases whose proof has been reviewed.
- check Separate each product and version
- check Exclude expired and not-yet-started rights
- check Keep complex licence terms visibly unassessed
- check Join the shortfall to the exact purchase proof still missing
Renewals
Review the renewal with the current position in front of you
A renewal date matters more when you can see the assignments and the evidence at the same time.
- check Show expired and approaching renewal dates
- check Identify renewals with a current recorded shortfall
- check Prepare a renewal decision brief in your business name
- check Keep the owner’s decision and supporting note with the product
Unused software
Review assignments before calling them spare
A retired computer or an old use date creates a review item. It does not authorise a removal.
- check Find retired devices and users still assigned software
- check Distinguish unknown use from old recorded use
- check Require evidence before recording a release
- check Compare the review list across your departments
Ownership
Keep the source records and the working papers
Your records, reviews and original imports stay together in a database you own.
- check Bring the agreed Snow report exports across in one step
- check Keep original columns for later mapping
- check Produce licence position and removal evidence papers
- check Add your contract owners, rules and questions as the business changes
Make it yours
Design your own Snow License Manager replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Snow License Manager. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your Snow License Manager data across and run it for you.
What it looks like
Ask it like you would ask a colleague
Real answers from the demo data that ships with Software Licences for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.
Software Licences for Claude Code
Connected to your own database
Which products have a shortfall, and which still need review?
HarbourCAD Professional 2026
- Publisher
- Fictional Harbour Software
- Metric
- device
- Purchased
- 3
- Evidenced
- 1
- Required
- 3
- Stale
- 2
- Balance
- -2
- Assessment
- SHORTFALL
HarbourCAD Viewer 2026
- Publisher
- Fictional Harbour Software
- Metric
- device
- Purchased
- 2
- Evidenced
- 2
- Required
- 1
- Stale
- 0
- Balance
- 1
- Assessment
- RECORDED COVERAGE
Kauri Documents 2026
- Publisher
- Fictional Kauri Software
- Metric
- user
- Purchased
- 3
- Evidenced
- 3
- Required
- 2
- Stale
- 1
- Balance
- 1
- Assessment
- PROVISIONAL
Southern Database Enterprise
- Publisher
- Fictional Southern Systems
- Metric
- review
- Purchased
- 0
- Evidenced
- 0
- Required
- 1
- Stale
- 0
- Assessment
- UNASSESSED
| Name | Publisher | Metric | Purchased | Evidenced | Required | Stale | Balance | Assessment |
|---|---|---|---|---|---|---|---|---|
| HarbourCAD Professional 2026 | Fictional Harbour Software | device | 3 | 1 | 3 | 2 | -2 | SHORTFALL |
| HarbourCAD Viewer 2026 | Fictional Harbour Software | device | 2 | 2 | 1 | 0 | 1 | RECORDED COVERAGE |
| Kauri Documents 2026 | Fictional Kauri Software | user | 3 | 3 | 2 | 1 | 1 | PROVISIONAL |
| Southern Database Enterprise | Fictional Southern Systems | review | 0 | 0 | 1 | 0 | UNASSESSED |
Ask it anything
Ten questions for your weekly licence review
Each question is answered by the fictional demo records. Snow already provides licence reporting; your own version can connect these checks to your business decisions.
Switching
How to switch from Snow License Manager
In practice, a move involves exporting your reports, mapping their fields, checking the imported records and running both systems side by side before switching over.
- 1
Export the Snow reports
Export Snow’s current Applications per computer and licence reports as CSV, which are the reports this import path uses. If your account does not offer them in that form, export what it allows and check the available report format with Snow License Manager. Decide which history to bring. Related agreements and other supporting documents need a separate export, so include them if you want them available for evidence review.
- 2
Load a trial import
Have the reports loaded through the import path, starting with its trial run before applying records. The importer accepts agreed English report columns for applications per computer and licence purchases, with standard date formats, and retains the original columns. If your Snow report layout uses different headings, map those fields first. The import does not verify purchase proof or certify that a recorded quantity grants coverage.
- 3
Review flagged records
Check what the import marks for review before treating the records as usable. New products and purchases start unassessed, and changed existing purchases stop for evidence reconciliation. Confirm that matching assignments updated as expected, repeated files did not create duplicate rows, and each purchase has proof checked before it counts toward coverage. Keep unsupported or complex licence terms marked for review.
- 4
Run both systems in parallel
Keep Snow License Manager running alongside the new database for a short period. Compare the same products, assignments, purchases, evidence and renewal decisions in both, then investigate differences rather than assuming the totals should match. The new desk covers reviewed device and named-user rights, not every Snow discovery or publisher licensing capability. Leave complex rights explicitly unassessed until they have been reviewed.
- 5
Switch off Snow
Switch off Snow License Manager only after you have checked that the records and evidence you need are present, reviewed the flagged items, and confirmed that your team can run its weekly licence review in the new database. Keep any source reports and related documents you still need under your own retention arrangements. Follow your normal process for ending access.
Where the real effort goes
The import itself is only part of the move. Most effort usually goes into mapping your report columns to your own fields, agreeing how your licence terms and evidence rules should work, and choosing how much history and supporting documentation to bring. Purchase proof still needs review, and complex rights may need specialist assessment. If you have Enterprise DNA run it, they handle this mapping and build the agreed rules into your version.
Not ready for a call?
Get your Snow License Manager switch plan by email
We will send you the step-by-step plan for moving your business off Snow License Manager, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your Snow License Manager switch plan is on its way.
Rather talk it through? Book a call arrow_forwardThree ways to own it
Do it yourself, have it customised, or have it run for you
Open source
Do it yourself
Free, open source
- 1 Clone the repo and run npm install
- 2 Run npm run demo with Claude Code, Codex, OpenCode or Cursor
- 3 Export the agreed Snow reports, check the date formats and run the trial import
- 4 Review the licence terms and purchase proof before relying on a position
Built around your business
We customise it
One setup fee, then a retainer for ongoing work
- check Your Snow exports mapped and reconciled against the originals
- check Your contract owners, fields and reviewed licence rules
- check Discovery connections or a web front end for your team
- check A different stack if your business needs one
Omni by Enterprise DNA
We run it for you
One setup fee, then a monthly retainer
- check Installed with access and backups agreed
- check Inventory evidence and renewal routines connected
- check Working papers and review drafts prepared from your records
- check Operated through Omni by Enterprise DNA with the rest of your business
Questions
Instead of Snow License Manager, answered
Is this a full replacement for every Snow calculation? expand_more
The free version covers the weekly desk for reviewed device and named-user rights. Snow has broader discovery and publisher licensing capabilities. We assess the rules and connections your estate needs, then build the agreed work into your version. Complex rights stay marked for review until that work is done.
Can we bring our Snow history across? expand_more
Yes. The free version accepts agreed English report columns for applications per computer and licence purchases, with standard date formats. Original columns are retained. Local report layouts need mapping, related documents need a separate export, and purchase proof must be checked before it counts as coverage. We handle that work in your version.
Does a green position mean we are legally compliant? expand_more
No. A recorded position is based on the evidence supplied and the rules reviewed. Missing inventory, complex use rights and incomplete contracts need the licence owner’s attention. The working papers show the basis of the calculation and remain drafts for review.
Will it remove unused software or contact a supplier? expand_more
No automatic removal or sending is included. It lists assignments to investigate, drafts the renewal request and records a release only when a person supplies confirmation. We agree any additional actions and controls when building your version.
What does it cost, and can our team have a screen? expand_more
The free version has no licence fee. Hosting, an agent subscription and your time are separate costs. Enterprise DNA builds your version for a setup fee and then a retainer, including a screen or connections when agreed. Sam reviews your actual Snow invoice and required work before recommending a switch.
Bring your Snow contract and one licence report
Spend 30 minutes with Sam. Show the annual bill, the records you review and the work that still needs checking by hand. We will map out your own licence desk and the connections it needs.
Software Licences for Claude Code is free and open source, published by Enterprise DNA.
Done paying for Snow License Manager?
Get your version built