RYGTRON

EVERY RIG WATCHES THE GAUGE.

RYGTRON WATCHES THE TRAJECTORY.

RYGTRON reads the kinetic signature of your drilling operation — downhole mechanics and surface flow integrity — and predicts the trajectory toward a critical event before non-productive time accrues.

A software-only overlay that integrates with your existing WITSML / SCADA telemetry. No new hardware. No replacement of your drilling infrastructure.

The Problem

WHY RIGS LOSE DAYS

Reactive Drilling

Your driller sees a torque spike only after the pipe has already stuck. By then, the rig is down, the day is lost, and the NPT invoice is climbing at $250k–$500k a day. The mud log tells you what already went wrong.

RYGTRON

RYGTRON watches the trajectory — how fast torque is climbing, how much momentum the deviation carries — and flags the downhole event minutes before the pipe sticks.

Dual-Branch Architecture

ONE ENGINE. TWO OPERATIONAL DOMAINS.

RYGTRON runs the same kinetic kernel across both branches of your operation — the physics never changes, only the signal vocabulary does.

DOWNHOLE

Drilling Mechanics & Wellbore Integrity

Reads the kinetic signature of the drill string — ROP, torque, WOB, standpipe pressure, vibration. Predicts kick, pipe-stick, and trajectory-loss signatures before they cascade into non-productive time.

Rate of PenetrationDrill String TorqueWeight on BitStandpipe PressureVibration HarmonicsMud Weight

Rapid-Response Directive

CRITICAL DOWNHOLE EVENT — INITIATE KICK/STICK PROTOCOL

SURFACE

Flow Assurance & Pressure Integrity

A PYNTIX-shaped volumetric defense layer for the surface. Detects flow-rate spikes, wellhead pressure anomalies, and leak signatures — predicting blowout and flow-assurance threats before they escalate.

Flow RateWellhead PressureTemperaturePipeline ThroughputChoke Pressure

Rapid-Response Directive

CRITICAL SURFACE EVENT — INITIATE CHOKE / SHUT-IN PROTOCOL

How It Works

THE SAME PHYSICS THAT PREDICTS MOTION
PREDICTS DOWNHOLE FAILURES.

A drill string losing equilibrium is a signal in motion. RYGTRON treats it like a physical object — reading its mass, velocity, and momentum to project where the well is heading, not just where it is.

1

It Reads the Telemetry

RYGTRON ingests the same WITSML / SCADA data your rig already produces — ROP, torque, WOB, standpipe pressure, flow rate, wellhead pressure — through your existing drilling bridge.

2

It Computes the Kinematics

The engine calculates the deviation from the well plan baseline, the structural mass of the reading, and the rate of change (velocity). No new data — just new math on existing telemetry.

3

It Projects the Trajectory

When velocity and momentum cross a kinetic threshold, RYGTRON flags the well as trending toward a critical event — before the pipe sticks or the pressure kicks. The trajectory is the early warning.

4

It Directs the Response

One of three directives: DRILLING NOMINAL, DOWNHOLE ANOMALY, or CRITICAL DOWNHOLE EVENT. The driller gets the prediction and the recommended action, not just a raw gauge reading.

The Three Directives

DRILLING NOMINAL

Parameters within plan. No action needed — keep drilling.

DOWNHOLE ANOMALY

Drill string trending off-plan. Watch this well more closely.

CRITICAL EVENT

Kick / stick signature detected. Initiate protocol immediately.

The Engine

RYGTRON READS THREE THINGS

The same kinetic principles that describe how objects move through space — applied to your wellbore and surface flow in real time.

Deviation Rate

How far the reading has drifted from the well plan baseline. A torque spike deviates before the pipe sticks and the NPT clock starts.

Flow Velocity

How fast the deviation is growing. A pressure reading trending toward a kick accelerates — the velocity is the early warning signature.

Kinetic Index

When deviation spikes AND velocity surges simultaneously, that's a kinetic event signature. RYGTRON catches it the instant it begins.

The Difference

THRESHOLD VS. TRAJECTORY

Legacy SCADA

RYGTRON

What it watches

A fixed threshold (pressure > X)

The trajectory toward the kick

When it alerts

After the parameter breaches

Before the event cascades

What it tells you

A gauge was too high

The well is trending critical, with a recommended action

Integration

Replaces your drilling software

Software overlay on existing WITSML/SCADA — no new hardware

Alarm fatigue

Every threshold breach = an alert

Only kinetic-signature events alert — fewer false alarms

Pricing

Per-rig enterprise contracts

Flat annual — unlimited telemetry across licensed rigs

Who It's For

IF YOUR OPERATION HAS A WELL, RYGTRON READS IT

Onshore Drilling

Offshore Platforms

Pipeline Ops

Midstream Flow

Pricing

FLAT ANNUAL. UNLIMITED TELEMETRY.

$150,000/YEAR

Unlimited downhole + surface telemetry ingestion

No per-reading charges — no metered usage fees

No new hardware — software overlay on existing WITSML/SCADA

Billed annually via Stripe — all-inclusive for licensed rigs

License RYGTRON

DEPLOYMENT

HOW RYGTRON INTEGRATES

A standardized five-step integration process gets RYGTRON live on your operation without replacing your existing infrastructure. Full production deployment typically takes 4–10 weeks, depending on operational scope, data availability, cybersecurity requirements, and the condition of your existing telemetry environment. Software overlay only — no new hardware, no rip-and-replace.

1

CONNECT

Point RYGTRON at your WITSML / SCADA telemetry bridge. No new hardware — the engine ingests the same data your operation already produces.

2

MAP

Map your signal vocabulary to the kinetic kernel. Define your baselines, sectors, and asset labels so the engine speaks your operational language.

3

BASELINE

Establish the structural baseline for every signal. The engine learns your normal operating envelope — deviation is measured against this, not a generic threshold.

4

VALIDATE

Run the engine in advisory mode alongside your existing workflow. Confirm the directives align with your operational reality before going live.

5

DEPLOY

Go live. Choose your approval mode — advisory, assisted, or autonomous — and the engine begins issuing directives with full audit receipts.

HARDENED AT THE GATE

Every inbound telemetry reading is authenticated against a per-license API key and passed through a standardized ingest security layer that enforces input validation, rate limiting, and replay protection. Spoofed, duplicated, or malformed signals are rejected before they ever reach the kinetic kernel — ensuring RYGTRON only acts on verified, trustworthy data.

AUDIT RECEIPTS

Every directive RYGTRON issues is sealed with a deterministic audit receipt — an immutable provenance packet containing the input hash, kinematic snapshot, the exact classification rule fired, the engine version, and a timestamp. This receipt enables full compliance replay: regulators and operators can reconstruct exactly why a directive was issued, long after the event occurred.

RYGTRON is an operational decision support tool, not a safety-critical control system. All directives are mathematical projections based on telemetry deviation and kinematic trajectory. Integration does not modify or replace your existing operational infrastructure.

YOUR WELL IS IN MOTION.

RYGTRON READS THE TRAJECTORY.

Connect your drilling bridge and let the kinetic engine predict downhole and surface events before they cascade.

RYGTRON

© 2026

RYGTRON is an operational decision support tool, not a safety-critical control system. All directives are mathematical projections based on telemetry deviation and kinematic trajectory. Not a substitute for driller or operational judgment.