Operators see the fleet
Prioritize the sites that need attention, acknowledge alerts, and keep the response visible to the rest of the team.
Solar operations monitoring
Stay ahead of lost production.
Solarverse shows you which solar sites are falling behind, what changed, and where your team should look first. Do it before the month-end report.
Installer, EPC, and O&M teamsWeb and native mobile
FleetAuto-refreshing
Current output0.00 MW
Updated 38s agoEnergy today0.0 MWh
Sites0
Inverters0/98
- Vršac Solar I412 kW
- Pančevo Field388 kW
- Subotica Ridge201 kW
- Zrenjanin North0 kW
Inverter 7 · Zrenjanin North: no telemetry after 3 intervals4m ago
Every minute
Fresh SunSpec readings
Connection-safe
Local buffering during uplink loss
Web + mobile
One status language everywhere
EU-first
Operational data residency
A problem at 10:42 should not become a month-end surprise.
Solarverse turns a quiet equipment change into a shared operating thread. Your team sees what happened, where it happened, and who is responding while the details are still useful.
Without that thread, teams rebuild the same context across inverter portals, weather feeds, spreadsheets, and service notes.
Zrenjanin North
Inverter 7 response timeline
The signal changes
Inverter 7 misses its expected telemetry intervals.
Detected from site data
Solarverse raises the alert
The site, device, last reading, and delivery state stay attached.
Email and push delivered
The response becomes visible
An operator acknowledges the event and the team sees who owns it.
Acknowledged by M. Petrović
One operational thread, from fleet signal to field action.
Solarverse keeps the context attached as you move deeper. The status, timestamps, units, and alert history do not disappear when you open the next screen.
01
Start with the exception, not the spreadsheet.
The fleet view combines current output, energy today, data freshness, and monitoring state. Search the portfolio or filter straight to degraded, offline, and faulted sites.
- Current production across the fleet
- Health state for every site
- A direct path into the affected plant
Fleet
12 sites · 2.4 MW capacity
Vršac Solar I412.4 kW1280 kWhHealthy
Pančevo Field388.1 kW1194 kWhHealthy
Subotica Ridge201.6 kW742 kWhDegraded
Zrenjanin North0.0 kW398 kWhOffline
02
See whether the weather explains the gap.
At site level, compare actual production with the weather-adjusted expectation. Performance ratio, irradiance, cloud cover, and forecast context help separate a weak day from equipment worth investigating.
- Actual versus expected energy
- Weather correlation and day-ahead forecast
- Clear configuration gaps when evidence is missing
Performance
Vršac Solar I · Weather-adjusted
Performance ratio
81.4%
Actual today
14.8 MWh
Expected today
15.6 MWh
Variance today
−5.1%
Actual versus expected
Today · five-minute intervals
ActualExpected
03
Give the person on call the full thread.
Solarverse carries fault and offline events from detection to delivery, acknowledgement, and resolution. Email, browser push, and native mobile push lead back to the same site evidence.
- One alert lifecycle across channels
- Per-operator notification preferences
- Web and mobile share the same status language
Alert response
Faults, offline events, and delivery
Device offline
Inverter 7 has not reported within three expected polling intervals.
Zrenjanin North10:42:18
Last power0.00 kWLast heartbeatunreachable
Email sentPush sent
AcknowledgeSolarverse10:42
Inverter 7 is offline
Zrenjanin North has missed three polling intervals.
Open site
Delivered to this device
The same operating truth, shaped for each person.
Solarverse keeps terminology, calculations, and status meaning consistent across the browser and mobile app while respecting each role's access boundary.
Technicians get the evidence
Open inverter electrical values, state changes, heartbeat quality, MPPT behavior, and history before heading to site.
Clients see only what is theirs
Grant read-only access plant by plant and present the experience with your product name, logo, and approved colors.
The site connects out. Your team does not connect in.
Solarverse keeps Modbus traffic on the plant LAN and gives each site an explicit provisioning path into the monitoring workspace.
01
Configure the site
Add the plant and its inverters in Solarverse, then create a one-time provisioning token for the site agent.
02
Connect from the plant
The agent self-registers, reads SunSpec over the local inverter LAN, and sends batched telemetry over outbound HTTPS.
03
Monitor and respond
Current readings appear in the fleet view while local buffering protects unsent data during an uplink interruption.
Remote monitoring without opening the plant to the internet.
Connectivity, access, tenancy, and data location are part of the product architecture. They are not settings added after deployment.
The inverter LAN stays private
The site agent talks to inverters over local Modbus TCP and sends telemetry outbound over HTTPS. Solarverse does not require inbound internet access to the plant.
Access follows explicit grants
Installer roles control operational actions. Client users remain read-only and see only the plants individually granted to them.
Tenant isolation reaches the database
Tenant-bearing application tables use forced PostgreSQL row-level security, transaction-local workspace context, and non-owner runtime roles.
Designed for EU operations
Solarverse's production architecture keeps operational data, backups, and logs in approved EU-region infrastructure with separated identity, application, and telemetry boundaries.
What teams ask before connecting a site.
The current product is built for KACO blueplanet inverters using SunSpec Modbus TCP. Solarverse reads the standard SunSpec device, AC inverter, and MPPT models rather than KACO's proprietary RS485 protocol.
See problems sooner. Protect more production.
Tell us how many sites you operate and where your current monitoring workflow breaks down. No account or password required.
- 15-minute introduction
- Review your current setup
- Leave with a clear pilot path