We created LicensePulse after years of working with enterprise software licensing and seeing how difficult it is for engineering organizations to understand software usage, control licensing costs, and prepare for vendor renewals.
LicensePulse exists to help engineering organizations make better software licensing decisions using accurate operational data rather than spreadsheets and guesswork.
The problem we set out to solve
Engineering software is among the most expensive line items a technical organization carries, and among the least measured. A simulation or CAD estate is licensed through concurrency, tokens, and pack stacking, which are difficult to model and almost impossible to reconcile against a contract by hand. The data that would answer the question sits in license daemon logs that were never designed to be read by finance, procurement, or leadership.
So the questions that matter get answered by estimate. How many licenses do we actually need? Which of these are idle? What happens if we cut ten percent? What should we agree to at renewal? Each of those is a decision worth a great deal of money, and each is routinely made without the underlying numbers.
Why the waste is not carelessness
The common framing is that organizations waste a third of their software spend on idle licenses through poor hygiene. We think that reading is wrong, and it matters because it leads to the wrong product.
When an organization cannot measure its position, buying a cushion is the correct decision. A denial during a program-critical week costs more than a spare license. An audit finding with penalty multipliers costs far more. That surplus is an insurance premium bought without the data to price it, not negligence.
This is why we do not lead with savings. Asking an organization to cut its cushion without first reducing the uncertainty that justified it is asking it to cancel insurance while the risk stays the same. We start with an accurate measurement, and the savings come after it.
The same logic explains something every license administrator knows: peak concurrency is contaminated data. An engineer denied a license once during a deadline will hold a session open for years afterwards. That behavior is individually rational and collectively expensive, and it quietly corrupts the exact number a renewal decision rests on. Separating real demand from defensive habit is part of what measurement is for.
What we built
- A read-only agent: a single file of standard-library Python. It runs inside your network, polls your FlexLM (FlexNet) or RLM daemon every five minutes, and pushes summary records out over HTTPS. It opens no inbound port, accepts no commands, and has no remote-execution path. The source is downloadable; read it before you run it.
- Concurrency, not seat counts. We report peak concurrent usage, denial events, and utilization by hour of day. How a solver is used on the night shift is a point you can negotiate on, but only with the data behind it.
- Numbers that show their work. Every figure traces back to the check-out records it came from. At a renewal someone across the table will question every number, and a figure you cannot defend is worse than no figure at all.
- Output shaped around the renewal. The product's job is to make you the best-prepared party in the room, well before the meeting happens.
What we will never do
Three commitments matter more to us than any feature, and we will write all of them into a contract.
We take no money from software vendors. No referral fees, no partner programs, no marketplace revenue share, no paid certifications. We cannot give honest advice on a renewal while being paid by the vendor on the other side of it. That revenue is available to us and we are choosing not to take it, so we say so here.
We will never sell your data, and it will never move toward a vendor. That includes anonymized or aggregated data and data in research reports. If we ever build pooled price benchmarks, participation will be opt-in, every contributor will benefit from it, and the data will only ever move in the buyer's direction.
We will never build individual surveillance. The same data that shows a product is over-provisioned could show which engineer held a license for four hours. We aggregate to teams and products, and we decline the work that would require anything narrower.
The full list, including how we handle exports, retention, and vendor subpoenas, is on our Trust page.
Where we are today
We would rather you hear this from us than discover it.
LicensePulse is early. There are no customer logos on this site because we do not yet have customers to name, and we have removed the invented statistics that were on these pages before. We are a small team, so we do not operate a 24/7 on-call rotation and we do not sell a service level we cannot measure. We hold no security certification (no SOC 2, no ISO 27001, no penetration test), and no audit is scheduled. Our security roadmap lists all of this plainly, including the parts that are unflattering.
What we can offer instead is that you are never trapped. Everything exports, in an open documented format, at any time, with no gate. If we were to disappear tomorrow you would keep your data, your history, and your evidence, and you could walk into your renewal without us. We would rather earn a renewal every year than hold anyone with an export button that does not work.
Who we build for
Engineering organizations of roughly 100 to 2,000 people running five or more engineering software vendors across one or more license servers, spending somewhere between $200K and $5M a year on them, where renewals are handled by someone who already has another full-time job.
If that describes your organization, we would like to talk. The first call is not a sales pitch. Our early customers will shape what this becomes, and we would rather build it with people who have lived the problem than guess at it.