A crew has photographed a turbine's information screen showing it stopped, and is asking for that to be recognised so a vessel or helicopter can put people on the tower. Nothing changes on the map until you approve it, and you set how long it stands.

Loading…

The distances a site alerts on, for text and WhatsApp messages only. Separate from the rings in the lightning view — those are your own screen and change nothing for anybody else. An administrator proposes a profile here; it does nothing until an owner approves it.

Once approved, the distances apply to every tower on that site, not just its map reference point — a strike can be forty miles from the site marker and ten miles from the crew at the far end of the array.

Loading…

Loading…

Send an automatic text message to a person's cellphone when lightning strikes are detected within 50, 30 or 10 miles of their assigned sites (closer strikes always alert immediately; an "all clear" text is sent once strikes stay away for 30 minutes). Each person can be assigned 1 to 5 sites.

Nobody can be enrolled by an administrator alone. You invite them, they complete the form and sign it, and then you approve. That signed record is what makes the message lawful to send, and it is kept as a certificate you can produce years later.

Loading…

Loading…

The link is single-use and expires in 14 days. If email is not configured it is shown here so you can pass it on yourself — an invitation should never evaporate silently.

Loading…

Texted STOP replies are honoured automatically. Use this for withdrawals that arrive by phone, email or in person — those carry the same weight and must still be recorded.

Adding a user emails them a one-time password-setup link. Regular users can't add anyone — only Admins and Owners can, and only Admins/Owners manage the Lightning text alerts above.

Visits, visitors, where they came from, which pages and console views they opened and how long they stayed — daily, weekly and yearly. Measured by this site itself: no cookie, no third-party analytics, no advertising network, and nothing that can follow anyone from one day to the next.

Loading…

Signed means signed the version now in force. Somebody who accepted an earlier version and has not seen the current one counts as Not-Signed, which is the reason to open this list at all. The NDA button lists every signed NDA with its certificate — master owner only, because the certificate is the signed instrument itself.

A safety check. It looks at every wind turbine’s map position and makes sure the globe, the site console and the lightning map all show the same, correct spot. If anything doesn’t match, it’s written to the error log for you. (This only checks — it changes nothing. To fetch fresh positions, use “Sync new server files locally” below.)

Fetches the newest turbine positions from public sources into a separate draft copy — the live website is never touched while it runs. When it’s done, a review window shows you exactly what would be added, changed or removed. Nothing goes live unless you download the draft and publish it through GitHub. You can also just throw the draft away. Master owner only.

How the self-learning forecast works, in one line: the software saves every forecast it makes, waits for the real weather to happen, compares the two, and teaches itself a small correction for each site — so it gets more accurate over time. Real-world measurements arrive with a delay (up to ~5 days offshore), so the numbers here build up over days, not minutes. Skill = how much better we are than simply guessing “tomorrow will be like today” (100 is perfect, 0 is no better). RMSE reduction = how much our learned correction improves the raw weather feed. Master owner only.

How many days of forecast a site writes down each run — which is what decides how far ahead the self-learning correction can ever reach. A correction at a given lead exists only once a forecast at that lead was archived and later checked against what actually happened, so this starts a clock; it cannot fill in the past.

The second self-learning model — the days past the first one's reach. The original keeps everything at and under the 72-hour look-ahead and is untouched by this; from 78 h upward this model answers, crossed over one lead bin either side so the forecast cannot step at the seam. It runs for Full and Max sites only.

Give a code to a tester; they redeem it on the login screen ("Sign in with access trial voucher") with their own email. 0 days = never expires (use that + role Admin for a long-term helper you can later promote to owner). Codes are shown once — copy immediately. Revoke anytime. Master owner only.

People who asked to be set up from the sign-in screen. No account exists for them — nothing was created. To let one in, generate an access code above and send it to them, then mark the request converted. Marking it here only records where the conversation got to.

PO/invoice access requests awaiting your decision. Approve activates the requested tier & sub-tier for that account (the account must already exist — issue an access code or have them register first). No card data is ever collected. Master owner only.

Every paying customer and all the seats under them — the account that bought the plan plus everyone they invited, including seats they promoted to admin. Open a customer to see their seats and devices.

Send overdue notice emails the customer that payment is late and starts a 5-business-day countdown. Their service stays fully on during it — someone locked out of the product cannot read the notice or show it to whoever signs the cheque — and it stops automatically when the countdown runs out.
Deactivate cuts the whole plan off immediately: every seat, every device, at once. They can still sign in and see why, so they can pay and come straight back. Reactivate restores the plan and re-enables exactly the accounts the deactivation blocked — never one that was already switched off before it. Master owner only.

Manually grant or change a customer's plan (e.g. after an off-platform contract). Seat cap defaults to the tier's cap if left blank. Master owner only.

Wind farms that were listed as “under construction” but now have real turbines visible in the latest data. Click promote to mark one as operational — that puts its turbines on the maps and creates its live site console.

Suggested profile corrections that need your yes or no (they came from only one source, sources disagreed, or an AI found them). Approve = the correction is applied and the maps update. Every suggestion shows where it came from so you can judge it.

Automatic backups. One is saved before anything big changes the data (the newest 20 are kept). Restore puts everything back exactly how it was at that moment — and it saves a backup of “now” first, so even a restore can be undone. User accounts are kept as-is unless you specifically choose to roll those back too.

User-submitted data & disputes from the console. 2 different admins or 1 owner must approve before an item is queued.

Your plan licenses a fixed number of devices (seats). Remove an old device to free a seat.

We store only what's shown here. Billing address & card details are handled by the payment processor at checkout, never by us.

For security, changing your password signs you out on any other devices.

Permanently deletes your account: sign-in credentials, profile, registered devices/seats and active sessions. This cannot be undone. Records of agreements you accepted or signed (Terms, Privacy Policy, NDA) are retained as legal evidence, as described in the Privacy Policy.