PipeProwler — flagship
Severity-graded pipeline notices with full source-to-API lineage at sub-minute latency — the physical signal layer the rest of the platform is built on.
PipeProwler surveils the pipelines and corridors that move Henry Hub prices, including every active Gulf Coast LNG export corridor, in real time. Pipeline notice text and scheduled-quantity flows are ingested continuously, standardized into a unified topology of meters and hub tags, and resolved into severity-graded events with full data lineage from raw source to API.
For the discretionary trader watching Henry Hub, the question is always whether the next move in price will be driven by something happening physically — a compressor outage, a freeze-off, an LNG feedgas curtailment, a force majeure on a corridor — before that physical event shows up on the screen. PipeProwler exists to surface those events the moment they post, scored for materiality, with full lineage back to the original notice so a trader, a risk team, and an audit team can all defend the same interpretation.
When a notice posts to a pipeline's electronic bulletin board, PipeProwler reads it, scores it across the dimensions that actually matter for trading, and surfaces it as a single resolved event.
Source: EBB notice · ID 84511 Resolved: 14:32:08 UTC · +47s
A severity-graded event answers three questions at once: what physically happened, how much capacity is affected, and whether the displaced volumes will reroute or stay constrained. Every field is sourced — the original notice is one click away, the standardization is reproducible, and the score itself is reviewable. The directional call is made by your models, not ours.
Coverage is defined by relevance to price, not by network breadth.
PipeProwler surveils the U.S. interstate pipelines that move physical volumes into and out of the Henry Hub area, and every active Gulf Coast LNG export corridor. The product point is not how many pipelines the platform monitors; it is that the pipelines the platform monitors are the ones whose physical actions actually move Henry Hub.
Three roles use PipeProwler differently. The product is designed to serve each.
Read PipeProwler events as the leading physical-reality signal — what's actually happening on the grid before it shows up in the futures price. The severity grade and capacity impact let the trader judge in seconds whether an event matters for the current position.
Use PipeProwler to track the corridor-level constraints that drive basis pricing across the U.S. grid. When a pipeline event affects deliverability into a specific hub, the basis trader needs that signal in the same moment the cash market starts to move.
Use PipeProwler to monitor the feedgas-corridor flows into the Gulf Coast export terminals. A maintenance window or a force majeure on a feedgas pipeline can reroute global cargo economics; PipeProwler surfaces those events the moment of the upstream notice.
Three product attributes a buyer should expect from a real signal infrastructure surface — and that other vendors in this lane do not deliver.
Notices are not a feed to be sifted; they are scored, resolved, and prioritized at ingest. The buyer sees what matters first, with the score made defensible by the underlying data.
Every observation traces back to the originating notice. A trader, a risk team, and an audit team can all stand in the same record of what happened, when it happened, and why it matters.
When a notice posts, the resolved event surfaces in under a minute. The trader who has to react to physical reality before the screen moves cannot wait on ten-minute polling cycles or research-cadence reports.
PipeProwler is built to plug into institutional workflows.
REST API today, with Python SDK, Excel Add-in, and Snowflake share on the roadmap. Custom alert routing over email, SMS, Slack, Microsoft Teams, and webhooks for events that need to reach the desk in the moment — additional channels on request. The same resolved data surface drives the dashboard, the API, and the alerting layer.
The platform's data sources, standardization, quality controls, and the severity rubric are visible to the buyer through the lineage trail every event carries. Severity scoring is deterministic: every event runs against versioned rules and content-hashed processes that reproduce the same output from the same inputs. The rubric's dimensions and framework are published; specific thresholds and scoring weights are held back as proprietary calibration.
The event exhibits and coverage figures are measured against production, not estimated. Every event carries the operator's posting time, our first-seen time, and our processing time, so latency claims are verifiable against our own data. Thirteen independent monitoring layers watch the surveillance itself, and every operator index is reconciled against our capture. SSO/SAML available for institutional deployments. SOC 2 in progress. Data lineage and audit logs available on request.
The U.S. interstate pipeline network and every active Gulf Coast LNG export corridor. The scope is calibrated to the pipelines and corridors that physically move Henry Hub prices, not to the largest meter count the platform can publish.
Notice text and scheduled-quantity flows are ingested continuously from FERC e-tariff postings and operator electronic bulletin board systems, then standardized into a unified topology of pipeline meters and hub tags before being resolved into severity-graded events.
Sub-minute. The platform resolves raw notice text into severity-graded events at sub-minute latency from source to API, measured from the moment a notice posts on the upstream source to the moment the event is queryable in the buyer's hands.
Force majeure events, capacity reductions, scheduled and unscheduled maintenance, pigging operations, flow direction changes, and other operational notices that materially affect physical gas flows. Every event is graded across five severity dimensions and tagged by corridor, basis pair, event type, and audience relevance.
REST API today, with Python SDK, Excel Add-in, and Snowflake share on the roadmap. Custom alert routing over email, SMS, Slack, Microsoft Teams, and webhooks for events that need to reach the desk in the moment. The same resolved data surface drives the dashboard, the API, and the alerting layer.
Institutional natural gas market participants: heads of trading, basis desks, LNG marketers, midstream operators, utility risk managers, and the risk and data teams who support them. The platform is sold through direct engagement.
PipeProwler is sold through direct engagement with natural gas market participants. Reach out for a working demo — coverage, severity-grading, and lineage shown live across the platform.
