Independent diagnostics for battery storage assets.
Oxaide is a Singapore-based engineering firm focused on independent BESS diagnostics for operators, investors, and asset teams. We start with a scoped forensic review and expand to continuous monitoring only where the asset and operating context justify it.
The work has to be precise for engineers, clear for operators, and defensible for investment, warranty, and risk committees.
What buyers should understand quickly
A defined review path, not another software pitch.
Independent from vendor pressure
We are not the OEM, EPC, or dashboard vendor. The job is to state what the telemetry supports.
Defined review scope first
Asset block, telemetry window, and mandate question are fixed before conclusions move.
Monitoring only if justified
Verify comes first. Horizon follows only if the site truly needs continuous coverage.
Oxaide Verify
A scoped forensic review for teams that need an independent view of degradation, yield loss, thermal risk, or operational anomalies.
Defined forensic review
View review scope →Oxaide Horizon
A continuous monitoring layer for sites that need ongoing coverage after the initial review.
Continuous coverage if earned
View product →What standard dashboards often miss
Standard BMS telemetry reports voltage and state-of-charge. We read raw cycling data for early stress and degradation signals before they become failures, yield losses, or board-level surprises.
7+ Years
Infrastructure Delivery
Singapore
Headquartered
Gazetted
GeBIZ Supplier
Controlled Boundary
Boundary Control
Built for situations where the answer matters
The point is simple: the output has to hold up across operators, investment committees, insurers, and procurement reviewers.
Independent by design
We are not the OEM, EPC, or dashboard vendor. The answer stays tied to what the telemetry supports.
Built for mixed audiences
The output has to work for engineers, operators, investment committees, insurers, and procurement reviewers.
Deployment discipline
Where the environment demands it, we work with customer-controlled or isolated operating models rather than pushing unnecessary SaaS sprawl.
Operating Principles
Operating principles
Oxaide is built around deterministic, physics-informed methods, not presentation-first software. The work is meant to stand up in front of engineering, investment, operations, and procurement teams.
Direct principal review
Technical scoping and sign-off stay close to the person who built the method.
Selective engagement model
We stay focused on reviews where the answer changes an operational, investment, or risk decision.
Controlled deployment options
Managed, customer-controlled, and isolated deployment paths are part of the engineering problem, not an afterthought.
Enterprise-Grade Infrastructure
Managed deployments can use Microsoft Azure with Cloudflare edge protection. On-premise deployments can run without routine internet dependency.
Infrastructure Partners
Principal Review Lead
Lee Wen Jie
Founder & Principal
Oxaide · Singapore
Principal standard
When capital, warranty, or operating exposure is on the line, the work has to be technically precise, explainable under scrutiny, and clear enough to support a decision.
Oxaide exists for asset teams that need independent technical judgment rather than generic software optimism. The objective is a defensible operating read that can survive investment, warranty, and risk review.
Oxaide is a trading name of Rocketship Pte Ltd (UEN: 201806463W).
Singapore-based engineering firm · 7+ years in infrastructure and systems delivery
Scope first
Defined review scope
Boundary, telemetry window, and mandate question are pinned down before conclusions move.
Encrypted handling
Protected review workflow
Review traffic and operating data are handled with encrypted transfer and controlled access.
Customer boundary
Customer-controlled deployment
Managed, private, and isolated deployment paths are available when the environment requires them.
Direct accountability
Principal sign-off
Technical accountability stays close to the method rather than disappearing into a generic workflow.