Raptrix Power · We close the physics gap

Full-physics grid intelligence.
On the live system. Every five minutes.

Sentinel turns the State Estimator case your control room already has into recovery-validated contingency intelligence — so operators and planners finally see the same grid.

Zero disruption to existing workflows · Pilot in weeksEx-NYISO Principal Engineer · Runs alongside your EMS today
5min
Default cadence · configurable 5–15
N-200+scale
Screened contingencies
Full ACNR
Strict Q-limit enforcement
.rpfone file
Ops ↔ planning handoff
Bring your models — works with existing RAW, CIM, PSLF, or native SE exports
The problem

Operators are flying with incomplete instruments.

The tools that screen the grid for contingencies were built around tradeoffs the system can no longer afford. Three of them show up every shift.

DC approximation

The screening throws away the physics that matters.

The industry standard for large-scale contingency screening trades away reactive power and voltage fidelity — exactly the physics that matter most under today’s load growth and IBR penetration.

Stale model snapshots

High-fidelity analysis on a stale model is still stale.

Even full analysis run against a model snapshot is only as good as the model. The live system’s actual dispatch, topology, and load present a different risk profile than any forecast predicts.

Manual contingency lists

Hand-maintained *.con files go stale the moment a breaker opens.

Legacy tools require manually maintained *.con definitions that expire the moment topology changes or equipment returns. Topology changes happen continuously. The lists don’t keep up.

Why now

The grid has changed. The tools haven’t.

01

Grid stress is accelerating

Data centers, EV adoption, and industrial electrification are driving load curves the system was not built to serve. New generation — much of it variable and geographically distributed — is connecting faster than planning models can absorb.

02

The NERC compliance bar is rising

Reliability standards require operators to demonstrate thorough contingency analysis. Regulators increasingly expect operators to show their work — not just that contingencies were screened, but that the screening was comprehensive and the methodology sound.

03

The status quo has a visible ceiling

The limitations of DC approximation are not new knowledge. What has changed is that those limitations now produce consequences visible to operators, planners, and regulators. The question is no longer whether better analysis is desirable — it is whether it is achievable at operational scale.

The breakthrough

For decades, the industry accepted a forced choice. We eliminated it.

Scale or physical fidelity — never both. Raptrix Core removes the tradeoff that defined contingency analysis for a generation.

Solver method
×DC / linear approximation for scale
Full AC Newton-Raphson — no linearization shortcuts
Coverage
×Selective full-AC on pre-screened lists only
Tens of thousands of studies per default 5 min cycle (configurable 5–15)
Contingency definition
×Static *.con files that go stale instantly
Autonomous topology discovery — no static *.con files
Data source
×Model snapshots, not live SE data
Live State Estimator data — the system right now
Discovery
×Cannot find what it was not told to look for
Surfaces contingencies no prior tool could find
The platform

One physics engine. Four capabilities.

We close the physics gap — planning to real time — so operations, outage coordination, and reliability teams work from the same high-fidelity view of the grid.

Raptrix Core
Full-AC Newton-Raphson. Strict Q-limits. Solver cloning.

The physics engine every product runs on — commercial value sits in the solver and real-time orchestration, not in locking your models.

Short-term planning

Forge

  • Outage coordination on the same physics
  • Interconnection & what-if studies from real operating points
Adoption path

We are honest about how this market adopts new tools.

Trust is earned where wrong answers have consequences. Raptrix is built for the deliberate timeline this market requires.

  1. 1Year 0–1

    Entry — no workflow change required

    • Sentinel runs alongside existing tools
    • Findings available for watchlists, escalation, and planning input
    • Full-AC compliance documentation at a scope legacy tools cannot match
    • Sentinel findings passed upstream to Forge
  2. 2Year 1–2

    Confidence — demonstrated accuracy builds trust

    • Track record of accurate findings across topology and operating conditions
    • Sentinel outputs begin to influence operational decisions
    • Forge case library grows across millions of accumulated scenarios
  3. 3Year 2+

    Full value — real limits, real capacity

    • Operators use Sentinel’s real limits to run closer to physical capacity safely
    • Full economic and reliability value of the platform realized
    • Empirically grounded contingency library matures into a planning asset

This is a long sales cycle by startup standards. It is the right cycle for this market, and Raptrix is building for it.

Open architecture

Built to be auditable. Built to interoperate.

In a market where wrong answers have consequences, trust comes from transparency — not proprietary lock-in.

Bring your models

Zero friction. No lock-in.

Public converters for PSS/E, CIM, and PSLF turn your existing models into .rpf — unlimited size, MPL 2.0, on GitHub. Keep your stack; add planning-grade physics where it matters.

Standard EMS integration

No custom plugins required.

Works with major EMS vendors via standard file push. Every modern EMS already exports the solved SE case on a timer or button press — no vendor negotiations to get started.

Auditability by design

Verify methodology, not just outputs.

Every .rpf file carries the network state, contingency provenance, and a deterministic fingerprint so teams and auditors can verify how a result was produced.

Commercial value where it belongs

Solver + orchestration — not your files.

Studio and open converters stay free of model-size lock-in. The commercial path is the high-performance solver and real-time operational intelligence that run on top.

A new pattern of work

Every solved State Estimator case
becomes a planning-grade study.

Sentinel ingests the case your EMS already exports on a default 5-minute cadence (configurable 5–15). Exhaustive N-1 on the live case. Simultaneous N-2 from the defined common-mode list. Sequential N-1-1 on by default. Recovery-validated against LTE / Normal windows. From tens of thousands of “what-ifs” it surfaces the small number of unrecoverable scenarios — each with an auditable certificate.

For operators
Real-time visibility into contingencies your static lists miss.
For planners
A growing library of real operating states — not stylized study cases.
Recovery Certificate
sentinel://case/2026-05-22T13:05Z/ctg/L7842-out
Unrecoverable
contingencyN-2 · line + xfmr
case_modesolved · live SE
q_limitsenforced
pv→pq switches3
recovery_window15 min LTE
reserves_availinsufficient
// reason
Voltage collapse at bus 4421 under greedy reserve redispatch;
no admissible control sequence within NERC LTE envelope.
metadata.fingerprint 7c4a9e…b201schema v0.14.2 · arrow ipc
Sentinel · operational flow

From solved case to recovery certificate.

Every step is automated. Every filter is auditable. Every output is a canonical .rpf your planners can replay.

  1. 01

    Ingest

    Solved SE case · default 5 min

    RAW, PSLF, or native State Estimator exports — no rip-and-replace.

  2. 02

    Screen

    Exhaustive N-1 + defined N-2

    N-1-1 default after intervening recovery. Simultaneous N-2 is the defined common-mode list.

  3. 03

    Solve

    Full-AC Newton-Raphson

    Strict Q-limit enforcement and PV-PQ switching. No FDNR shortcuts.

  4. 04

    Recover

    LTE / Normal-window recovery

    Q-limits enforced. Greedy reserve dispatch + switched-shunt recovery (on by default). Only unrecoverable cases are surfaced.

  5. 05

    Certify

    Auditable per case

    Every filtering decision is grounded in defensible physics.

  6. 06

    Hand off

    Canonical .rpf out

    One file carries the operating state forward into planning. Every cycle also writes SAL.

Zero lock-in

Bring your existing models with zero friction.

Open converters for PSS/E, CIM, and PSLF feed the same self-describing .rpf interchange — so you keep your stack and still get planning-grade handoff from the live operating state.

Read about .rpf
PSS/ECIMPSLF.rpf
NERC Level 3 · Large Loads

Built for the grid that’s arriving — not the one we modeled in 2010.

AI data centers and other large, electronically coupled loads behave nothing like traditional demand. Sentinel treats them as first-class citizens — so operators and planners get a defensible, physics-based view of system risk without waiting on EMS vendor roadmaps.

Voltage sensitivity

Modeled natively at the bus, not assumed away with a generic load.

Up / down ramps

Rapid ramp and load-reduction schemes carried with the operating point in .rpf.

Contingency impact

First-class in N-1, defined N-2, and profile-armed VRT.

IBR interaction

IBR-tagged screening. FACTS/PST carried in .rpf; NR device control is not claimed.

VRT / large-load arming

VRT / large-load arming from load profiles.

Every operating state Sentinel evaluates ships with the computational-load profile attached — seasonal envelopes, buildout ramps, voltage guardrails, and reduction schemes.

carried in .rpf
Stability screening

Beyond steady-state — when the operating point demands it.

When dynamics data is available, first-swing stability screening runs on the same solved operating point used for contingency analysis. Large-load rejection scenarios are supported today; inverter-centric models are expanding.

Engineering services

Site selection & interconnection studies, with the same physics.

Planning-grade studies for candidate locations and POI/POW decisions — defensible diligence delivered on the same full-AC engine that powers Sentinel and Forge.

Site selection

Candidate-site screening and full-AC diligence aligned to your approval process.

POI / POW

Interconnection and withdrawal studies at planning-grade fidelity with auditable outputs.

Why this exists

Built by someone who knew what was missing.

Raptrix began in 2013 as Kestrel when founder Matthew Musto, a power-systems engineer with 22 years as Principal Engineer at NYISO, set out to solve contingency analysis the right way — full Newton-Raphson physics with no shortcuts. He spent those years inside the control room until April 3, 2026, when he left to build Raptrix full-time.

This is not a software company that discovered a grid problem. It is a practitioner who understood the problem from the inside — now leading a growing team shipping the only modern platform that pairs a high-performance C++ solver with real-time contingency analysis (Sentinel) and short-term planning (Forge) on one physics engine.

Disciplined physics

Full-AC Newton-Raphson with strict Q-limit enforcement and intelligent PV-PQ switching — non-negotiable.

Operator-first

Automation that augments operator judgment — never replaces it.

Deploy where you operate

On-prem (RHEL certified), air-gapped, or cloud. No vendor lock-in.

No-cost pilot for qualified teams

Pilot Sentinel on your representative case.

Bring a recent State Estimator export. We will run exhaustive N-1 + defined N-2 with LTE / Normal-window recovery and walk through the results with your team — no slide-deck theater.

Early adopter customers
Transmission Operations · Operations Engineering

A pilot engagement on your system — no workflow change, no day-one commitment to act on outputs. Just the chance to see what you have been unable to see.

Technology partners
EMS Vendors · Planning Software Providers

Our open-source I/O layer creates natural interoperability. We are not trying to displace your platform — we are trying to make it better.

Industry thought leaders
Standard-Setting · Grid Policy · Reliability Research

Engagement, validation, and co-authorship of the conversation about what rigorous contingency analysis should look like.

info@raptrixpower.com · Founder direct: matthew.musto@raptrixpower.com · github.com/RaptrixPowerFlow