Short answer: Robot software is priced in four overlapping ways: a perpetual licence bought once per robot or per seat, a subscription charged per robot per period, feature modules switched on for an additional fee, and a support-and-updates contract renewed annually. Most real installations combine at least two of them. The hardware price in the quotation is a single line; the software terms decide what the system costs to run, extend and eventually retire.
Perpetual licences: the traditional model
The classic arrangement bundles the robot's base software with the arm and charges separately for engineering software — offline programming, simulation — per seat, as a permanent licence. Its virtues are predictability and ownership: the cell keeps running if the vendor relationship ends. Its trap is version lock: the licence entitles you to the version bought, not its successors, and upgrades arrive later as a paid project. When comparing perpetual offers, ask which version, which options are included, and what an upgrade to the current version costs in year three — the answer is rarely in the first quotation.
Subscriptions: per robot, per period
Newer platforms — especially fleet software for mobile robots, cloud monitoring, and AI features that improve continuously — are priced as subscriptions, typically per robot per month or year. The model matches how the vendor develops the product and gives buyers a running cost instead of a capital one. Its risks are structural: the software may degrade or stop if the subscription lapses, fleet growth multiplies the line item automatically, and renewal pricing is the vendor's future decision. Buyers should ask, before signing, what exactly happens at lapse — full stop, reduced mode, or continued basic operation — and get the answer in the contract, not the demo.
Feature modules: the option list
Across both models sits the option list: vision guidance, force control, conveyor tracking, palletising patterns, specific communication protocols, safety-rated functions. Each is a module with its own price, and the same robot can double in software cost between a bare configuration and a fully optioned one. This is the section of the quotation most worth line-by-line reading, because options bought 'just in case' are a pure donation, while options discovered missing at commissioning cost project time instead. Our guide to reading a robot price quotation shows where these lines sit in the full hardware-software-installation picture.
Support and update contracts
The fourth layer is the annual contract: helpdesk access, software updates, security patches, sometimes remote diagnostics. It is easy to treat as overhead and expensive to discover otherwise — an unpatched controller on a factory network is a security finding waiting for an auditor, and a version frozen for six years eventually fails an integration it would have passed. Evaluate support contracts like insurance: what response times, in which time zones, through which channel, and whether updates can be applied without a vendor visit. The directory's software section lists vendors whose entire business is this layer of the stack.
The risks nobody prices: end of service and data
Two questions belong in every software negotiation and appear in almost none. First, end of service: when the vendor retires the platform or version, how much notice, and does the installed software keep running? Second, your data: programs, configurations, production logs and learned models — in what formats can they be exported, and does export survive the end of the contract? A cell whose programs cannot be exported is a hostage asset. Both answers are cheapest to obtain before the purchase order, when the vendor still wants the sale.
Seats, sites and the second cell
Two pricing details reward attention because they only bite later. Engineering software is often licensed per seat, and the seat count that suffices for the first cell quietly becomes the constraint when a second cell, a second shift or an integrator's engineer all need the tools at once. Fleet and platform software is sometimes licensed per site rather than per robot, which reverses the scaling arithmetic of the per-robot model — better for large fleets, worse for pilots. Neither detail is visible in the headline licence price; both are one question each, asked before the order, and both belong in the same contract schedule as the lapse and export terms.
Negotiation checklist
Ask for the software bill of materials as explicitly as the hardware one: every module, its model (perpetual or subscription), and its renewal terms. Cap renewal increases where you can. Tie subscription start dates to acceptance, not delivery. Confirm lapse behaviour, export formats and end-of-service notice periods in writing. And record the answers in the machine file alongside the hardware documents — as the GlobleMatch pricing page illustrates for services generally, the transparency you demand at purchase is the transparency you get.
Frequently asked questions
What are the main ways robot software is priced?
Four models overlap: perpetual licences bought once, subscriptions charged per robot per period, feature modules switched on for an extra fee, and annual support-and-update contracts. Most installations combine at least two of the four.
What happens if a robot software subscription lapses?
It depends on the vendor — anything from full stop to a reduced basic mode. Because the range is so wide, the lapse behaviour should be asked explicitly and written into the contract before signing, not discovered afterwards.
Which software costs surprise buyers most often?
Feature modules: vision, force control, tracking and protocol options can double a robot's software cost. Options bought just in case are wasted money, and options discovered missing at commissioning cost project time instead.
What should I negotiate about my robot's data?
Export rights: your programs, configurations and production logs should be exportable in usable formats, and the export should survive the end of the contract. Also ask for the end-of-service notice period for the platform you are buying.