FireSight

Partners · machine builders, integrators and resellers

Ship every machine with secure remote support built in.

Machine builders support lines in plants they don't control, and system integrators connect plants they don't own. FireSight OT gives both a way in that the plant's IT team will actually approve: outbound only, per machine, with working hours and a full audit trail.

Become a partner How FireSight OT works
A machine builder's Hub serving its installed base, wide viewThe machine builder's service engineers sign in to the builder's own Cloud Hub. Each customer plant is a company on that Hub. Every machine shipped has a Cloud Connector with its own device license, dialling out to the Hub. The plant's own staff get accounts for their own machines only. YOUR SERVICE TEAM YOUR CLOUD HUB MACHINES YOU'VE SHIPPED Service engineersvendor accounts, two-factor Commissioning teamuntil the end date you set Plant stafftheir own machines only Cloud Hub remote.your-company.example One company per customer Device license per machine Identical lines, no renumbering Remote checks and updates Audit log the plant can see outbound TLS Filler, Acme Foods (Turin)CC-5 · device license · 192.168.1.0/24 Filler, Acme Foods (Bari)CC-4 · device license · 192.168.1.0/24 Wrapper, Nordic PackagingCC-4 · device license · 192.168.1.0/24 Palletiser, Beta DairyCC-3 · device license · 192.168.1.0/24 A machine builder's Hub serving its installed baseService engineers, the commissioning team and plant staff sign in to the builder's Cloud Hub. Each machine shipped has a Cloud Connector with its own device license that dials out to the Hub, even when every line uses 192.168.1.0/24. Your service teamvendor accounts, hours, end dates Your Cloud Hubremote.your-company.example One company per customer Device license per machine Identical lines, no renumbering Remote checks and updates Audit log the plant can see outbound from every machine Filler, Acme Foods (Turin)CC-5 · device license · 192.168.1.0/24 Filler, Acme Foods (Bari)CC-4 · device license · 192.168.1.0/24 Wrapper, Nordic PackagingCC-4 · device license · 192.168.1.0/24 Palletiser, Beta DairyCC-3 · device license · 192.168.1.0/24

Example: a machine builder runs one Hub for every line it has shipped. Each customer is a company of its own on the Hub, so plants never see each other's machines.

Three ways to work with us

Pick the model that fits how you already sell

Machine builders (OEM)

Remote support in every machine

Fit a Cloud Connector in each machine you ship, with its own device license bound to its serial. Run one Hub for your installed base, or connect each machine to the customer's own Hub. Either way, the license travels with the machine.

System integrators

One way into every plant you look after

Run a Hub for the plants you maintain, with each customer as its own company, or set one up in the customer's name. Your engineers get vendor accounts with the hours and end dates each customer agrees to.

Resellers and distributors

License it to your own customers

The FireSight portal gives resellers their own area: register customers' Hubs and Cloud Connectors, and issue licenses from your allowance, which is kept separate for FireSight firewalls and FireSight OT connectors.

Why plants say yes

Built to pass the plant's IT review

The hardest part of remote support is often getting it approved. FireSight OT answers the questions IT and security teams ask before they open anything.

  • No inbound firewall rules. Cloud Connectors only dial out, on 443 or through the site's proxy.
  • Only the machines you're granted, never the plant network. The site's own allowlist on the device caps it.
  • Vendor accounts with two-factor sign-in, working hours and an end date. Sessions close when time is up.
  • A complete audit log of who reached which machine and for how long, with the vendor marked on every entry.
  • Identical lines just work. Every customer can keep 192.168.1.0/24 on the plant floor.
  • Help with the paperwork. Pages on NIS2 and the Machinery Regulation to share with your customers.

Getting started

From first call to first machine online

  1. Talk to us

    Tell us what you build or maintain, how many machines or sites, and how your engineers get in today.

  2. Try it on a test line

    We help you set up a Hub and a Cloud Connector on a machine in your own workshop first, before it goes near a customer.

  3. Agree the model

    Device licenses per machine, a Hub license, or a reseller allowance in the portal, with partner pricing.

  4. Ship it

    Flash one SD card image for every machine. On site, a one-time code ties each device to the right customer.

Let's put remote support in your next machine

Partner pricing, help setting up a test machine in your workshop, and help with your first customer. Tell us a little about what you build, and we'll get back to you.

Become a partner Watch the OT how-to videos