License consumption tracking for Altair token pools

Engineering teams running Altair's token-based licensing model face a specific, recurring administrative problem: they don't know until after the fact which jobs, workflows, or software versions consumed more tokens than expected. Users explicitly call out that newer Altair versions 'take more tokens' and that license point costs have risen with recent releases — but there's no straightforward way for a team lead or IT manager to see, in real time, which engineer ran which tool for how long and what it cost in tokens.

The gap persists because Altair's incentive structure runs in the opposite direction — higher token consumption means higher renewal spend, and a tool that helped customers optimize their consumption would reduce Altair's revenue. The buyer here — the engineering IT manager or procurement lead managing the Altair contract — is entirely different from the daily users, and the daily users have no reason to self-report their consumption patterns.

What teams do today is export raw log files from the Altair License Manager, parse them manually or in Excel, and try to reconstruct usage patterns retroactively — usually only when they're about to renew or when they've burned through their token pool unexpectedly mid-project. Nobody is watching the pool drain in real time, and nobody is flagging when a particular workflow (say, a large assembly in Inspire) is consuming tokens at a rate that will exhaust the pool before a project deadline.

This recurs every renewal cycle, every time Altair releases a version with different token weights, and every time a team grows or takes on a larger project. The cost of getting it wrong is either over-purchasing tokens on renewal (common, because teams pad their estimates after getting burned) or hitting a wall mid-project and waiting for a license expansion to be processed.

What to build

Build a lightweight daemon that reads the Altair License Manager log in real time, maps token consumption to specific tools, versions, and users, and surfaces a dashboard with burn rate, projected pool exhaustion date, and per-user and per-tool breakdowns — with email alerts when burn rate exceeds a configurable threshold.

Where to start

Target companies with 20+ Altair seats who are running HyperWorks Units (HWU) pools across multiple departments — they have the most pain from unexpected consumption and the most organizational pressure to justify the license cost to finance at renewal.

The hard part

Altair's license log format has changed across versions and isn't officially documented as a public API, so parsing it reliably across customer environments requires either reverse-engineering multiple log formats or finding enough early customers to validate the parsing logic before it breaks in an edge case.

How it makes money

Flat monthly fee per Altair license pool managed (not per seat), because the value is organizational visibility, not individual use — roughly $200–$600/month depending on pool size, with a one-time setup and log-parsing configuration fee.