We do not host your SCADA

And we do not want to. If you run VTScada, it stays yours: your host, your tag database, your control, your relationship with the customer. Field Warden feeds it.

This page is written for the integrator and the automation lead, because you are the people who will be asked whether this is a threat. It is not, and the specific reason is that we do not do the part you do. There is no Field Warden control system, no historian to migrate to, and no seat licence that displaces yours.

How the data reaches you

Every value a Sphynx reads is published over MQTT on its own topic, one topic per channel, timestamped at the device. That is the whole interface and it is deliberately boring: a host subscribes to exactly the topics it wants and nothing has to be scraped, polled or reverse engineered.

The topic taxonomy is documented rather than discovered. It is stable enough to build tags against, and a change to it is a version change rather than a surprise on a Tuesday.

Alongside MQTT there is a REST API for values and history, and bulk CSV for a backfill or an audit. Same data, three shapes, whichever suits what you are building.

What we are building for VTScada specifically

Prebuilt tag types so a Sphynx channel becomes a tag by configuration rather than by hand, and importable widgets so a page showing a well does not have to be drawn from scratch. Both are in progress rather than shipping, and this page will say so until they are.

Until then the MQTT topics are stable and documented, which is enough to build against today. If you are integrating now and want the taxonomy before it is published, ask and you will get it.

Where this is genuinely useful to you

The sites your customer never approved a full deployment for. Every producer has them: a handful of wells too remote or too marginal to justify a host connection, running unmonitored because the quote was never going to be signed. Those are the ones a Sphynx covers, and it puts them in the same asset tree as the ones you already look after.

That tends to grow the monitored footprint rather than divide it, and the part that needs control is still the part that needs you.