The Complete Guide to Machine Vision Software Licensing, Costs and Hidden Fees

What it really costs to build, deploy, scale and maintain a vision system, for system integrators, machine builders and OEMs.

You can cost the hardware of a vision system to the penny. Every camera, lens, light and cable sits on the bill of materials with a price beside it. Ten cameras means ten lenses and ten lots of lighting. The software that runs on top does not behave like that. For anyone building vision systems for a living it is where the budget quietly goes wrong.

The reason is simple. A licence is not one line on the bill of materials. It splits into how you build, how you deploy and how much you keep paying once the system ships. It changes shape completely depending on whether you are an integrator delivering one system or an OEM shipping a thousand.

This guide follows the software cost across the life of a system, build, deploy, scale and maintain. At each stage it shows what you are really paying for, where the fees hide and how the main platforms differ. We sell the Zebra Aurora and Teledyne software, which makes those our worked examples. MVTec HALCON is the market leader, named throughout for contrast. Open source sits alongside as the route with no licence fee and a cost of its own.

The Two Licences and the Question Underneath

Before the lifecycle, hold three ideas. Almost every commercial platform charges you once to build the application and again to run it. The development licence is the build cost. The runtime licence is the deploy cost. Underneath both sits ownership, whether you buy the software outright and keep it or pay every year and rent it. Those three ideas explain most of what follows.

Stage One, Build

Building the application needs a development licence. It is the toolkit, the full set of tools you write and debug against. It is usually priced per developer seat or per system rather than per deployed machine.

On Zebra Aurora the development licence arrives as a USB dongle, included with the development package, that opens the whole software development kit. The dongles run on the CodeMeter system. One developer building the vision application needs one. Where a team shares the work there are ten, twenty and thirty-user development dongles that run against a licence server, which removes the drawer full of keys at the cost of IT managing the server and developers staying connected to it.

Zebra also offers Aurora Imaging Library Lite, a free SDK with no runtime cost. It is limited to controlling Zebra hardware such as the frame grabbers. If you point it at a non-Zebra GigE Vision or USB3 Vision camera, with no Zebra board or PC in the system, you need a paid runtime licence for the acquisition interface.

Teledyne splits the job. Sapera LT, the acquisition and control SDK, is free with Teledyne cameras and frame grabbers. Sapera Processing, the image processing and AI library that OEMs and integrators actually build in, is the licensed part, with the AI inference tool needing a separate Sapera AI licence. HALCON gives you a development licence to build in its HDevelop environment or in code, valid for the length of a Progress subscription or without limit on a Steady purchase. Open source asks for no licence at all. OpenCV ships under the permissive Apache 2.0 licence. It asks for your engineers' time instead.

The build-stage trap is licensing people who barely touch vision. Picture fifty developers where three work on the machine vision code. You do not want fifty full development dongles. The thing that triggers the need for a development licence is code that runs the image processing. The usual answer is a full development key for the three who build the vision application, plus a cheaper option for the wider team whose code only passes through it.

Stage Two, Deploy

A built application has to run somewhere. Running it is a separate licence. The runtime licence is the deploy cost. On most platforms it is charged per machine. This is the moment a lot of budgets are set wrongly, because the quote to prove a concept on one PC is not the quote to roll the solution across a line.

Aurora licenses the runtime by package. You license only the specific modules your application used, machine vision, code reading, metrology, colour, industrial communication, whichever ones it touches. You do not pay for the rest. You lock the runtime down in one of two ways, a hardware dongle you move between machines, or a software key tied to a hardware fingerprint on the deployment machine. If there is no suitable hardware to fingerprint, you buy an ID dongle to be one. For anyone embedding Aurora in a product, a utility called gencode can hide the whole licensing step from the end customer.

Teledyne turns the runtime into a reason to buy its frame grabbers. Run Sapera Processing on a compatible Teledyne frame grabber and the standard runtime licence is offered at no additional charge, conditions apply, covering the core image processing, area-based pattern matching, blob analysis and lens correction. The advanced tools and the AI inference sit above that and are licensed. Sherlock, the no-code environment for integrators, is licensed per system and runs on any Windows PC or on a Teledyne vision controller.

HALCON keeps the runtime strict. A runtime licence is required on each machine, node-locked to a dongle or a network card through CodeMeter. There is no floating runtime to pass around a network. It is modular in the same spirit as Aurora, letting you license the parts you use. On the commercial side the edition decides the shape, a Progress subscription that stays current or a Steady purchase you own outright, both set out on MVTec's editions and licensing page.

Stage Three, Scale

This is the stage that separates a project from a product. It is where an integrator and an OEM part company. Deliver one system and the runtime is a single line you barely notice. Ship the same design on ten machines and you buy the runtime ten times. Build it into a product you sell by the hundred or the thousand and the per-unit software cost becomes one of the numbers that decides whether the product makes money.

The platforms pull in different directions here. Teledyne makes a strong move for volume, though it is tied to its frame grabbers rather than any hardware. Sapera LT acquisition is free with Teledyne hardware. The standard Sapera Processing runtime is offered at no additional charge when you deploy on a Teledyne frame grabber, conditions apply. An OEM that builds around Teledyne frame grabbers can take the per-unit cost of the standard toolset close to zero. The development SDK and the fuller or AI runtimes are still paid. This is not a blanket free ride. A camera on its own does not carry it.

Aurora approaches volume through its hardware too. You can fingerprint the runtime to Zebra devices and use gencode to hide the licensing from the people who buy your machine, which suits embedding at scale. The runtime is still bought per deployment, which makes volume a conversation about packages and quantities. HALCON holds a per-machine runtime whatever the volume, bought through your partner, with an embedded and Arm porting route and cloud licensing for virtualised deployments. Open source removes the per-unit licence entirely, which is exactly why some high-volume builders carry the engineering and support themselves rather than pay a runtime on every unit.

The lesson for anyone shipping volume is that the headline licence price matters less than two things, the per-unit runtime cost at your numbers and whether standardising on one vendor's hardware or an OEM agreement changes it. That negotiation is where the real volume pricing lives. It is worth having before you commit a product to a platform.

Stage Four, Maintain

The last cost is the one that arrives after the system is running. Support and updates usually come free for the first year and then move to a modest annual fee. On Aurora the first twelve months are included, after which you pay to keep service pack updates, fixes and manufacturer support. You can let it lapse. You keep the software. You just stop getting the improvements. The day you need a fix is the day you wish you had kept it.

Ownership shapes this too. A perpetual licence is locked to the version you bought, which makes new features past the upgrade window a fresh purchase. HALCON makes the cadence an explicit choice, a Progress subscription that always carries the newest release against a Steady purchase that gives a stable version with free upgrades for two years. Over a fleet's life the dongles and fingerprints become their own small job, with failures, spares and remote sites all needing a plan.

The Four Platforms Side by Side

The same four platforms, read across the life of a system.

What It Actually Costs

Most vendors keep pricing behind a quote. Here is a real sense of the numbers, using Aurora as the worked example because we hold its list prices. These are rounded indicative list prices in pounds. A real quote depends on the exact packages and the volume, though the shape is accurate.

On the build side, a single-user development licence is about £3,400, for one dongle that opens the whole toolkit. The debugging dongle for team members who only run and debug code is about £780, roughly a quarter of a full seat. Network development dongles for shared teams start at about £34,000 for ten seats. Maintenance, after the first year that comes included, is about £686 a year per developer.

On the deploy side the runtime is where the range is widest, because you only license the tools your application uses. Three points on the scale show it.

• Lower cost, a single tool. A barcode reading runtime, the identification package, is about £215. A basic machine vision or image analysis runtime is around £170 to £260. The simplest single licences, an interface or a codec, are about £86.
• Mid range, a real application. A label and code verification station, image analysis with code reading, advanced OCR for printed and date-code text and the geometric tools that locate the part, is about £1,900.
• High end, all in. The complete bundle, every tool including deep learning, 3D, metrology, colour and industrial communication, is about £2,850 per machine. Bought as one bundle it costs less than stacking the same tools one by one.

Two small things sit on top. Choosing a USB dongle over a software key adds about £86 to a runtime. All of these are per deployed machine, which is the number that matters once you start shipping.

The other platforms sit differently. Teledyne is the outlier on the standard tools. Sapera LT acquisition is free with Teledyne hardware. The standard Sapera Processing runtime comes at no additional charge when you deploy on a Teledyne frame grabber, conditions apply, which can take the standard toolset to nothing on a frame grabber build. The development SDK, the fuller runtimes and the AI runtime are paid. Sherlock is licensed per system too. MVTec does not publish HALCON prices and quotes by edition, licence type and project through a partner, with the same drivers at work, development against runtime, how many runtimes and deep learning on top. Open source carries no licence cost at all.

The figure that decides a project is the runtime multiplied by how many machines you ship. A £215 barcode runtime across fifty stations is a very different number from a £2,850 all-in runtime across fifty stations. That gap is the whole reason to license only what each machine actually needs.

Paying for Acquisition You Do Not Need

One trap cuts across every stage. Some software keeps you on its licence even when all you want is to get images off the camera. You use the vendor's acquisition for the pixels. Your own or a third party's algorithms do the work. The vendor's runtime still has to be licensed on the machine.

It is avoidable. Image acquisition is covered by an open part of the GenICam standard called GenTL. A GenTL producer, usually free from the camera maker, hands images to any GenTL consumer regardless of the hardware beneath. Teledyne's Sapera LT is free in the same spirit. HALCON, by contrast, needs a licence to run at all, even when it is only grabbing frames. If acquisition is all you need, a standard GenTL producer does it with no processing runtime attached.

This is why the GenTL driver Clearview built for the Zebra Iris GTX smart camera matters. It lets established libraries pull images straight from the camera over the open standard. You keep a free hand over which software does the processing, instead of being tied to one stack just to see a picture.

The Hidden Fees to Watch For

Gathered in one place, these are the costs that turn a cheap-looking licence into an expensive one.

• Paying to build then paying to run. Development and runtime are separate. The proof-of-concept quote is not the deployment quote.
• Runtime that multiplies. One runtime per machine. Ten stations is ten licences, a thousand units is a thousand.
• AI as its own licence. Deep learning and AI inference often sit outside the base, a separate Sapera AI licence on Teledyne, a deep learning entitlement on HALCON.
• The version trap. A perpetual licence is tied to its version. Next year's features are a new purchase or an upgrade window you have to be inside.
• Maintenance lapse. Drop the yearly support and you keep the software but lose the updates, the fixes and the manufacturer support.
• Dongle and fingerprint logistics. Physical keys and hardware fingerprints fail, get lost and sit in awkward places. A fleet needs spares and a plan.
• Hardware and architecture lock. A licence tied to one machine or processor type may need reissuing when you change platform or swap the hardware it is bound to.

Where We Stand

We should be straight about our position. We sell and license two families. The Zebra Aurora software, which is the Aurora Imaging Library and Aurora Design Assistant. The Teledyne software, which is Sapera Processing and Sherlock. MVTec HALCON is the market leader and we have named it throughout, because an engineer choosing a platform is better served by a fair comparison than by silence. Open source we will point to when a team can genuinely carry it.

What we care about is matching the licensing model to how you build and how you ship. An integrator delivering bespoke systems and an OEM shipping a product in volume should not be on the same model. Getting that right is worth more than shaving a few percent off a headline price.

If you are building or shipping vision systems, talk to us about software options before you commit to a platform. Our engineering team can walk through what each one will really cost across the life of your system, not just on the first quote. Get in touch, info@clearview-imaging.com or +44 (0)1844 217270.