The operating system for solar service.
CANOS is the platform Cannon Solar built and runs to service 3,200+ sites in 22 states — monitoring, dispatch, work orders, SLAs, and portfolio reporting in one system. We didn't license it. We built it because nothing else did the job.
- SITE-2841 · Atlanta, GADispatched
- SITE-1907 · Tampa, FLIn Progress
- SITE-3312 · Austin, TXResolved
- SITE-2118 · Macon, GADispatched
Illustrative — actual portfolio view inside the platform, built & operated by Cannon Solar
CANOS speaks both ops and finance.
Pick the lens that matches your role.
Run your service desk like an air traffic controller.
If you're the person whose phone lights up when a system goes dark, CANOS gives you the screen you've always wanted. Every fault becomes a ticket. Every ticket has an owner. Every owner has an SLA clock.
- Tickets open themselves
Inverter fault, comms loss, underproduction — CANOS opens the ticket the moment monitoring sees it.
- Dispatch in two clicks
Nearest qualified tech, parts inventory, scheduled window, customer notification — all from one work order.
- Sign-off on the truck
Field techs close jobs from mobile with photos, readings, and customer signature. No paperwork in the office.
- Escalation built in
Tickets approaching SLA breach escalate to ops leads automatically. Nothing falls through.
From a fault on the roof to a closed ticket.
Six layers, one continuous loop. Every site you give us flows through this pipeline within minutes of going live.
- 5-min pollLayer 01Site telemetry
Inverter, optimizer, meter, and battery data pulled every 5 minutes from manufacturer APIs (Enphase, SolarEdge, Tesla, Generac, Tigo, etc).
$ tlmtry.ingest() → 2,847 sites - 1 schemaLayer 02Normalized fleet data
Different brands, different units, different schemas — normalized into one fleet model so a fault is a fault, regardless of vendor.
$ fleet.normalize(vendor) → ok - 120+ rulesLayer 03Detection rules
Threshold + anomaly rules per site class flag underproduction, comms loss, panel-level faults, and battery degradation.
$ rule.match(underprod) → hit - < 60 secLayer 04Auto-ticketing
Detections become tickets with site context, history, suggested cause, and parts likely needed — assigned to the right tech automatically.
$ ticket.open(#48211) → routed - Same-weekLayer 05Dispatch & resolution
Schedule, route, execute, document, close. Customer notifications fire at every step.
$ dispatch.assign(tech_07) → eta 2d - Daily pushLayer 06Reporting back
Daily, monthly, and on-demand exports back to your asset platform. CANOS is the operator; your AMP stays the system of record.
$ report.sync(amp) → 204 ok
The intelligence layer behind CANOS.
CANOS isn't just dashboards and dispatch. Underneath it runs Canos AI™, our proprietary AI operating system purpose-built for solar EPC. It's how we run 3,200+ sites with the discipline of a utility and the speed of a startup — and it's the same engine every CANOS customer benefits from.
Every project shipped on CANOS makes the next one tighter, faster, and cheaper to operate. Generic CRMs and horizontal AI copilots can't replicate this — the moat is the decade of solar outcomes feeding the model.
Adaptive design intelligence
Multi-model reasoning ingests utility data, irradiance, roof geometry and tariffs to produce engineer-grade designs in seconds.
Unified operations graph
Sales, engineering, procurement, install and service all operate on a single live graph — every lead, panel, permit, and truck-roll is one queryable object.
Autonomous workflow orchestration
Tasks self-route to the right human or automation based on capacity, geography, skill, and SLA — Canos AI doesn't just track work, it dispatches it.
Real-time margin telemetry
Per-project P&L updates with every material draw and labor punch. Margin erosion is detected in hours, not at month-end close.
The more it's used, the smarter it gets.
More projects → richer training data → sharper models → better outcomes → more projects. Each turn of the wheel widens the gap between Canos AI™ and any off-the-shelf tool a competitor could buy.
- 01 — ObserveEvery action is captured
Designs, redlines, install photos, commissioning data, service tickets — all event-sourced into one graph.
- 02 — LearnOutcomes label the data
Real-world results auto-label the upstream decisions, creating training signal generic AI can't access.
- 03 — RefineModels retrain continuously
The intelligence core ingests new outcomes and updates design heuristics, dispatch policies, and pricing logic.
- 04 — CompoundTomorrow > today
Every project shipped raises the floor for the next. The platform you onboard onto only gets faster over time.
CANOS plugs into the stack you already have.
We're the operator on the ground. Your AMP, CRM, and monitoring portal stay the system of record — CANOS just keeps them honest.
- Also Energy (PowerTrack)
- Locus Energy
- PowerHub
- Conductor (kWh Analytics)
- Salesforce Energy & Utilities
- Custom AMPs on request
- Enphase Enlighten
- SolarEdge Monitoring
- Tesla Fleet API
- Generac PWRview
- Tigo Energy Intelligence
- Mana Monitoring
- Salesforce Service Cloud
- HubSpot Service Hub
- Zendesk
- ServiceNow
- Custom REST API & webhooks
- Scheduled CSV/SFTP exports
Don't see your platform? We've integrated with most of them — just ask.
What lands in your inbox the first of every month.
An illustrative monthly rollup for a 247-site residential portfolio. Real reports include site-level detail, ticket history, and SLA evidence.
- Inverter fault14 tickets
- Comms / monitoring loss9 tickets
- Underproduction7 tickets
- Battery service5 tickets
- Other3 tickets
| Site | Issue | Opened | Resolved | SLA |
|---|---|---|---|---|
| SITE-2841 · Atlanta GA | Inverter fault — Enphase IQ8 | Mar 04 | Mar 06 | Met |
| SITE-1907 · Tampa FL | Comms loss — Envoy reboot | Mar 09 | Mar 10 | Met |
| SITE-3312 · Austin TX | Underproduction — soiling | Mar 14 | Mar 18 | Met |
| SITE-2118 · Macon GA | Battery degradation — capacity test | Mar 22 | Mar 27 | Met |
Illustrative — actual reports include full site detail and SLA evidence
Put your portfolio on it.
Tell us about your sites and how you want to engage. We'll come back with a coverage proposal, SLA recommendation, and integration plan within 24 hours.