Launch
The nearest station.
Perimeters and airports
The fence is long. The image from it must have an age.
One patrol cannot cover kilometres of fence. A drone from a station is at the sensor before a car. The operator in the centre decides on the response and needs to know the frame is valid.
Needs: Fleet from one centreControl from a centreEvidence after the flight
Illustrative case study
A fence, three stations, one sensor
This is not a customer and not a flight that happened. It is a description of how this area would read if the image carried its age.
A long perimeter, an illustration
Drones wait at stations. A fence sensor launches the nearest one. The operator in the centre decides on the response and needs the first valid image, not the last frame of the fence.
By the halls the signal drops. The stretch stays unchecked until the image meets the target. Flight near a runway is not in the example. That would need the airport's authorisation.
After the return the pack belongs to the sensor and the time. A station count on the website is not a design for a specific airport.
Arrival
Valid only.
A gap
The alarm is not closed on an old frame.
AKIZU is not the tower and does not authorise flight near a runway.
Image age through the example
The chart requires JavaScript.
The chart is a simulation. Move the slowdown and see when the example stops being under the 50 ms target. The target is not a measured result.
Deployment schematic
Where everything stands and how the image travels
The schematic is not to scale and is not a design for a specific site. It shows where the drone is, which two networks carry the frame and where the decision is made.
Numbers in the schematic
- 1Stations along the fence. The drones wait.
- 2Sensor S launches the nearest drone. The runway above is not in the example.
- 3Both networks. By the halls the signal drops.
- 4Platform ties the alarm to the sensor and time.
- 5The operator decides from the first valid image.
- 6The pack belongs to the sensor, not to the whole night.
Symbols in the schematic
- BStation or launch point
- DDrone with AKIZU Brain
- S1 · S2Two mobile networks at once
- PAKIZU Platform: fleet and pack
- OAKIZU Direct: operator and image state
Red and blue beacons: police, state, the military in training. Orange: everyone else. The blink is only on screen. Schematic, design. The list beside it explains the codes in the drawing. The beacon is a payload from another maker, not an AKIZU product.
Concrete case
Minute by minute
The same illustrative case as above, written out in time. The times are an example. It is not a record of a flight that happened.
- 01:00Quiet. Drones at the stations.
- 01:12Sensor S on the fence. The nearest drone launches.
- 01:13The stretch by the hall over the target. It stays unchecked.
- 01:14The first valid image at the sensor. The operator decides.
- 01:20Return to the station.
- 01:22The pack for sensor S and the time.
An illustration, not a deployment record. N
Use options
Everything it can be used for in this area
Each row is a separate use. The Parts column says which AKIZU parts it would involve. Status N is a design, C is a target, U is unknown.
| Use | Who uses it | What AKIZU supplies | Parts | Status |
|---|---|---|---|---|
| An airport fence away from the runway | Airport security | The first valid image at a sensor | Brain, SIM, Platform, Direct | N |
| A power plant or substation | Operator | An alarm tied to a sensor | Brain, Platform | N |
| A prison or a warehouse | Site owner | No closing an alarm on an old frame | Brain, Direct | N |
| A regular fence round | Site protection | Stretches where the image drops | Platform | N |
| Flight near the runway | — | Needs airport authorisation, not in the example | — | U |
None of these uses is deployed today. A row is not an offer and not an authorisation to fly.
01
The problem today
01
The fence is longer than one route
Without stations and rotation, stretches stay without an image.
02
Metal and halls disturb the signal
At an airport and on an industrial site the link breaks over short stretches.
03
An alarm at night
The operator cannot see whether the image has frozen before deciding.
04
An airport has its own rules
Flight near a runway is not ordinary operation and AKIZU does not authorise it.
Without AKIZU and with AKIZU
The same situation, different information on the screen. Proposed behaviour, to be verified in a pilot.
| Situation | Without AKIZU | With AKIZU |
|---|---|---|
| The image is late | The image looks live; the pilot does not know how old it is. | Frame age is on the screen and the state changes to Reduced freshness. N |
| Several drones, one team | The operator does not know which image is current. | Every drone has its own age and state. An old image is not treated as confirmation. N |
| The pilot is in a centre far from the drone | Latency changes and the pilot cannot see it. | The deadline guard warns when a command arrives late. N |
| You need to explain what happened | Video without exposure time and without commands. | Evidence package with image age, states and commands. N |
02
How it would work
- StationsDrones sit along the perimeter. Platform shows which one covers which stretch.
- AlarmA sensor launches the nearest drone.
- ArrivalDirect shows the image age. The response rests only on the Valid state.
- A gapIf the image is not valid, the stretch stays marked unchecked.
- ReturnThe drone lands at the station and the record closes.
- OperationsPlatform shows stretches where the image repeatedly loses freshness.
The flow is illustrative. AKIZU is in development.
03
Mission scenario
How many metres further the drone is than the image shows. Pick a scenario or set the speed and image age.
The interactive calculation requires JavaScript.
Scenario speeds are examples. 87.4 ms is the p99 measured internally over WiFi with a phone as transmitter, not on a drone.
04
Requirements and answers
| Requirement | How AKIZU answers it | Status |
|---|---|---|
| Nearest drone to the alarm | Platform shows the station and image age after launch | N |
| Signal by the fence and halls | Two networks, the switch is logged | N |
| Flight near a runway | Only with the airport's and the authority's authorisation. AKIZU does not grant it | N |
| Night camera operation | Depends on the drone; AKIZU has not verified it | U |
- Zmeasured internally
- Mmanufacturer data, not verified by AKIZU
- NAKIZU design
- Ctarget
- Pplan
- Odesign estimate
- Unot yet known
05
Who works with it
01
Monitoring operator
Decides on a response only from a valid image.
02
Perimeter technician
Sees stretches where the image repeatedly loses freshness.
03
Security manager
Has a pack for every alarm.
What we will measure in the pilot
- Time to the first valid imagewe will measure in the pilot P
- Decisions from an old image0 C
- Alarms with a pack100 % C
06
What you get after every flight
- Time from alarm to the first valid image
- Image age at the response decision
- Stretches with reduced freshness
- Network switches along the fence
- A pack for every alarm
- Overview of stations and their image coverage
Recommended products
07
Context
Airport drone operations have their own rules
EASA maintains the rules for unmanned systems. Proximity to a runway is for the airport and the authority, not for the image supplier.
Source: EASA
Remote stations already fly elsewhere
In September 2025 Aker Solutions obtained European certification for beyond-line-of-sight inspections of sites. That is not an AKIZU certification.
Source: Smart Maritime Network
How does image age differ from latency?
Network latency is only part of the journey. Image age is the time from frame exposure on the drone to its display to the operator. VERA attaches the exposure time to every frame and the station verifies it before display.
Does it work without a mobile network?
The AKIZU design is built around LTE and 5G. According to the manufacturer, the Starling 2 Max base platform also supports Wi-Fi and Microhard. Our internal measurement was done over WiFi.
Does AKIZU replace a BVLOS authorisation?
No. BVLOS flights need an authorisation in the Specific category based on a SORA 2.5 risk assessment. AKIZU Platform is meant to give the operator an image-age record as evidence for that assessment.
Can AKIZU fly beside a runway?
Not by itself. Flight near an airport needs the airport's and the authority's authorisation. AKIZU supplies image age if the flight is authorised.
How many stations are needed?
That follows from the length of the fence and from a pilot. The site shows examples only, not a design for a specific airport.
09
What the operator sees
The three image states in this area. Proposed behaviour, to be verified in a pilot.
The operator can decide on a response.
The stretch stays unchecked until the image meets the deadline.
The alarm is not closed on the last frame of the fence.
10
How the fleet is laid out
Illustrative layout. Drone and station counts are an example, not an offer.
Stations 1 to N
Along the fence
Each covers a stretch. An example, not an airport design.
Alarm drone
Nearest station
Flies to the sensor. Age from launch.
Centre
Monitoring
Sees which stretch is valid now.
11
How a response runs
Times are an example. They show when image age decides.
- quietStationsDrones wait. No live data until they launch.
- alarmLaunchThe nearest drone.
- arrivalImageA decision only from Valid.
- returnPackTied to the sensor and the time.
12
What we do not do in this area
Not the airport tower
AKIZU does not run runway traffic and does not talk to aircraft crews.
Not the fence
We do not supply sensors or fencing.
Not an authorisation to fly near a runway
The airport and the authority grant that.
A pilot in this area
The fence is long. The image from it must have an age.
We are looking for first partners. The application is pre-filled for this area.
Other areas
Example deployments are illustrative. AKIZU is in development and does not replace a BVLOS authorisation.
In more detail
Before a meeting on a perimeter
A station count on the site is not an airport design.
A sensor launching the nearest drone is an illustration only. Flight near a runway is not in the example. That would need the airport's authorisation.
An alarm is not closed on an old frame of the fence. We are not the tower.
Bring to the meeting
- Where the stations are.
- What the sensor launches today.
- Whether the route runs near a runway.
This is not
- Tower authorisation.
- A design for a specific airport.
- A guard contract.
Explore
Explore every area and the other sections
Twelve solution areas and the sections that belong with them. The case studies are illustrations, not completed deployments.
Solutions
01Public safety02Infrastructure inspection03Drone manufacturers04Defence and resilience05Logistics and medical transport06Industrial sites and ports07Crisis management and civil protection08Mobile operators09Corridors and convoys10Search and rescue11Public events