Our platform
The Wattness Terminal
Live for ERCOT. Every US ISO/RTO next.
How views connect
The Terminal, layer by layer
From a published market file to an answer, in six layers.
01
Sources
Every figure starts in a published market file: from ERCOT today, from every US ISO/RTO next.
In ERCOT: prices at every dispatch run, settlement prices every fifteen minutes, the day-ahead market each day, and what each battery did, sixty days on. Each column is a battery, as tall as its MW.
- The file we follow · One day's dispatch record
- NP3-965-ER · sealed
- Next · Every US ISO/RTO, then the world
- Read from each market's own files
02
Data readers
Each file is checked against its source and read into a typed table.
Disclosures become a day's record for every battery and prices become intervals at every node; each table keeps its window, its gaps and which legs are estimated. Any figure can be traced back to the files it came from.
- Read and checked · The day's record
- Four source files, each checked against its source
- Readers · One for every view
- Fleet Board · Fleet Map · Battery Page · QSEs · Month Close · Market
03
Selections
Pick a battery and draw a circle around it; every view that reads the selection follows.
The battery in focus, a 100 km circle and its peers travel between the views that read them. Siting and Diligence keep their own, so exploring one never overwrites another.
- Circle around this battery · 100 km
- The batteries inside it, against the fleet
04
Tabs and sections
Each view is a tab built from sections, and linked tabs move together.
Candles, the Battery Page and the Fleet Map are tabs. Link them and one crosshair, one day and one battery drive them all; pin any section to your Watch Wall.
- Linked group · Candles · Tape · Forecast Vintages
- One crosshair · one day · one battery
- A section · One figure
- Traced back to the files it came from
05
Workspaces
A workspace arranges tabs for one role and opens on that role's question.
My Battery for owners, Lending and Diligence for lenders, Trading Day for QSEs, Market for traders, and more beside them. Each keeps its arrangement as you leave it.
- Owners · My Battery
- Lenders · Lending and Diligence
- QSEs · Trading Day
- Traders · Market
06
Ness
Ness answers questions from the Terminal's own data, beside the workspace.
Ask in plain words. Ness can also go full screen or float.
- Ness · Ask in plain words
- Beside the workspace · full screen · floating
Built for each role
For everyone around a battery.
Each role opens its own workspace, with Ness beside it.
BESS ownersMy BatteryHow does my battery compare with the batteries around it?(opens in a new tab)
DevelopersSitingWhich batteries are near my site?(opens in a new tab)
Lenders and investorsLending and DiligenceWhat is this battery's record, month by month, and how much does it vary?(opens in a new tab)
InsurersRevenue FloorsProWhere do shortfalls emerge across comparable batteries?(opens in a new tab)
QSEsTrading DayEnterpriseWhere does the fleet need attention, and what do its plans and records show?(opens in a new tab)
Traders and analystsMarketWhy did prices move, and what was known beforehand?(opens in a new tab)
ResearchersEvidenceCan I reproduce this figure and cite its inputs?(opens in a new tab)
Asset managersFleetWhich batteries trail their neighbors, and what is behind the gap?(opens in a new tab)
Next
One plan for the battery and its trades.
We are building the Terminal's analysis into one plan per battery: its energy and reserve offers, sent through its QSE and co-optimized by the ISO/RTO, alongside positions that need no battery, such as day-ahead virtual bids and hourly futures.

ERCOT today.Every US ISO/RTO next.Then the world.
Our Businesses
Storage Intelligence

What the model carries
- State of charge
- —
- Electrochemical fade
- —
- Thermal headroom
- —
- Interconnect limit
- —
Read at the asset, per interval
Cumulative, per cycle
Against the enclosure's own limit
Firm baseline and non-firm headroom
Values withheld. The desk publishes its method continuously.
Overview
What We Do
We develop deterministic, degradation-aware dispatch models for utility-scale BESS and hybrid assets. Real-time state of charge, electrochemical fade and thermal headroom enter the marginal cost curve directly, rather than being applied as a correction after the fact.
That lets participation be co-optimized across energy and ancillary products without eroding asset warranties or long-term operational life — the constraint the model respects is the one the hardware actually has.
Capabilities
What It Does
01Degradation-Aware DispatchUtility-scale BESS
Cycle depth and rate enter the cost of a decision rather than a maintenance schedule. A throughput a warranty will not carry is priced as unavailable, not as expensive.
02Thermal Boundary EnforcementEnclosure and power conversion
Headroom is read at the enclosure rather than inferred from ambient. A schedule that would derate the asset is refused at the boundary, before it reaches the market.
03Multi-Product Co-OptimizationEnergy and ancillary services
Energy and ancillary products are one coupled problem. Solved together under one physical constraint set, the asset can hold a commitment it would otherwise have had to hedge.
Our Difference
What Sets Us Apart
Most dispatch treats a battery as a nameplate rating with a schedule attached. The physics arrives afterwards, as a derate or an outage, and the schedule was always a fiction.
We model the asset at its boundary and decide against that model, so a commitment is something the machine can carry rather than something the optimizer hoped it could.
Our Businesses
Flexible Load Orchestration

What the model carries
- Deferrable share
- —
- Ramp profile
- —
- Thermal inertia
- —
- Curtailment tier
- —
By workload class, per interval
Time to reach a commitment
Hall and rack line
Access class held at the point of interconnection
Values withheld. The desk publishes its method continuously.
Overview
What We Do
We enable hyperscale data centers, AI training clusters and industrial facilities to participate as dynamic grid resources. Internal workload deferrability and thermal inertia are mapped to real-time nodal congestion, so the site can answer a constraint with a schedule rather than with an outage.
That is what makes rapid, non-firm access under connect-and-manage tariffs usable: the load can prove what it will give up, and give it up without risking operational downtime.
Capabilities
What It Does
01Workload Deferrability MappingAI and batch compute
Training and batch work carry slack that interactive work does not. Classified at the rack line, that slack becomes a resource the grid can be offered rather than a risk the operator absorbs.
02Congestion-Aware SchedulingNodal signals
The binding constraint is usually local and usually brief. A schedule that reads it directly can move work by minutes and clear a limit that a firm connection would have had to be built around.
03Non-Firm Access Under TariffConnect-and-manage
Access classes already exist in tariff. What has been missing is a load that can demonstrate it will honor one, which is a measurement problem rather than a regulatory one.
Our Difference
What Sets Us Apart
Curtailment is normally manual, coarse and total: a site is on or it is off, and the decision is made by someone reading a screen.
Deferrability is a property of the workload, not of the building. Read at that resolution, a hall can give the grid what it needs without giving up what it was built to do.
Our Businesses
Verifiable Market Dispatch

What leaves the platform
- Nodal offer curve
- —
- Real-time telemetry
- —
- Settlement file
- —
- Delivery record
- —
In the format the control room already ingests
At the cadence the market settles on
Structured for conventional QSE submission
Accumulated, and checkable after the fact
Values withheld. The desk publishes its method continuously.
Overview
What We Do
We turn edge decisions into artifacts a market already accepts: standard nodal offer curves, telemetry packets and settlement files that existing Qualified Scheduling Entities can submit without workflow changes.
Alongside each run we generate a selective cryptographic proof that it executed as declared, and a delivery record that accumulates — so a counterparty can check a claim rather than take it.
Capabilities
What It Does
01Native Market ArtifactsISO and RTO interfaces
Nothing here asks a market to change. What leaves is the same shape as what a scheduling entity submits today, which is the difference between a product and a proposal.
02Reconstructible ExecutionOptimization runs
A proof that a run happened as stated, generated beside it rather than after it. Verification sits alongside dispatch — no power market clears on a ledger, and none has to.
03Delivery ScoringHistorical performance
A declaration nobody can check is an invitation to inflate it. A score built from what was actually delivered turns self-asserted capability into something with a cost attached.
Our Difference
What Sets Us Apart
Coordination that requires a tariff rewritten is coordination that stalls. Most proposals in this space begin by asking the market to become something else.
This one is an overlay. The firm interconnection baseline stays exactly where it is, as a floor nothing may touch, and everything we add is above it and optional.
Get in touch
See it on ERCOT's own data.
The Wattness Terminal is open at wattness.tech. If you own, finance, insure or schedule batteries, or publish market data, tell us what you need from it.
