Private map
Your topology, assets, telemetry, and work state as layers on the same geographic surface the public market lives on.
See the public surface
Your own tenant on Ask the Grid. Connect the telemetry, network, and commercial systems your organization already runs; add private workloads; and read all of it against the live public market — without ever confusing public evidence with internal state.
Enterprise adds private layers to the map, network, and radar surfaces. Same instrument, now pointed at your operating truth.
Your topology, assets, telemetry, and work state as layers on the same geographic surface the public market lives on.
See the public surface
The same feeder, redrawn as a one-line: source, switches, and downstream share, laid out automatically from the topology, not hand-drawn.
See the public surface
Network, market, weather, forecast, and operational signals aligned on one clock — your operating picture, not a generic dashboard.
See the public surface
We speak to the industry's operational, network, and commercial systems — and stand up scoped connectors for the rest.
Operational historians
Telemetry, availability, and asset state from your PI System.
Network & GIS
Topology, conductors, switches, substations, and service territory.
Commercial
Positions, awards, schedules, settlements, and portfolio context.
Custom connectors
SCADA, EMS/ADMS, trade capture, and internal databases via scoped connectors.
Enterprise connectors are configured per engagement. Public market feeds remain source-attributed and separate from your private state.
A private grid is not just a view — it is a place to run private analysis. Your connectors and programs execute as isolated, sandboxed jobs on your tenant, with the results kept in your workspace.
Your data feeds run as isolated, sandboxed jobs on your tenant — the same runtime that powers our own market connectors.
Run BESS shadow programs and per-asset optimization against your own telemetry and the live market, side by side.
Recurring reconstructions, settlements checks, and reports — executed on a schedule, results kept in your workspace.
Private workload in a tenant
A BESS shadow program (or a private connector) running in an enterprise tenant — the job, its schedule, and its result read against the live market.
4/3· capture & drop inFirst-class tenant isolation in the data layer — your data never mixes with another organization's.
Bring your identity provider; scope who sees which assets, markets, and workloads.
Per-tenant credentials and connection secrets, provisioned and rotated for your tenant only.
Retention, residency, and deployment controls scoped to your organization's requirements.
A scoped engagement, not a self-serve toggle — most first deployments start with one market, a small private-data boundary, and one decision that matters.
Read your service territory, DER, and outages against the wholesale market your load and generation clear into.
Put your fleet's telemetry and dispatch inside the prices, constraints, and weather that shaped its opportunity.
Join positions, schedules, and settlements to the live nodal market and the events moving it — in one surface.
Tell us the market, the systems you'd connect, and the decision you're trying to support. We scope the tenant before we quote it — these are operating systems, not seats.