Products

Products & technology

Four layers, one stack — and you can own every part of it

We build the hardware, the platform and the assistant ourselves, and we publish the parts worth publishing. Take the pieces you need: a gateway you can read the source of, a platform you can self-host, an agent you can keep behind your own keys, or a containerised data centre that runs where the grid does not reach.

01 · Open hardware

TXG-200 Field Gateway

An open industrial IoT gateway you can read the source of.

Schematics, PCB files, BOM and firmware are published under permissive licences. You can audit the design, build it yourself, or buy it assembled and calibrated — the data sheet does not stop where our convenience starts.

Open hardwareModbusLoRaLTE
  • 2× RS-485 (Modbus RTU / TCP master & slave), 1× RS-232
  • 4× analogue input configurable as 4–20 mA or 0–10 V, 2× digital in, 2× relay out
  • Ethernet, Wi-Fi, LTE Cat-1 / Cat-M1, LoRa (SX1262) and Iridium backhaul options
  • Mainline Linux — runs Modbus / MQTT / OPC UA bridges and your own containers
  • Secure boot, discrete TPM, per-device TLS certificates, signed OTA updates
  • Store-and-forward ring buffer sized for 30 days of readings at 5 s cadence
ComputeDual-core Arm Cortex-A55 · 1 GB RAM · 8 GB eMMC
Field busModbus RTU / TCP, MQTT, OPC UA, CAN (option)
Input power9–36 V DC, reverse-polarity protected, solar-ready
Environment−40 °C to +70 °C, IP66, Class I Div 2 pending
LicenceHardware CERN-OHL-P · firmware MIT
$449 assembled & calibrated · volume pricing on request
02 · IoT platform

Texas Energy IoT Platform

The device registry, rules engine and console behind every deployment.

One place for devices, gateways, users, alarms and exports. Host it with us, or run it inside your own network as a container bundle — the API is identical either way, so moving later is a configuration change, not a migration project.

Self-hostableREST APIMulti-tenant
  • Device registry with firmware, health and last-seen state for every asset
  • Rules engine with hysteresis, delays, quiet hours and escalation chains
  • Role-based multi-tenant access for operators, engineers and partners
  • REST + MQTT APIs, webhooks, scheduled CSV / XLSX exports
  • Retention tiers from 13 months of raw samples to fully decimated long-term trends
  • Audit log covering every configuration change
DeploymentHosted (US region) or self-hosted container bundle
IngestMQTT 3.1.1 / 5, HTTPS bulk, Modbus poll, OPC UA
ThroughputTested at 25,000 samples/s per cluster node
Retention13 / 36 / 84 months depending on tier
SLA99.95 % availability target, measured monthly
$49 / mo up to 25 devices · self-hosted licence from $2,400 / yr
03 · AI assistant

FieldOps AI Agent

Ask about the field in plain English, get answers grounded in your data.

An operations assistant wired into the same telemetry and alarms you already have. It correlates pressure, temperature, run time and dyno-card shape changes across a lease, explains what it found with links back to the raw traces, and drafts the work order — you approve anything that touches equipment.

AgenticOn-prem optionHuman-in-the-loop
  • Natural-language queries over wells, leases and time ranges
  • Anomaly narrative: what changed, when, and which sensor was leading
  • Alarm triage that groups related events and suppresses duplicates
  • Drafted work orders and shift handover summaries for a human to confirm
  • Runs on a small model at the edge, or hosted behind your own key
  • Read-only tool access by default; every write action requires approval
Data boundaryYour tenant only — never used for training
ModelsBring your own key, or on-box 7B–14B open models
LatencyTypical answer in 3–8 s for a 7-day window
ActionsProposal + evidence, requires operator approval
AuditEvery prompt, tool call and answer is logged
$99 / mo per lease group · included in Enterprise platform tier
04 · Off-grid compute

Off-Grid Compute Module

Turn field gas into compute capacity, with no grid interconnection.

A containerised data centre that arrives with its own generation. Feed it associated gas, flare gas or trucked LNG and it produces power, cooling and compute at the well pad or mine site — the premise being that where the energy is stranded, the compute should go to the energy rather than the other way around.

Gas-to-computeContainer DCBehind-the-meter
  • 20 ft and 40 ft container options, air-cooled or rear-door liquid cooling
  • Natural-gas gensets with scrubber / knockout skid for raw field gas
  • Accepts associated gas 800–1,200 BTU/scf with 30–100 % turndown
  • Battery-backed ride-through so workloads never see the transfer switch
  • Compute agnostic: GPU inference nodes, general-purpose servers or ASICs
  • Ships with the IoT platform monitoring it and the AI agent operating it
Sizes250 kW · 1 MW · 2.5 MW (electric)
Deployment time8–14 weeks from order, 3 days on site
NetworkStarlink / microwave / fibre — no grid required
CoolingAir, adiabatic assist, or rear-door liquid
AvailabilityN+1 generation, N+1 cooling, 99.9 % target
Request a review priced per kW installed and per kWh generated
Off-grid compute

From the flare stack to a rack

Where energy is stranded, move the compute to the energy. The chain below is what actually sits inside the container — nothing in it depends on grid power, grid timeline or grid price.

01

Field gas

Associated or flared gas taken off the separator — gas that would otherwise be burned at the flare stack.

02

Conditioning

Knockout drum, filtration and pressure regulation bring variable field gas to genset specification.

03

Generation

Stoichiometric gas gensets with N+1 redundancy; battery ride-through covers the load during transfer.

04

Compute

Containerised GPU or general-purpose racks run inference, telemetry processing or third-party workloads.

05

Operations

The same IoT platform monitors wells, gensets and racks; the AI agent triages alarms across all three.

Container models

Three reference sizes. Anything above 2.5 MW is scoped as a project rather than a product.

Model Footprint IT load Fuel draw Cooling Racks Lead time
OG-250 20 ft container 250 kW IT load ≈ 2.4 MMBtu/h Air / adiabatic 4 racks · up to 20 kW each 8–10 weeks
OG-1000 40 ft + genset skid 1 MW IT load ≈ 9.6 MMBtu/h Rear-door liquid 16 racks · up to 62 kW each 10–14 weeks
OG-2500 2× 40 ft + power skid 2.5 MW IT load ≈ 24 MMBtu/h Rear-door liquid 40 racks · up to 62 kW each Project scoped

Energy is stranded, compute is movable

Interconnection queues in the major US markets run three to five years. A container does not wait in that queue — gas that is already flaring at the pad becomes sellable compute within a quarter.

The generation already exists

Remote pads, mine sites and compressor stations have gas, right-of-way and crews on site. Adding compute to that footprint costs far less than building power for a compute footprint from scratch.

One console, not four

Because our IoT platform already knows the wells, adding genset and rack telemetry to it is a device registration problem — which is why the off-grid module ships with monitoring and the AI agent included.

Pick a layer, or take the whole stack

Buy the gateway and run the platform yourself, or hand us a site and we will return a running container. Same APIs either way.