PrimeNG's paid licence pushes Angular teams to weigh MIT migration paths

What changed in PrimeNG's licensing

A detailed post on dev.to by developer mkornas recaps a shift that has left many Angular teams redoing their budgets: on 28 June 2026, PrimeNG moved from MIT to a commercial licence. According to the post, PrimeNG 22 and later ship under the PrimeUI licence, as do PrimeVue 5+ and PrimeReact 11+, and the GitHub repository switched to security-fixes-only maintenance on the same day. Versions up to and including PrimeNG 21 remain MIT, since an already-granted licence cannot be withdrawn.

The reported pricing works out to $599 per developer for a perpetual licence with a year of updates, rising to $799 from 2027, plus $399 per developer per year to continue receiving updates after the first year. A free community licence exists, but eligibility requires meeting every one of four conditions: under $1M revenue, fewer than five developers, fewer than ten employees and under $3M in outside funding, with annual renewal and runtime checks. The post also notes that some of the components admin applications lean on hardest — Scheduler, Text Editor, Charts and Task Board — are sold separately under PrimeUI PRO, priced from $399 to $799, with a data grid, spreadsheet, gantt and diagram announced for later in 2026.

The four options

The dev.to guide frames the decision as a choice between four paths. Teams can freeze on PrimeNG 21, which stays MIT and functional but will not track future Angular releases — buying time rather than a solution, in the author's words. They can pay: for a 20-developer team that is roughly $12k now, $16k from January, and around $8k a year thereafter, before any PRO widgets. They can move to the community fork, Optimus UI by the OpenNG Foundation, which keeps selectors and class names identical and is therefore the least disruptive move, though it is volunteer-run and inherits PrimeNG's open issues. Or they can migrate to a library that has been MIT from the start.

The MIT migration route

The bulk of the post documents that last option using mk-kit, an Angular 22 component library the author is closely involved with, so the claims should be read as first-party promotion as much as neutral analysis. As described, it offers 180 MIT-licensed components with no runtime licence checks, signal-based inputs, standalone OnPush components, zoneless operation, WCAG 2.1 AA support and theming built on CSS custom properties. It is deliberately narrower than PrimeNG — there is no PDF viewer, spreadsheet, diagram editor, terminal or dock — but the categories PrimeUI sells as PRO, such as charts, rich text editing, an event calendar and a kanban board, sit in the free package.

The practical draw is a migration schematic. Running it in dry-run mode first produces a Markdown report before any file is touched, and both libraries can coexist in a single application during the transition. The schematic rewrites imports and class names, applies roughly 150 selector rules, handles mechanical input renames such as severity to tone, and updates the Angular and package configuration. Its guiding rule, according to the post, is that it never rewrites anything it cannot make compile: dialogs, toasts, [model]-driven menus and components with no counterpart are flagged with template comments and report entries rather than guessed at.

The known gaps are listed up front: no organisation chart, dock, terminal, meter group or float-label variant; select options supplied as data rather than projected elements; and Promise- and signal-based services rather than Observables. The suggested order of work is dry run, theme swap, schematic application, then removing PrimeNG from package. once the report is empty.

Why it matters

A licensing change to a decade-old default library is not an abstract legal matter; it converts a free dependency into a recurring line item with a hard price step on 1 January 2027 and a compatibility clock on PrimeNG 21. Teams now have to make an explicit choice — pay, freeze, fork or migrate — and each option carries real migration or maintenance cost. It is worth noting that this account comes from a single post written by someone promoting an alternative, so the pricing figures and library claims should be verified against PrimeTek's official terms and hands-on evaluation before any commitment. The closing argument, though, is hard to dispute: whichever path a team picks, it should be a decision rather than a default.