Home › Monitoring accounts

Monitoring accounts

Every system's monitoring, findable in one place.

A fleet of installs across a dozen manufacturer portals is a fleet nobody can actually check. One screen, one catalog of monitoring links, map and table views, and encrypted credentials for the platforms that never opened an API.

Start free trial →7 days free · No credit card

A bookmark is not a monitoring integration, and pretending otherwise costs you callbacks.

Most inverter manufacturers give installers a portal and nothing else. A handful have real APIs, some have partner programmes with waiting lists, and several have no programmatic access at all. So the practical reality for a service company is dozens of portals, dozens of logins, and a customer on the phone while somebody hunts for which one their system is on.

SolarProjeX keeps one catalog of monitoring links per customer system, editable from the screen itself rather than through an import script. View the fleet as a map or a table, filter to one platform or all systems, and open the right portal for the right customer without guessing.

For the platforms with no public API, credentials are stored encrypted, with support for multiple accounts on the same platform — the normal situation when you have inherited installs from other companies. Where taking over a customer's monitoring account requires their agreement, there is a consent flow that asks them properly and records the answer.

  • One catalog of monitoring links per customer system, editable in the app
  • Map and table views, filterable to a single platform or all systems
  • Encrypted credential storage for platforms with no public API
  • Multiple accounts per platform, for fleets inherited from other companies
  • Platform picker covering the manufacturers service companies actually meet
  • Customer consent flow for monitoring-account transfers, with the answer recorded
  • CSV import for platforms that export their fleet, with per-account labels
  • Production alerts routed to the office, with low-impact noise filtered out

How it works

Built for the portals that exist, not the APIs you wish existed.

🗺️

Map or table

See the fleet geographically or as a filterable list. Both read the same catalog, so they cannot disagree.

🔐

Credentials, encrypted

For platforms with no API, store the login safely instead of in a spreadsheet — several accounts per platform if that is your reality.

🤝

Consent, properly asked

Taking over a homeowner's monitoring account needs their agreement. The request goes out, and the answer is recorded.

🔕

Alerts worth reading

Low-impact production alerts stop paging the office, so the ones that matter still get read.

Frequently asked questions

Is this a live production monitoring integration?

Where a manufacturer has a usable API, production data flows in. Where they do not, this is honest about being account and link management rather than dressing a bookmark up as a feed. Both are useful; conflating them is what leaves a company thinking it is monitoring systems it is not.

Which platforms are supported?

The platform picker covers the manufacturers a solar service company actually meets in the field, and adding another is a configuration change rather than a rebuild.

Why store credentials at all?

Because several major platforms have no public API and no partner access, and the alternative in practice is a shared spreadsheet of passwords. Encrypted storage inside the platform, with access controls, is the safer version of a thing companies already do.

Everything SolarProjeX does, built for solar

One platform from the first lead to the last warranty claim. Every capability below is part of it.

Run your solar service on one platform.

Start free in 30 seconds. No credit card. Cancel anytime.

Start your free trial →