OEM and Brand Label SCADA and HMI Software
Embed the platform in your machine, ship it under your own brand, and support one product line instead of five.
Apply to the OEM program See the licensing at a glanceFrameworX is an industrial platform that machine builders embed in their equipment and ship under their own brand. It unifies SCADA, HMI, IIoT and Historian in one product, connects directly to controllers through more than 100 native drivers included in the licence, and runs on Windows and Linux from an embedded controller up to a plant server. The interface is available in 12 languages, licences are perpetual, and local tags are unlimited in every edition. One project built once deploys to a panel at the machine, to a browser for remote service, and to a phone in the field.
Who builds the platform you would be embedding?
An OEM licence is a fifteen year decision. The software goes into a machine you will still be supporting long after the sales conversation, so the question that comes before any feature comparison is who is going to be standing behind it.
The team that builds FrameworX has been shipping industrial software since the DOS era. In 1996 it co-founded InduSoft (now AVEVA Edge) and built the HMI engine behind it, and it has shipped every generation of this platform since. FrameworX is the current one, built from scratch on managed .NET rather than carried forward from the last.
That history matters here more than on any other page on this site, because embedding a platform means inheriting somebody else's roadmap. The full lineage is written out here.
What is an OEM licence for SCADA and HMI software?
An OEM licence lets a machine builder embed industrial software inside a product and sell that product to an end customer, rather than asking the customer to buy the software separately and install it themselves. The end customer buys a machine. The software is part of it.
That changes three things compared with a normal seat licence. The commercial terms have to work at the volume you ship rather than per engineer. The branding has to be yours, because the customer is buying your machine and not somebody else's software. And the support relationship stays with you, because the customer will call you when the machine stops.
Brand label is the same arrangement carried further: the interface, the documentation and the deployment all carry your identity, and the platform underneath is not the thing the customer is choosing.
Can I ship FrameworX under my own brand?
Yes. Brand label deployment covers the operator interface, the documentation and the deployed application, so the software your customer runs presents as your product.
Build once, deploy anywhere
One project runs on a local operator panel at the machine, in a browser through the WebAssembly client for remote service, and on a tablet or phone. There is no separate mobile project, no plugin, and no second application to keep in step with the first. A service engineer can diagnose equipment without installing client software on anything.
One template across a product line
Build one HMI template and deploy it across many machines, then customise it per customer without rebuilding it. Projects are stored in one secure file with built-in versioning, so the same application can be reused across machine models and revisions and kept under change control.
An interface in 12 languages
The interface ships in 12 languages. For a machine builder selling into more than one market this is the difference between one product and one product per region, and it is included rather than sold as a localisation package.
Your machine joins the customer's plant, not just their floor
Machines publish through MQTT with Sparkplug B and participate in a Unified Namespace as an edge node, so a machine you ship becomes part of your customer's plant wide data model on the day it is commissioned, with no separate gateway to buy. UNS by Design.
What should I embed in my machine, an HMI or a full platform?
It depends on what the machine has to do once it is installed, and the three editions map onto that question directly. Every edition includes every module.
| Edition | Built for | Typical OEM use |
|---|---|---|
| MachineHMI | Machine level applications, five concurrent clients, unlimited tags | The operator interface on the machine, plus remote service access through a browser |
| EdgeConnect | Edge collection and protocol conversion | An instrument or skid that has to speak to a plant system it was not designed for |
| Enterprise | Plant wide deployment, unlimited clients | A line or a fleet of machines supervised as one system, with a historian behind it |
All three are built on the same managed .NET foundation and share a single designer environment, so a project does not get rewritten when a machine grows into a line. Moving between editions costs the difference in price rather than starting again.
Can my customers configure the machine I ship them using AI?
Yes, and it is part of the platform rather than a separate product. FrameworX is AI-Native by architecture. It exposes MCP servers for the Designer, for the Console and for the Runtime, plus an in-process AI agent spine inside the runtime, all released and supported today.
For a machine builder that means two distinct things, and they are worth separating.
Your engineers build faster
An AI client works on the real object model of the solution: tags, devices, alarms, historian, displays and scripts. It configures against the actual project rather than generating text about it, and your engineer reviews each step as it lands. Objects your engineer created stay read only to the AI client until they are unlocked, so the collaboration boundary is enforced by the platform rather than by discipline.
Your customer gets a machine that can explain itself
Through the runtime surface, an AI client reads live tag values, the Unified Namespace, active alarms, alarm history and tag history. An operator can ask the machine a question from a panel on the screen. A script can call for a shift summary or a probable cause hypothesis on an alarm. That capability ships in your machine without you building it.
The model is the customer's, and so is the data
FrameworX ships no language model and no model weights. It connects to an endpoint the customer chooses and hosts, which can be an OpenAI compatible endpoint such as an Ollama server on their own network. When the customer hosts the model, inference happens on their hardware and plant data stays inside their firewall. For machines going into regulated, air gapped or data sovereign sites, that is what makes the capability usable at all.
The runtime AI reads, and does not write
By default the runtime AI reads. It does not change setpoints and it does not acknowledge alarms. Write actions exist only where a solution author deliberately exposes them as Custom Tools, per solution, and every tool group has an independent switch. Deterministic control stays with the PLC logic, the loops and the interlocks. This is a line drawn in the architecture rather than in a policy document, which is the answer your customer's safety review is going to ask for.
Why this is worth reading twice if you build machines
The AI capability in your product is not something you have to build, budget for or maintain. It arrives with the platform, it runs on infrastructure your customer already controls, and it carries no per seat AI subscription. The full architecture is written out here.
Will it talk to the controllers I already use?
More than 100 native protocol drivers ship in the base install, including Rockwell, Siemens, Modbus, CODESYS, Beckhoff, Omron, OPC UA client and server, MQTT with Sparkplug B, SNMP and BACnet. They are in the licence rather than sold as separate connectivity modules, so the driver a customer needs is not a line item on a quote.
A driver toolkit is included for building your own. If your machine uses a proprietary protocol, or a controller nobody else supports, you can write the driver yourself against a documented API, or the Tatsoft team can build it. For an OEM with in house hardware this usually matters more than the driver count does.
Beyond the controllers, the platform connects to SQL databases, REST APIs, and historians including AVEVA PI and Canary, and to cloud storage such as Azure and Snowflake. Scripting is C#, VB.NET and Python 3, running natively in the runtime.
How does OEM licensing work?
The platform terms below apply to every licence. The OEM specific commercial terms are set per programme, because volume, territory and support model change what makes sense.
| Term | How it works |
|---|---|
| Licence type | Perpetual |
| Local tags | Unlimited in every edition |
| What scales the cost | External I/O points, meaning the physical signals coming from the field, rather than the number of tag names in the project |
| Modules | Every module, feature and 100+ connectors included in each licence |
| Annual support | 20 percent per year, or 16 percent on a three year term. Strongly recommended and not mandatory: the perpetual licence keeps running without it |
| Redundancy | Plus 50 percent, licensed as an option |
| Changing edition | Costs the difference in price |
| OEM commercial models | Subscription, per device, or upfront. Which one fits is set per programme, because volume, territory and support model change the answer |
| Development licences | Five NFR licences, extended for as long as the partnership is active |
| Source code | Not licensed. A source-code escrow agreement is available as an option, at a cost arranged per agreement. See below |
| Interface languages | 12 |
| Operating systems | Windows and Linux, from an embedded controller to a plant server |
| AI subscription | None. There is no per seat AI charge in the platform |
What happens to my product if Tatsoft is not here in ten years?
It is the fair question, and it is the one that decides OEM deals more often than any feature does. You are putting somebody else's platform inside a machine you will support for fifteen years. There are three answers and they work in order.
First, the licence is perpetual and it does not depend on us. An OEM licence is bought once and keeps running. The annual maintenance agreement is strongly recommended, because it is how you receive updates, new drivers and support, but it is not mandatory. Equipment you have already shipped keeps running on the licence you hold whatever happens to the company behind it. That is a property of the licence rather than a promise about the future.
Second, the record. This team has been building industrial software since 1996, when it created UniSoft, which became InduSoft (now AVEVA Edge). Systems built on that lineage three decades ago are still running in production today, and current product lines at major automation companies are still built on the core this team developed. Closer to home for a machine builder: German OEMs are still deploying a version of this platform that is ten years old, because the machine it runs on is still being sold and still being supported. Continuity here is not a policy statement, it is what has already happened over thirty years. The full lineage is written out here.
Third, escrow, for partners who want source access on top of the first two. Tatsoft does not license source code, and no OEM agreement offers it. What is available instead is a source-code escrow agreement, a standard instrument in the software industry: the source is deposited with an independent agent, and if the company is no longer active the partner gains access in order to make their own modifications and keep their equipment maintained. There is a cost attached to the escrow contract and it is arranged per agreement rather than included by default. It is the additional protection that some large brand-label partners ask for, and it is available if you want it. The source remains Tatsoft intellectual property before release and after it.
What do OEMs actually build with it?
Two partners have made the relationship public, so their products can be named and checked. Six more categories are running in the field under agreements that stay confidential.
SPIN builds Action.NET, a brand label SCADA product for the energy market
Action.NET is built on FrameworX and sold under SPIN's own brand, with more than 400 SCADA systems deployed across power generation, transmission and distribution, including industrial substations and wind power. SPIN brings more than twenty years in the energy market, and worked with the Tatsoft team to build the DNP 3.0 and IEC 60870-5 drivers the product needed.
This is the full brand label pattern in production: the partner's product, the partner's customers, the partner's support relationship, with FrameworX inside. Read the Action.NET solution.
Wunderlich-Malec Engineering builds regulatory and environmental reporting products
The Environmental Information Systems group at Wunderlich-Malec builds reporting products on FrameworX for facilities operating under Title V permits, CFR 40 Part 75 and Part 60, and California RECLAIM. Compliance reporting is where the data model, the historian and the audit trail carry the product, which is why the platform underneath it has to be the same one running the plant. Read the Environmental Information Systems solution.
Six more, under confidential agreements. Most OEM agreements stay private, because the point of a brand label product is that it presents as the partner's. These are applications running in the field today, described by what they do.
Flow meter manufacturer
Advanced metering solution running on an embedded Linux controller.
Water analysis instruments
Protocol converter with real time calculations, on a small form factor industrial PC.
Industrial computer manufacturer
Brand label HMI and Andon software shipped as part of the hardware product.
Packaging machinery
SCADA, HMI and OEE for a packaging machine builder moving to a connected IIoT application.
Process analysis skids
HMI and SCADA for a supplier of water treatment and analysis process skids.
Generator manufacturer
Embedded data collection and analytics on wind power generation equipment.
The equipment categories where FrameworX is most often embedded are packaging, bottling and labelling, industrial robotics and motion control, printing and converting, semiconductor and electronics assembly, food and beverage production equipment, and mobile machinery in agriculture, construction and logistics.
What comes with an OEM partnership?
Engineering support during the build
Direct access to the engineering team while the first machine is being built, which is when the decisions that are expensive to reverse get made.
A driver built for your hardware
The driver toolkit is included so you can write your own. Where a protocol is proprietary or unusual, the Tatsoft team can build the driver instead.
Co-development and joint go to market
Optional, and shaped per partner. Some OEMs want a technical relationship only. Others want the platform vendor in front of their customer.
Five development licences, and an engineer to start with
An OEM partnership includes five not-for-resale development licences, extended for as long as the partnership is active. It also includes a one to one session with our engineering team to design the new project, at the point where the design decisions are cheapest to get right.
Training that does not depend on us
The AI Tutor delivers a structured curriculum of 45 lessons across three tiers inside a live Designer session, and every lesson builds something in a real solution that runs. Any customer with AI Designer has it, so your engineers can get productive without booking our calendar.
How do I apply to the OEM program?
Through the application form. It asks for a work email, your name, phone number, country and company, and takes about a minute. A work email is required and free mail providers are not accepted, because the first thing we look at is which company is asking.
An application is not a commitment on either side. OEM terms are set per programme, so the first conversation is about what you are building, the volume you expect and the markets you sell into, and that conversation shapes the commercial terms rather than the other way round.
The OEM and brand label track sits inside Vanguard Alliance, the Tatsoft partner programme.
You will get a first reply within one business day. Applications reach the sales team rather than one person, so an answer does not wait on somebody's calendar.
If you would rather talk before filling anything in, that works too.
Common questions
What is an OEM licence for SCADA and HMI software?
An OEM licence lets a machine builder embed industrial software inside a product and sell that product to an end customer, instead of the customer buying and installing the software separately. It differs from a normal seat licence in three ways: the commercial terms work at the volume you ship rather than per engineer, the branding is yours because the customer is buying your machine, and the support relationship stays with you because the customer calls you when the machine stops. Brand label deployment carries that further, so the interface, the documentation and the deployed application all present as your product.
Can I white label an HMI and ship it under my own brand?
Yes. Brand label deployment covers the operator interface, the documentation and the deployed application. One project built once deploys to a local operator panel, to a browser through the WebAssembly client for remote service, and to a tablet or phone, with no separate mobile project and no plugin. Build one template and deploy it across many machines, then customise per customer without rebuilding, with projects stored in one secure file with built in versioning so revisions stay under change control.
Are OEM agreements public or confidential?
That is your decision. Most Tatsoft OEM agreements are confidential, because the point of a brand-label product is that it presents as yours. Some partners choose to make the relationship public instead, because saying that FrameworX is inside their system helps them sell it. Wunderlich-Malec and SPIN are both public examples. SPIN builds Action.NET, a SCADA product for the energy market built on FrameworX and sold under its own brand, with more than 400 systems deployed in generation, transmission and distribution. Wunderlich-Malec Engineering builds regulatory and environmental reporting products on the platform through its Environmental Information Systems group. Both are described on the Tatsoft partner solutions page. Either way, public or confidential is written into the agreement rather than assumed.
Should I embed an HMI or a full SCADA platform in my machine?
It depends on what the machine has to do once installed. MachineHMI is sized for machine level applications with five concurrent clients and unlimited tags, and covers the operator interface plus remote service access. EdgeConnect suits an instrument or skid that has to speak to a plant system it was not designed for. Enterprise covers plant wide deployment with unlimited clients, for a line or a fleet supervised as one system. All three share the same managed .NET foundation and a single designer environment, so a project is not rewritten when a machine grows into a line, and moving between editions costs the difference in price.
What if my machine uses a protocol you do not support?
More than 100 native drivers ship in the base install and are included in the licence rather than sold as separate connectivity modules. For anything not covered, a driver toolkit is included so you can build your own against a documented API, or the Tatsoft team can build the driver. For an OEM with in house hardware or a proprietary bus, that path usually matters more than the driver count.
Can my customers use AI to configure or query the machine I ship?
Yes, and it is part of the platform. FrameworX exposes MCP servers for the Designer, the Console and the Runtime, plus an in-process AI agent spine inside the runtime, all released and supported today. Your engineers can build against the real object model with an AI client reviewing each change with them. Your customer's operators can ask the running machine about live values, the namespace, active alarms and history from a panel on screen. That capability ships in your machine without you building it, and there is no per seat AI subscription.
Does using the AI features send my customer's plant data to a cloud?
Not unless the customer chooses that. FrameworX ships no language model and no model weights. It connects to an endpoint the customer selects and hosts, which can be an OpenAI compatible endpoint such as an Ollama server on their own network. When the customer hosts the model, inference runs on their hardware and plant data stays inside their firewall, which is what makes the capability usable for machines going into regulated, air gapped or data sovereign sites. The runtime AI also reads rather than writes by default: it does not change setpoints and does not acknowledge alarms, and write actions exist only where a solution author deliberately exposes them per solution.
How is FrameworX licensed, and what drives the cost?
Licences are perpetual. Local tags are unlimited in every edition, so the scaling cost is external I/O points, meaning the physical signals coming from the field, rather than the number of tag names in a project. Every module, feature and 100+ connectors are included in each licence. Annual support is 20 percent per year, or 16 percent on a three year term, redundancy is plus 50 percent, and moving between editions costs the difference in price. OEM commercial terms are set per programme, because volume, territory and support model change what makes sense.
Can I ship the same machine into markets that need different languages?
Yes. The interface is available in 12 languages, included rather than sold as a localisation package. For a machine builder selling into more than one market that is the difference between maintaining one product and maintaining one product per region. Machines also publish through MQTT with Sparkplug B and participate in a Unified Namespace as an edge node, so the machine joins the customer's plant wide data model on the day it is commissioned without a separate gateway.
What happens to my machines if Tatsoft stops trading?
The OEM licence is perpetual and the annual maintenance agreement is not mandatory, so equipment you have already shipped keeps running on the licence you hold. Maintenance is strongly recommended because it carries updates, new drivers and support, but it is not a condition of continued use. Beyond the licence itself there is a track record: this team has been building industrial software since 1996, when it created UniSoft, which became InduSoft (now AVEVA Edge), and systems built on that lineage three decades ago are still running in production today, with current product lines at major automation companies still built on the core this team developed. Partners who want a further guarantee can add a source-code escrow agreement, at a cost arranged per agreement, which gives access to the source for their own maintenance if the company is no longer active.
Do you license source code to OEM partners?
For most partners the first protection is simpler than escrow: the OEM licence is perpetual and the annual maintenance agreement, while strongly recommended, is not mandatory, so equipment you have already shipped keeps running on the licence you hold. On top of that, Tatsoft does not license source code and no OEM agreement offers it. What is available instead is a source-code escrow agreement, a standard instrument in the software industry: the source is deposited with an independent agent, and if the company is no longer active the partner gains access in order to make their own modifications and keep their equipment maintained. There is a cost attached to the escrow contract and it is arranged per agreement rather than included by default. It is the additional protection that some large brand-label partners ask for. The source remains Tatsoft intellectual property before release and after it.
How do I apply to become an OEM partner?
Through the application form, which asks for a work email, your name, phone number, country and company. A work email is required and free mail providers are not accepted. You will get a first reply within one business day, and applications reach the sales team rather than one person. An application is not a commitment on either side: OEM terms are set per programme, so the first conversation is about what you are building, the volume you expect and the markets you sell into, and that conversation shapes the commercial terms rather than the other way round. The OEM and brand label track sits inside Vanguard Alliance, the Tatsoft partner programme.