Universal drilling data hub
Any format in.
Any format out.
Any format out.
WITStream Connect® is a drilling data hub you install on your own server. It collects live data from any rig source, WITSML, WITS0, ETP, OPC-UA, Modbus TCP or LAS, shows every rig on a live dashboard with drilling analytics built in, and passes the data on to your other systems in any of those formats. Setting it up for a new rig or contractor is done on a settings screen, without a developer.
The problem
Drilling data speaks six dialects, and nobody agrees on the words
Every rig, every contractor, every service company can speak a different protocol, and often a different naming convention for the exact same measurement. A multi-year campaign can span several contractors on one well. Most platforms in this space pick one format, convert it one way, and charge a services engagement every time that changes.
WITStream Connect® fixes this by normalising every protocol into one canonical model first: every source writes into the same shape, every sink reads from it, so a new rig or contractor's own numbering is a settings screen your own staff can change.
That's how WITStream Connect® removes that cost entirely.
Six protocols, one industry, no shared language
WITSML
WITS0
ETP
OPC-UA
Modbus TCP
LAS
3+
contractors' worth of mnemonic conventions, often on one well
Calculate your own number
What is reconfiguring for a new rig or contractor actually costing you?
Enter your own figures to see what reconfiguration delays cost your rig each year.
Estimated annual cost of that delay, at your own numbers
$0
Day rate × days lost × reconfigurations per year. WITStream Connect® reconfigures through a settings screen, typically the same day, so most of this is recoverable.
By the numbers
No implementation cost: self-hosted, no professional services
500+ rigs, one deployment, no starvation
WITSML validated against PDS WITSMLstudio
Reconfigured for a new rig with zero code changes
An AI layer already live, seven capabilities, no extra cost
Built for the rig floor and the RTOC
Every reading, at a glance
WOB, RPM, torque, standpipe pressure, hookload, flow rate, mud weight, gas, block position, ROP against depth: the same instrument-panel conventions a driller already trusts.
Why WITStream Connect®
The industry competes on protocol breadth. We compete on how fast you're actually running.
Every serious platform in this space can talk WITSML. The cost has always been what happens next: a different contractor, a different channel numbering, a different unit set, and whether that takes a settings screen or a change order.
No developer, no code
A field engineer reconfigures it
A new contractor's channel numbering, a different unit set: it's a couple of minutes on a tablet at the rig.
WITStream Connect®
Typical enterprise platform
Reconfiguring for a new rig or contractor
A settings screen, no code
Usually a services engagement
Where your data lives
Your own infrastructure, self-hosted
Usually the vendor's cloud
Operating system
Windows Server as a native service, or Linux and macOS with Docker
Often locked to one platform or the vendor's own infrastructure
Getting started
One command, then a settings screen
Usually a sales cycle and an integration project
Implementation cost
None, no professional services, no onboarding fee
Often a paid integration project
Format symmetry
Any format in, any format out, both directions
Often one-way conversion
Mnemonic mapping across vendors
Solved once, centrally, across every protocol
Handled per integration
Scale proven
500 simultaneous rigs, no cross-contamination, no hard-coded ceiling above that
Varies
AI and predictive monitoring
Built in, live, seven capabilities, no extra cost
Usually a separate analytics product
"Typical enterprise platform" describes general patterns common across this category, not any specific competitor's product or claims.
By the numbers
Six protocols, five hundred rigs, zero code changes
6
Protocols, both directions
WITSML, WITS0, ETP, OPC-UA, Modbus, LAS: every one both a source and a sink.
500
Simultaneous rigs, one deployment
No starvation, no cross-contamination between connections, at fleet scale.
0
Code changes to switch rig setups
A completely different WITS0 channel scheme and unit set, reconfigured through the UI alone.
7
intelligence capabilities, live
0
extra cost, no add-on tier
0
seconds of delay, computed live
1
canonical stream feeds all of it
What it does for you
Seven capabilities, live in the product today
Mechanical Specific Energy monitoring
Catches a dulling bit or a harder formation before a driller would ever see it by eye, computed live from parameters already streaming.
Sensor health & data quality
A dead, stuck, or spiking channel is caught the instant it happens, before a bad reading ever misleads anyone.
Non-productive time detection
Every stalled minute caught and timed automatically, work normally tracked by hand for cost and AFE reporting, done for free.
Rig-state activity classification
Drilling, circulating, tripping in or out, static: classified continuously from readings already streaming, no extra sensor needed.
Cross-rig benchmarking
A live, sortable comparison across an entire fleet, so an ops manager watching several pads always knows which one to look at first.
Automated shift reporting
A complete, print-ready shift report, footage, downtime, every parameter's average and range, generated the moment it's needed.
Automated survey QC
Your directional driller enters the planned well path once, a short table of measured depth, inclination, and azimuth stations, in the configuration screen. Every survey station is then checked against that plan the instant it arrives, using the same minimum-curvature maths a directional driller already trusts, and flagged the moment it drifts beyond the tolerance you set.
And it's all one canonical stream
None of this needed a separate system, a data export, or a consultant to configure. It runs on the exact same normalised shape every one of six protocols already feeds into, live, the moment WITStream Connect® is deployed.
Available as a paid add-on
A natural-language query interface, a Level-1 support assistant, and offset-well correlation, built for you
Ask the data a question directly, no report builder, no SQL, plus a support assistant and offset-well comparison against historical logs. Both are scoped and ready, built to order once you're on board and priced separately.
See the AI layer running live
Pricing
Priced by the number of rigs connected
Reconfiguring for a new rig, a new contractor, a new unit set costs nothing extra: it's done on a settings screen. One deployment, self-hosted on your own infrastructure.
Starter
First deployment, one field
Up to 3 rigs
✓ Every protocol: WITSML, WITS0, ETP, OPC-UA, Modbus, LAS
✓ Unlimited reconfiguration, no extra cost
✓ Self-hosted, your infrastructure
✓ Shared API key access
Get started
Growth
A handful of active pads
Up to 10 rigs
✓ Everything in Starter
✓ Single sign-on (your own identity provider)
✓ Role-based access control
Get started
Fleet
Most common
Up to 30 rigs
✓ Everything in Growth
✓ Proven past 500 simultaneous rigs, no cross-contamination
✓ Priority support
Get started
Enterprise
Multi-region operators
Unlimited rigs
✓ Everything in Fleet
✓ Dedicated onboarding
✓ Custom contract terms
✓ Capacity sized to your deployment, no software cap
Talk to us
Add-ons, available on any tier
A natural-language query interface, a support assistant, and offset-well correlation
Built for you once you're on board, priced separately from your tier. .
Why the price doesn't move when your setup does
Every plan reconfigures the same way, through the settings screen
A different rig contractor's channel numbering, a different unit set, a new mnemonic convention: none of it needs a developer or a change order, at any tier, even a full protocol switch, zero code changes.
15+
years in production
Global
oil and gas drilling companies running it
0
minutes of downtime
0
moments of lost telemetry
Then and now
Fifteen years of field experience, carried forward
That history is what WITStream Connect® is built on. Three things limited it, and WITStream Connect® exists to fix exactly those three things.
Origin
XStream Connect®
✕Compiled directly into a customer's own application, any change needed a developer to rebuild and redeploy it
✕Windows only
✕One direction only: WITSML flowed in and was consumed, nothing was ever normalised and sent back out
→
Evolution
WITStream Connect®
✓Standalone and self-hosted, reconfigured live through its own settings screen, no developer, no rebuild
✓One container, runs on Linux, Windows, or macOS
✓Bidirectional: any format in, any format out, across every protocol a drilling operation uses
How we work
The same three principles run through everything we've built
Self-hosted, always
Runs on your own infrastructure. Drilling data stays on your infrastructure; only licensing metadata leaves a deployment.
Bidirectional
Every one of six protocols proven as both source and sink. Most platforms in this space pick one format and convert one way.
Proven at scale
500 simultaneous rigs, no starvation, no cross-contamination, no hard-coded ceiling anywhere in the code.
What bidirectional actually buys you
A contractor's own equipment streams one protocol; your historian, SCADA, or engineering software expects another, and that pairing changes every time a contractor or a piece of equipment changes. One deployment can take in a WITSML feed and re-emit it as OPC-UA for your historian, or take in WITS0 from a legacy rig recorder and re-emit ETP for a modern engineering tool, live, with nothing custom built for that one pairing. Your own downstream systems never have to match whatever a contractor's equipment happens to speak.
Want to see it running?
Request a demo
Live, guided, on your screen
We walk you through it ourselves, screen-shared, on a call. Tell us a little about you and we'll be in touch to schedule it.
Contact sales
Talk to us about your deployment
Pricing, fleet sizing, anything short of a full demo. Tell us what you need and someone from our team gets back to you.
Getting Started
From licence key to live data, in three steps
Everything here describes the product as it is today. If something doesn't match what you see, please let support know.
01
Get a licence and install it
Sign up through the customer portal, pick a tier, and your licence key appears on your account page straight away. You need a server with at least 2 processors and 4 GB of memory, on-premise or in your own cloud account; nothing is hosted for you. Then run one line on it.
Windows Server (or Windows 10/11), no Docker needed, in PowerShell opened with Run as administrator:
irm https://witstreamconnect.com/install.ps1 | iex
Linux, with Docker, in a terminal:
curl -fsSL https://witstreamconnect.com/install.sh | bash
The installer asks for your licence key once, creates a dashboard API key and shows it to you (keep it; the dashboard asks for it the first time), then ends with numbered steps, including the address to open in a browser on any computer that can reach the server. On Windows it installs WITStream Connect® as a service that starts with the server and opens Windows Firewall for it. Running the same line again later updates to the newest version and keeps your settings.
02
Map your first connection
Click Configuration at the top right of your dashboard, then + Add connection beside the Connections heading, and choose the Source type: WITSML, WITS0, ETP, OPC-UA, Modbus, or LAS file. Each source type reveals only the fields it actually needs. If your rig's own mnemonics don't match the standard set, the mnemonic map translates them, this is the same settings screen that reconfigures for a completely different contractor's channel numbering with no code changes.
Outputs (CSV, or any of the six formats) are tick boxes under Additional output sinks on the same screen; each network output is given a free port automatically. Click Save configuration at the bottom, then Apply now in the green message at the top, and the change is live within about half a minute.
03
Watch it run
The live dashboard shows every connection's live state. Transferring means data is flowing; reconnecting means a connection dropped and is retrying on its own, no action needed; a plain suspended badge with a message means it needs a look, usually a specific, readable reason (an unreachable address, a rejected credential) rather than a generic failure.
Common questions
A connection shows "suspended", what do I do?
Read the status message next to it first, it gives the specific reason. Most causes are an address or credential issue on the source system itself. It will keep retrying on its own; nothing else stops running while it does.
Can I try it with a simulated rig?
Yes, ask us and we switch it on for your licence; it appears on the configuration screen as Mock (demo) within about 15 minutes. It is useful for evaluating the product before your rig feed is connected, for setting up your outputs (testing your historian, OPC-UA client or WITSML consumer against steady data, away from a live rig), and for training operators on the dashboard and configuration screen.
Can I change tiers later?
Yes: click Manage subscription on your account page in the customer portal. Nothing about your configuration needs to change; tiers only govern how many rigs can connect at once, and your installation picks up the new tier within 15 minutes.
Does reconfiguring for a new rig need a developer?
No. A different contractor's channel numbering, a different unit set, a different protocol entirely, all of it is the same settings screen described in step two above, with zero code changes.
How do I choose how a log displays on the dashboard?
Open a connection on the configuration screen and scroll to its "Log display" section. Add the mnemonic you want to control and pick a radial gauge, a line or area trend, or a depth-indexed trend. Anything left unconfigured just uses a sensible default, nothing needs choosing before the dashboard looks right.
Something not covered here?
Self-hosted, universal drilling data hub.
© 2026 WITStream Connect®.