Skip to content
Orbitify
Changelog

Release 2026.11.06

Every change we make that people can see, newest first. Each release is named by the day it went out.

November 6, 2026Release 2026.11.06

New

Compare a turbine's defects across visits

A turbine's page has a new Across visits tab. Each defect is one row, with its blade, side, zone and distance from the root, its severity at every visit, and its trend: New, Worse, Same, Better, Not seen since a visit, Repaired (its request or work order is done) or Not checked (the latest visit did not photograph that part). Defects getting worse come first, so you can plan blade repairs before they become critical. Select a cell to open that photo from that visit.

In plans with InspectionsLink
New

See what you know as a graph

Knowledge has a new Graph tab, first in the list. Each dot is a page you may open, or an asset, location or asset type, linked by where an asset is, what it is part of, its type and the work orders pages cite. It opens with every dot in view; when your company has more than 2,000 dots, it opens on your biggest site. The assistant can open the graph beside the chat.

In plans with OperationsLink
Changed

One work order per turbine from defects

When you raise requests from a turbine's defects, you get one request per blade as before, and now also one work order per turbine that lists every damaged blade. The choice is ticked by default. Requests from drone findings now come only from accepted ones: findings the AI found that nobody has reviewed yet, and rejected ones, are refused, and the dialog says why.

In plans with InspectionsLink
Changed

Ungraded wind defects say Not graded

Before, a wind defect saved without a severity showed as Moderate. Now it says Not graded until someone grades it, in the defect list and the counts. A turbine's PDF report now holds only the accepted defects of the inspection you picked, each with its severity, blade and side, and uses the turbine's own blade length. Rejected defects are kept, hidden by default and left out of reports and counts.

In plans with InspectionsLink
New

Drone inspections add their assets

When solar or wind inspections are turned on for a project, its turbines with their blades, hub and tower, or its zones, blocks and strings, are added to Assets by themselves. Projects that already take drone inspections get theirs once, when this release starts, and a company with no asset types for turbines or strings gets the solar or wind ones. They are kept up as turbines are added, moved or changed and panel reviews are saved. A turbine that is deleted has its assets disposed of, never deleted, and a name you gave an asset stays. Each wind defect now records its blade and side.

In plans with InspectionsLink
Changed

Solar inspections count anomalies one way

Solar inspection setup and review now count anomalies the same way everywhere: detected, pending review and accepted, and reports and the sidebar count accepted anomalies only. Severity follows one scale everywhere, from the temperature difference: Moderate from 5 °C, Major from 10 °C, Critical from 15 °C. An inspection no longer adds its own layer to the map: its image sets and orthomosaics are listed under the inspection, and shapes drawn on the old layer moved to the Notes layer, and one with its own categories stays as an ordinary layer. The panel review is set out as steps.

In plans with InspectionsLink
Fixed

The assistant explains drone and map changes

Before, when the assistant offered to change a drone inspection, a map or a project file, its card and reply could show internal numbers instead of saying what would change. Now the card says it in plain words, such as Add the layer Roads to the map, and its reply says what was done. When it cannot do what you asked, or a map does not open, it says why, in English or Vietnamese.

In plans with AssistantLink
Fixed

Blade defect checks ask for photos

Before, checking the fix of a wind turbine blade defect asked for thermal photos and could name the defect only as a finding. Now the check names the defect, such as Crack, and asks for photos, which a person judges beside the photo of the defect.

In plans with InspectionsLink

How we change Orbitify

New things and fixes go out as soon as they are ready. A change to how you already work, or one that asks something of you, is announced ahead, by this much:

Kind of changeNoticeHow you hear
A new feature, an improvement or a fixNone: announced on the dayWhat's new and this page
A change to how existing work is done: a moved screen, a renamed step, a new required field, a default switched onAt least 14 daysA notice to your administrators, and a coming change in What's new
An administrator must act; a feature is removed; where data is kept, or which AI model or region answers, changesAt least 30 days, with a date to act byA notice to your administrators by email and in the Inbox until one of them acknowledges it, and a reminder 7 days before
A change that breaks what a connected system does through the API or webhooksAt least 6 months, under a new API versionThe API changelog on the developers page, an email to whoever answers for each connection, and Deprecation and Sunset headers
A security fixNone: explained afterwardsThis page

Building on the API? See the developers page for its version and its own changelog. Developers