Continuous diagnostics for BESS operators
dQ/dV and resistance profiling at the edge.
Use Horizon when periodic reviews stop being enough. It runs the same diagnostic logic on your own infrastructure so operators can catch drift earlier and act with evidence.
WITHIN RANGE
Module 04 · Cluster 01
Physics-informed review trace from the compiled analysis pipeline.
Continuous monitoring when the site truly needs it.
Earlier warning, local control, and a disciplined rollout path
Most diagnostic tools add another screen and another monthly bill. Oxaide is built to shorten the path to a usable technical decision, with deployment options that match the site.
Earlier signal detection
Horizon carries the same diagnostic logic into a live monitoring layer so operators can investigate drift before it turns into an outage, safety event, or warranty dispute.
Standard dashboards tend to show the symptom late, after the team has already lost time, yield, or confidence in the asset.
Deployment control
Deploy Horizon on infrastructure you control, whether you need a connected model or a local-only operating environment.
Many monitoring products assume a permanent cloud relationship even when the owner needs local control and a tighter operational boundary.
Commercial fit
Start with the site or operating environment where continuous monitoring matters most, then expand only if the evidence supports it.
Some vendors want the platform decision before the team has proved the monitoring layer is worth deploying.
What Horizon adds after Verify
Early Thermal Anomaly Detection
LFP batteries can hide degradation inside flat voltage curves. We use dQ/dV analysis to reveal patterns that help operators intervene earlier.
Internal Resistance Profiling
Resistance behavior often moves before visible capacity decline. Horizon helps operators track those changes and investigate risk sooner.
On-Premise Deployment
Deploy as a compiled binary on your own infrastructure. Detection and alerting stay close to the asset, while response remains with your existing safety systems.
Choose your deployment model
The same diagnostic logic, adapted to two different operational environments.
Connected deployment
On-site monitoring with a secure upstream path.
Use this model when teams need local analysis plus a centralized view for remote stakeholders.
Air-gapped deployment
No cloud dependency. No routine data egress.
Use this model for sites that require local-only analysis and a tightly controlled operational perimeter.
Start with Verify. Expand with Horizon.
Most teams begin with Verify. Horizon becomes relevant when the site needs continuous signal, not just another dashboard.
Horizon Pilot
Pilot deployment for one site or one operating environment.
Engagement model
Scoped around asset, telemetry path, and deployment model
- Builds on Verify findings and pilot goals
- Monitoring design for site topology and duty cycle
- Trend tracking across charge cycles
- Deployment planning for connected or air-gapped environments
- Structured pilot scope for one site or asset block
- Commercial path to a broader rollout if justified
Target Profile
How Oxaide Works:
The 2026 Capabilities Overview
A direct briefing on what Oxaide reviews, how the methods are validated, and where Verify and Horizon fit in a serious engagement.
Inside the briefing
• What dQ/dV and resistance profiling reveal that standard dashboards do not
• Typical degradation and yield-loss patterns we look for in BESS and solar telemetry
• How Verify and Horizon fit into a sensible engagement path

Focus
BESS + Solar
