What a perpetual licence with an update window actually means

Software licences are read once, at purchase, when everyone is optimistic. The differences between them only become visible at the awkward moments: when a renewal invoice arrives, when a developer leaves, when someone runs a fresh install two years later and the build fails. This article is about those moments.

The three models, and what happens when you stop paying

The middle row is the one most developer tools use, and it is the one most often misunderstood — usually as the top row. The distinction matters most for the scenario nobody plans for: a project that goes quiet for eighteen months and then needs one small change. Under a subscription, that change starts with a purchase. Under a perpetual licence, it starts with npm install.

How Styloviz implements it

Styloviz Pro is a perpetual licence with an update window. The mechanism is worth explaining precisely, because "you keep what you bought" is easy to write and harder to actually build.

1. Your licence key never expires. There is no expiry date in it, and nothing in the components reads one.
2. A 12-month plan gives you twelve months of updates. A lifetime plan has no cutoff at all.
3. When your window closes, the private registry filters the package metadata it serves your key so that it lists only versions published on or before your cutoff.
4. npm then resolves against that filtered list and installs the newest version you are entitled to. It never sees the newer ones, so there is nothing to fail on.
5. Renewing extends the cutoff. Nothing is re-downloaded and nothing is re-keyed.

The practical consequence: a lapsed licence is not a broken build. It is a build that resolves to the last version you were entitled to — the same one it resolved to the day your window closed. A fresh clone on a new laptop three years later installs and compiles.

What does not happen

Nothing in a Styloviz component checks a key at runtime. There is no banner, no watermark, no console warning and no degraded mode in your application if a key is absent, wrong or expired. The licence is enforced at install time, at the registry, and nowhere else.

This is worth checking with any commercial UI vendor, because the alternative is a licence term that permits your production application to display a notice to your users about your billing status. Read that clause specifically. It is a question about what your customers might see, not about what you owe.

Seats, and what counts as one

Styloviz is licensed per team, not per developer per year. A Personal licence covers one developer; Team covers ten; Enterprise covers twenty-five. A seat is a developer who builds with the Pro packages — not a designer reviewing a pull request, not a CI runner, and not an end user of what you ship.

The per-seat arithmetic is the part worth doing yourself: a Team licence at $449 covering 10 developers is a tenth of that per developer, once, with twelve months of updates — and the licence does not lapse into unusability afterwards.

And the free tier has no thresholds

92 of the 169 components are MIT licensed, with no revenue cap, no employee count, no developer limit and no funding condition. 3 of the 21 templates are free on the same terms. MIT means what it always means: use it commercially, modify it, ship it, and you owe nothing and re-confirm nothing.

That is a deliberate contrast with conjunctive free tiers, which require you to satisfy every one of several conditions and to re-confirm annually that you still do. A threshold you can cross without noticing is a licence risk carried by whoever forgot to re-check.