Optix Licensing in Plain Terms: Tokens, Entitlements, and What "Pre-Activated" Really Means

Licensing is nobody's favorite part of a project. But with FactoryTalk Optix it's worth ten minutes up front, because the decisions you make while sizing an application are the ones you live with for years and a few are genuinely hard to undo.

There are two different licenses

The most common mix-up is treating Optix licensing as one thing. It's two.

Studio Pro licenses the design software and is tied to a user — the person building the application. Runtime licenses the application running on a device in the plant, activated with a 25-character entitlement key. That key isn't needed for Studio Pro, which sends people hunting for the wrong credential more often than you'd think.

Tokens: what your application is allowed to do

Runtime isn't licensed per seat or per panel. It's sized in tokens, consumed by the capabilities your application uses so token count is a design constraint, not just a line item.

Rockwell's Runtime Sizing wizard tallies tokens across four things: presentation (native client, web clients, or both), features you switch on, controller connections, and OPC UA interoperability. The total maps to a package size from XS to XL.

The one that burns people is web clients, which are counted by concurrent sessions. It's easy to think "we'll add web access later" and find that later means buying up a tier. If there's any chance operators, maintenance, or a plant manager will want browser access from a tablet, count those sessions now.

Rockwell's own advice is worth following: buy one size larger than the wizard suggests. Applications grow in ways nobody plans for — a second web client during commissioning, another controller when the line expands. Headroom is cheaper than hitting a ceiling mid-project.

What "pre-activated" means for your deployment target

OptixPanel terminals and the Edge Compute modules ship with Runtime embedded — they run at first power-up. OptixEdge arrives with a factory entitlement sized by catalog number. Deploy to a Windows or Ubuntu machine and nothing is pre-licensed: you install Runtime Tools and activate yourself.

The nuance that matters: pre-activated means licensed at the size ordered, not unlimited. Check the tier on a panel before designing an application around it.

The gotcha: two rehosts per month

This one bites during maintenance, not design.

Rehosting moves a Runtime entitlement to another device — a panel dies, you swap in a spare, the entitlement moves across. Fully supported. But Rockwell caps it at two rehosts per calendar month, and a third means contacting software support before that device comes up.

For a one-off failure, fine. But picture a bad month: a panel fails, then another on a different line, then someone repurposes a box for another cell. That's three, and now you're waiting on a support ticket to finish the job. Sequence staged rollouts with that ceiling in mind — and make sure your maintenance team knows, since they're the ones who'll hit it at an inconvenient hour.

Three things that come up in practice

Entitlements are currently perpetual. Subscriptions exist as an option; an expiration date means that's what you have.

Offline activation works properly. Air-gapped devices don't need internet exposure — generate a request file on the device, process it on a connected machine, bring the entitlement file back. Rehosting works the same way.

Unlicensed Runtime stops after about two hours. Fine for a bench test, unusable for production. If you're running Optix in a Docker container and it dies right around the two-hour mark, that's the license, not a crash.

Remote Access licenses separately

Worth knowing because it runs on much of the same hardware: FactoryTalk Remote Access has its own Basic and Pro runtime tiers, entirely separate from Optix tokens. The Embedded Edge Compute module ships with an XS Optix Runtime license and a Remote Access Runtime Pro license — two entitlements, one device.

If remote support is part of how you maintain systems — and for integrators supporting machines at customer sites, it usually is — you can trial it through the "Try it now" request:

https://www.rockwellautomation.com/en-us/products/software/factorytalk/remote-access.html

Practical note: it's a request, not an instant download. Expect up to 48 hours for your trial key. Request it a few days before a demo or proof of concept, not the morning of.

The short version

Size for what the application will become, not just day one — especially concurrent web sessions. Know which deployment targets arrive licensed and at what tier. Keep the two-per-month rehost limit in mind before hardware swaps, and tell whoever handles maintenance. And if Remote Access is in your support model, request the trial key early.