Autodesk offers two ways onto the same products: a named-user subscription — one person, one product or collection, unlimited use for a flat annual term — and Flex, a prepaid pool of tokens burned at a published daily rate whenever anyone opens a product, expiring 365 days after purchase. The decision rule is access days: frequent users are cheaper on subscription, occasional users are cheaper on tokens, and the crossover for each product can be computed from your own usage reports. The estates that get this wrong are not the ones that pick a side — they are the ones that never run the arithmetic.
Published 20 March 2026 · Last reviewed 23 March 2026
The named-user subscription is the model Autodesk moved its whole base onto after retiring new perpetual sales and, in the early 2020s, multi-user network licensing. One assigned person gets one product — or an industry collection — with unlimited use for the term, annual or multi-year. Assignment is personal: sign-in is how the license is enforced, and sharing a login is a compliance breach, not a workaround.
Flex is the occasional-use answer. The organization prepays a pool of tokens; any user with access who opens a Flex-enabled product draws that product’s published daily rate from the pool and has the product for 24 hours, whether they use it for five minutes or eight hours. Rates differ by product — a day of a flagship authoring tool costs several times a day of a viewer-class tool — and are set out in Autodesk’s Flex rate sheet. Tokens expire 365 days from purchase; under standard terms, unused tokens are neither refunded nor rolled over.
Structurally this is the same trade every consumption model presents: the subscription buys cost certainty per person and is indifferent to intensity; Flex buys precision per access day and is indifferent to who shows up. The distinctive Autodesk twist is the daily granularity — a token day is the unit, not an hour and not a month — plus the hard expiry clock on the pool itself.
This guide compares licensing models as published by the vendor; it is general information, not legal or licensing advice for your situation, and it names no firms. Token rates, product eligibility and program terms shift — verify current rates against Autodesk’s published rate sheet and your own agreement. The firm directory lists Autodesk-capable advisors with balanced pros and cons, listed, not ranked.
| DIMENSION | NAMED-USER SUBSCRIPTION | FLEX TOKENS |
|---|---|---|
| Unit | One person, one product or collection, per term | One product, one 24-hour access day, at the product’s token rate |
| Who can use it | The assigned individual only; reassignment per program rules | Anyone in the organization with access to the pool |
| Intensity | Unlimited use; cost indifferent to days worked | Metered per day per product; brief use burns a full day’s rate |
| Commitment | Per-seat term, annual or multi-year | Pool prepaid up front; tokens expire 365 days from purchase |
| Unused capacity | A quiet seat still costs its full rate until the term ends | Unspent tokens are written off at expiry; no refund or rollover standard |
| Budget shape | Flat, predictable, headcount-shaped | Usage-shaped; needs governance to stay forecastable |
| Renewal posture | Seats dropped or downgraded at term end; multi-year locks the rate and the count | Pool resized at each purchase — the lever is always available |
| Compliance surface | Login sharing and legacy installs against named-user terms | Largely self-licensing per day used; the risk moves to cost control |
The two rows that decide real money are intensity and unused capacity. A subscription wastes money on people who rarely open the product; Flex wastes money on people who open it daily — and on tokens that quietly time out. Both wastes are measurable in advance from data you already have.
For each product, the crossover is a simple division: the annual subscription cost against the product’s daily token rate gives the number of access days at which the two models cost the same. Industry commentary commonly places that crossover somewhere around 60–75 days per user per year for mainstream authoring products — an indicative range only, since it moves with every rate-sheet and price revision. The point is not the number; it is that the number is computable for your estate, today, from Autodesk’s published rate sheet and your usage reporting.
The practical method advisors use: pull per-user, per-product access-day counts from the admin console for a trailing year, sort each product’s user population by days used, and the histogram virtually draws the answer — a block of daily users who belong on subscriptions, a long tail of occasional users who belong on Flex, and a contested middle where the decision is genuinely close and secondary factors (multi-product use, seasonality, contractor churn) tip it.
Two refinements matter. First, multi-product days stack: a user who opens two Flex products in one day burns both rates, where a collection subscription would have covered both — multi-product users hit the crossover much sooner than single-product arithmetic suggests. Second, collections change the threshold: a collection seat costs more than a single-product seat but covers the whole stack, so the right comparison for a multi-tool user is collection-vs-tokens, not product-vs-tokens.
Named-user fits the production core: drafters, designers and engineers in the product daily or near-daily, where unlimited use at a flat rate is unambiguously the cheaper shape and the multi-year term converts a known need into a locked rate. It also fits anyone on a collection’s breadth, and roles where workflow continuity matters more than the marginal cost of a quiet week.
Flex fits the long tail that every design-adjacent organization carries: project managers who open a model a few times a month, reviewers and checkers, site and field staff, seasonal contractors, training cohorts, and specialists whose tool is needed two weeks a year. It also fits genuine uncertainty — a new team whose usage pattern nobody can forecast yet burns tokens for a quarter and generates exactly the data the subscription decision needs.
Mixed is the steady state. Almost no estate of size lands cleanly on one model; the realistic outcome is a subscription core plus a governed token pool, re-balanced annually as the usage histogram moves. At the largest scale, token-based enterprise agreements extend the consumption logic estate-wide — a different negotiation with the same underlying meter, and the same governance burden at larger scale.
The named-user renewal is a conventional seat negotiation: count, mix, term length and rate protection. Autodesk’s commercial posture favours multi-year terms — price-stability for commitment — which is worth taking only on the seats the histogram proves are permanent. The under-used middle of the estate is the negotiation’s real subject: every seat moved to Flex before the renewal is leverage, and every seat left unexamined renews by inertia.
Flex purchases negotiate differently: the lever is pool size and purchase timing rather than per-seat rate, and the expiry clock cuts both ways — oversized pools donate the residue to the vendor at day 365, undersized pools force top-ups bought without leverage mid-project. Sizing purchases to roughly a year of measured burn, and calendaring the re-purchase as a decision rather than a reflex, keeps the lever in the buyer’s hand.
On compliance, the models trade places. Named-user terms make login sharing a breach and leave legacy serial-number installs — the residue of the perpetual era — as the classic finding when Autodesk or its agents come asking; estates that migrated programs without retiring old installs carry exposure they have already paid to replace. Flex, by contrast, is largely self-licensing — a tokened day is a licensed day — but the meter converts governance failure into spend instead: an unwatched pool with broad access is a budget incident waiting to be discovered at the quarterly review. A licensing advisory engagement typically covers both faces: entitlement hygiene on the subscription side, burn governance on the token side.
The five-minute day. Opening a product to check one dimension burns the full daily rate. Populations that “just dip in” frequently are subscription users wearing token costumes — the per-day granularity punishes habitual brief use hardest.
Stacked rates. Two products opened in one day burn two daily rates. Multi-tool workflows that look occasional per product can be heavy in aggregate — run the crossover against the collection, not the single seat.
The expiry write-off. Tokens bought oversized “to be safe” expire at 365 days with no refund or rollover under standard terms. The write-off appears in no invoice and no renewal quote; it simply happens, annually, to estates that size pools by guesswork.
The unwatched pool. Flex access granted estate-wide without reporting discipline lets heavy users settle invisibly into the most expensive possible shape. The admin console’s usage reports exist precisely so this is caught in a month, not a year.
The contractor reflex. Issuing full subscriptions to short-term contractors because procurement knows how, then reassigning them late or never. Reassignment rules have limits, and a seat that outlives its contractor is pure shelfware — the population Flex was designed for.
The legacy install. Perpetual-era serial numbers still running alongside the new models are the most common audit finding in Autodesk estates. The model comparison above is irrelevant to an install that is licensed under neither.
Flex is a prepaid, organization-wide pool of tokens. When a user opens a Flex-enabled product, the product’s published daily rate is deducted and the user has 24 hours of access — however briefly the product is actually used. Rates differ by product and are listed in Autodesk’s Flex rate sheet. Tokens expire 365 days from purchase; unused tokens are not refunded or rolled over under standard terms.
It depends on the product’s daily rate and current pricing; commentary commonly places the crossover around 60–75 access days per user per year for mainstream products — an indicative range only. The defensible answer comes from dividing your subscription cost by the product’s daily token rate and checking your own usage reports against the result.
Yes — 365 days from purchase, with no refund or carry-over of unused tokens under standard terms. Plan purchases to measured annual burn rather than to worst-case demand, and treat each re-purchase as a sizing decision.
Yes. A subscription covers the products it names; the same user opening a different Flex-enabled product can draw tokens for it. Mixed estates need per-user, per-product reporting checked against assignments, or the two models quietly overlap at full price.
New perpetual sales ended years ago, and multi-user network subscriptions were retired in the early 2020s with trade-in paths to named-user. Named-user and Flex are the current models for most products, with token-based enterprise agreements for the largest estates. Legacy installs that outlived their entitlements remain the classic audit finding.
It narrows one class — a tokened day is a licensed day, so casual over-deployment becomes spend rather than breach. It does nothing for legacy installs or login sharing against named-user terms, and it converts the compliance discipline into a cost-governance discipline: the meter always runs.
Pulling the access-day histogram, computing the crossover per product at current rates, sizing the token pool to measured burn, and walking into the renewal with the under-used middle of the estate already re-shaped — that is precisely the work of an Autodesk licensing advisory engagement, and of renewal negotiation when the term ends. The Autodesk hub maps the vendor’s wider licensing world, and the directory lists every firm covering Autodesk — with balanced pros and cons, listed, not ranked. Choosing between them? Start with how to choose an Autodesk licensing partner.
The same flexibility-for-rate trade, seat-shaped →
Another vendor’s version of the model shift →
Every firm for this work →
The seat-count event, prepared for →
How this work is paid for →
Every field guide on the site →
Tell us the vendor, the service you need and where things stand, and we will route your brief to firms that genuinely cover that combination. The directory and matching are free for buyers, no vendor ever sees your brief, and we add no markup.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.