One Spine · Drone intelligence
Drone intelligence for a whole city.
We fly your city, map every building, drain and tree, then fly it again. Every department sees exactly what changed, and where, with the photos to prove it.
What changed in this ward since the last flight?
- 1
412 buildings new or extended
Found by comparing this flight with the last one. Nobody had to walk the ward.
- 2
38 built over the drain
Each one sent to the ward office that looks after that drain.
- 3
61 bigger than their tax record
Measured size against the size on the bill. The gap is revenue.
- 4
Tree cover down 2.1%
Mostly lost along the new road on the park's edge.
The whole idea
Everyone is asking the same three questions.
A city deciding where a drain floods and a bank deciding whether to fund a plot want the same things answered. One system can serve both.
Why it compounds
We keep every past look at the ground.
A report starts going stale the day it is written. This does the opposite: the next flight updates everything built on it.
A year later
Built-up area up 6.4%. Tree cover down 2.1%. Both traced to the ward responsible.
Nothing gets painted over. The second look at the same ground is the part nobody else can give you, because they never took the first.
What everything rests on
What it is built on.
Who opens it
Three kinds of user, one shared picture.
What it answers
28 decisions, grouped by the question, not the department.
All of them come off the same base. Spotting what changed answers a tax question, an encroachment question and a storm-damage question, so the next answer costs far less than the first.
Revenue, assessment & valuation
5 use cases
- “Which properties have grown since the register was written?”
- “Does this security exist as described, and what sits on it?”
Planning, development & compliance
6 use cases
- “What can be built here, at what scale, and what constrains it?”
- “What was built, and how does it differ from what was permitted?”
Infrastructure, utilities & assets
7 use cases
- “What assets exist, in what state, and which need attention first?”
- “Who is connected, who is not, and what would it take to reach them?”
Risk, resilience & insurance
5 use cases
- “For a given rainfall, how deep does it get, and which assets flood first?”
- “Across many locations, which are exposed, and by how much?”
Environment, energy & land
5 use cases
- “Which roofs and parcels can carry how much generation?”
- “Which parcels meet a stated requirement for size, access and terrain?”
How people use it
Different jobs need different screens.
How it is delivered
The same platform, three ways.
It is the same system for a government and for a company. What changes is where it runs and who can see what.
Public body
Who uses it
Many departments under one administration, each seeing only its own area
Where it runs
On your own servers when the rules require it, or a cloud in the same country
Enterprise
Who uses it
Sales, risk, planning and operations teams, plus the advisers they bring in
Where it runs
Hosted by us, kept separate from other customers when the data is sensitive
Published tier
Who uses it
Residents, small businesses, researchers and partner apps
Where it runs
Free to read, no personal details, capped above a generous limit
Honest limits
What we will not claim.
The most useful thing we can tell you before you start.
A photograph is not a measurement
A number you can stand behind comes from measured, checked data, and we tell you how sure we are, every time.
The system proposes, a person disposes
Nothing official goes out on its own. A person signs every decision that affects somebody.
Field work shrinks, it does not vanish
You still send people out, just to the right places, for a reason you already know.
Start with one neighbourhood, not a whole city.
One small area proves the whole thing works. And once we have flown it, the second look at that same ground is something nobody else can give you.