Live network map
Feeder runs drawn as lines and colored by their worst pole. Storm badges, progressive marker disclosure for big fleets, and popups with live tilt drawings.
Grid asset monitoring
Catch the lean before it becomes an outage.
PoleDancer mounts a continuously-reporting tilt and environment sensor on your distribution poles and turns the telemetry into a live operations console — fleet-wide thresholds, per-pole overrides, storm posture, and history you can stand behind at a post-event review.
- 8 channels
- line power, lean, pitch, roll, temp, humidity, pressure, air quality — plus position
- 0 wires
- solar powered, mesh connected — no service drop, no site IT
- 24/7
- reporting on your schedule, with a storm-watch cadence
demo fleet — 24 poles, 4 feeder runs, one critical lean at 12.3°
The console
One screen your operations desk can actually run on.
Severity is computed the way your standards are written: lean against caution and critical thresholds, independent alert bands per metric, and interval-aware offline detection — a pole on a 30-minute reporting cycle isn't flagged after five.
From map pin to root cause in two clicks
Select any pole for its live tilt drawing, threshold-banded history charts that page back through time as you pan, an inclination gauge against its effective thresholds, and every environmental channel with staleness called out per field.
- History charts with drag-to-pan paging — pull older data without leaving the screen
- Per-field staleness: a dead sensor on a live pole raises a parameter-loss alert
- Install location vs. sensor GPS, with per-level fallback rules
Your standards, drawn — not coded
Caution and critical lean angles are set on a draggable angle picker that zooms itself to the range you're working in, so a 0.5° adjustment is a hand movement, not a config file. Fleet-wide defaults apply everywhere; the pole that deserves a tighter watch gets its own override.
- Fleet defaults with per-pole, per-branch, and per-zone overrides
- Independent caution / critical bands on every environmental metric
- Interval-aware offline rules — the example math is shown as you type
Thresholds that match your standards
Fleet-wide caution and critical lean angles with per-pole overrides for the crossing that deserves a tighter watch. A visual angle picker, not a config file.
Independent alert bands per metric
Caution and critical min–max bands on temperature, humidity, pressure, and air quality — plus required-parameter alerts when a channel goes quiet.
Zones & branches, with inheritance
Model your territory the way you operate it. Reporting schedules and position rules resolve device → branch → zone → fleet, and every selector shows what it inherits.
Storm watch
Flip a branch — or the whole fleet — to an elevated reporting cadence when weather moves in. Storm posture is badged on the map, so restoration crews see which structures moved, and when.
Offline detection that respects schedules
Offline means late against its own expected interval — a configurable grace period past each pole's resolved reporting schedule, not a blanket timer.
Accounts, roles & audit trail
Admin, operator, and read-only accounts under one organization — and a full audit trail of who changed which threshold, assignment, or setting, and when. Post-event review includes the humans.
Alerts that reach your team
A severity event log with acknowledgment, and notifications by email, webhook, or SMS — each user subscribed to exactly the severities and zones they own.
Field-tech view
A phone-first page per pole for the crew on site: navigate-to link, notes and photos, mark-as-inspected. The truck roll ends with the record already updated.
Fleet intelligence
Every pole keeps a case file.
Thresholds catch the pole that's already leaning. Trend analysis catches the one that's going to — a drift of a fifth of a degree per week never trips an alarm, but it's unmistakable in the history.
Lean trend analysis
Every pole's full-resolution history feeds a per-pole drift rate. A footing that's letting go moves slowly — PoleDancer surfaces it weeks before it reaches a threshold, while it's still a scheduled truck roll instead of an outage.
- Drift rate in °/week per pole, flagged while the pole still reads Normal
- Fleet rankings — your most failure-prone poles, and the failure modes they share
- Alert event log with acknowledgment: who saw it, who cleared it, and uptime per branch
- Scheduled PDF/CSV fleet reports; CSV export of any filtered list
5:58 AM on Feeder 2.
Every pole already reported in.
How it works
The poles look after each other.
Sensors on your poles form their own radio network — each one passes its neighbors' readings along the line, and one node with a cellular connection carries the whole run to the cloud. No wiring, no site survey, no IT project.
01
Clamp a node to the pole
Your crew mounts it in minutes. Solar powered — nothing to wire, nothing to set up in the field.
02
Nodes find each other
Every sensor talks to its neighbors by radio and passes their readings along the line, pole to pole.
03
One node phones home
A PD-X1 backhaul node gathers the whole run's data and sends it to the cloud over the cellular network.
04
You watch it live
Map, alerts, and history in the console. When a pole leans, loses power, or goes quiet — you know which one.
Runs as managed cloud hosting; self-hosted deployment inside your network is available on Enterprise plans.
Outage detection
When a span goes dark, know which one. Immediately.
Every node senses whether the line above it is energized. When supply drops, the poles that lost power flag themselves on the map within one reporting cycle — so dispatch sees the true extent of an outage, pole by pole, before the first customer call comes in.
- Line-power state reported alongside tilt and environment on every cycle
- De-energized spans drawn on the network map, separated from sensor-offline poles
- Storm watch raises the cadence, so restoration progress reads in near-real time
Hardware
Two nodes. One self-connecting network.
Sealed, solar-powered units your line crews mount during routine work. Every node carries a factory serial (PD-XXXXXXXX) printed on the enclosure — claim it in the console and it's reporting under your organization from the first message.
PD-S1
Sense nodeThe workhorse — one on every monitored pole.
- 3-axis tilt: lean, pitch, and roll from vertical
- Line-power sensing — reports whether its span is energized
- Temperature, humidity, pressure, air quality, GPS
- Solar panel with sealed battery reserve
- Self-forming mesh radio — relays its neighbors' readings
PD-X1
Backhaul nodeEverything the PD-S1 senses, plus the connection out.
- LTE / 4G / 5G cellular modem
- Collects the mesh — one serves a typical run of up to ~20 poles
- Store-and-forward buffering through network drops
Reporting cadence is fleet-configurable with per-branch overrides and a storm-watch mode; provisioning is by serial — no field flashing, ever.
Deployment
Your crews already know how to install it.
Nodes arrive provisioned, serialized, and labeled. A crew mounts one below the crossarm during routine work — no service drop to run, no field configuration, nothing to flash. The mesh finds its neighbors on its own; claim the serial in the console and the pole is reporting under your organization before the bucket is down.
- Self-powered — solar with battery reserve, no connection to the line
- Joins the mesh automatically; only the PD-X1 needs a cellular signal
- Claimed by factory serial (PD-XXXXXXXX) printed on the enclosure
- Install crews can be quoted through a PoleDancer partner when you want turnkey
Start with the corridor
that keeps you up at night.
Pricing
Priced per monitored pole. The more you watch, the less each costs.
You choose which poles to instrument — river and highway crossings, storm corridors, poles flagged at inspection. One subscription per monitored pole covers telemetry, the console, alerting, outage detection, and history. Volume breaks apply automatically as your fleet grows, so a long many-pole feeder lands well below the list rate.
Starter
Prove it on one feeder.
$10/pole/mo
PD-S1 $69 · PD-X1 $179 per node, one-time
- From 10 monitored poles
- Live console, map, and severity engine
- Outage detection and storm watch
- 12 months of history
- Email support
Most deployments
Professional
Run your territory on it.
$7/pole/mo
Same hardware list — volume breaks below apply
- Everything in Starter
- Zones & branches with schedule inheritance
- Lean trend analysis & fleet rankings
- API access & webhook notifications
- Scheduled PDF/CSV reports
- 36 months of history
- Priority support
Enterprise
Fleet-scale, hardware included.
from $4/pole/mo
Hardware included on a 3-year term — spares pool too
- Everything in Professional
- Sensor units + replacements included
- Unlimited history retention
- SSO (SAML/OIDC)
- Self-hosted deployment option
- Named support engineer & uptime SLA
- Rollout planning with your line crews
Volume price breaks
Applied automatically across your whole fleet, on Starter and Professional alike. Cross a threshold and every monitored pole moves to the better rate.
| Monitored poles | Platform rate | Hardware per unit |
|---|---|---|
| 10 – 99 | list price | list price |
| 100 – 499 | −10% | −15% |
| 500 – 1,999 | −20% | −25% |
| 2,000+ | −30% | −35% |
Annual billing. Most poles take a $69 PD-S1; one PD-X1 backhaul node serves a typical run of 15–20 poles, and its cellular data is included in the subscription. Hardware ships provisioned and serialized; installation is by your crews or a PoleDancer install partner, quoted separately when you want it.
Questions
Asked by every operations manager so far.
Do we have to instrument every pole?
No — and most fleets shouldn't start that way. Typical first deployments cover the poles where failure is expensive or likely: water and highway crossings, poles that carried inspection flags, storm-exposed corridors, and aging feeder trunks. Start with a feeder or two, then extend with the same zones and thresholds.
How does volume pricing work?
Every monitored pole on your account counts toward one total, and that total sets your rate. Cross 100, 500, or 2,000 poles and the whole fleet — not just the new poles — moves to the better platform rate, with matching breaks on hardware. Instrumenting a long feeder end-to-end is exactly the case the curve is built for. On Enterprise terms, hardware drops out of the math entirely.
How does a pole know it lost power?
Each node continuously senses the field radiated by the conductors above it — energized lines are unmistakable at pole distance. When that signature disappears, the node reports the span de-energized on its next cycle. Because the sensors are solar-powered and never touch the line, the mesh keeps reporting straight through the outage — which is the whole point.
How many backhaul nodes do we need?
Plan on one PD-X1 per run of 15–20 poles; the rest are PD-S1 sense nodes. The backhaul node is the only unit that needs cellular coverage, and its data plan is part of the subscription. During rollout planning we place the PD-X1s against a coverage map so a weak-signal corridor never strands a run.
Who installs the sensors?
Units arrive provisioned, serialized, and labeled. Your line crews mount them during routine work and claim each unit in the console by its serial — no field configuration. If you'd rather turn the whole thing over, we quote installation through a partner as part of your rollout.
What happens during a storm?
Storm watch flips selected branches — or the whole fleet — to a faster reporting cadence, and the map badges every run that's in storm posture. As crews restore service, re-energized spans clear on the map pole by pole, so progress reads in near-real time instead of by radio check-in.
Can we run it inside our own network?
Enterprise plans can deploy the full stack — broker, ingestion, time-series store, and console — on infrastructure you control, with the same per-pole subscription covering software and support.
Put a number on every pole you worry about.
Start with one feeder. You'll know your worst pole by the end of the first week.