Many machines, from any maker, flown as one fleet — safely, and with a record of everything that happened.
AEROE is the software layer between a fleet of drones or robots and the people responsible for them. It asks every vehicle what it can do, plans only what the whole fleet can hold, refuses anything it cannot — and writes down every decision so it can be checked afterwards by someone who was not in the room.
Every drone or robot ships with its own controller, its own app and its own limits. Put twenty of them from three suppliers on one site and nobody has a single view of the fleet, a single place to plan, or a single record of what was done. AEROE is that place — and it belongs to no vehicle maker.
A vehicle joins AEROE through a small connector its maker or integrator writes against a published interface. The core of the platform never knows which brand it is flying — that is enforced by an automated check on every change, not by policy. Mixed fleets are the normal case, not a special one.
Speed, height, battery life, radio delay, how precisely it can hold a position, how well its clock is synchronised — every vehicle declares these, and every plan is checked against them before take-off. A plan the fleet cannot hold safely is refused, with the number and a suggested fix, at the desk rather than in the air.
Who approved what, which version flew, what each machine was told, what went wrong and what the system did about it — all written to a tamper-evident log and exportable as a bundle that a customer, an auditor or a regulator can verify without AEROE. Runs entirely on-site; nothing has to leave your network.
Each vehicle type gets a connector — written once, tested against AEROE's conformance suite, and certified. A simulator ships in the box, so a fleet can be rehearsed before a single real vehicle is powered on.
An operator chooses a formation or a sequence of them, in structured controls or in plain language. AEROE lays out every position, checks spacing, airspace, altitude, battery and timing, and either commits a numbered version or explains exactly why not.
The fleet takes station; the console shows it in 3D and from above, beside its own live event log. If a vehicle drops out, the response was chosen before launch — hold the shape, re-plan, or bring everyone home — and it is applied automatically.
What was planned, what was flown and where they differed — per formation and per transition — is exported as a verifiable bundle. Rehearsals can be replayed from the record, not from a recording of the screen.
Each picture below is the console's own top-down view of a formation the platform planned, checked and flew in simulation. Formations can be tilted upright in the sky, joined into timed sequences, and composed for where an audience or a camera will stand.
20 machines
24 machines
10 machines
13 machines
9 machines
14 machines
100 machines
14 machines
24 machines
18 machines
200 machines
90 machines
Also available: rectangle, and any picture or logo traced into a formation at authoring time. Spacing, spread and other measured figures for each panel are on the technology page.
The same machinery — sequences, pre-chosen responses, declared limits, evidence — serves each of these. What differs is the site, the operating manual and the people; the platform does not need to know which it is running.
Timed sequences of figures, checked so no two machines ever cross too closely between them; a viewpoint that is part of the plan; a rehearsal compared with the plan figure by figure. Built for operators assembling fleets from more than one maker.
Corridor sweeps with parallel lanes, routes over real ground, discs at even density — flown as sequences and checked against the battery of the weakest vehicle rather than the best. The export shows what was covered.
Perimeter patrols, standoff observation, search patterns, communications relay and logistics — non-lethal roles where the record matters as much as the mission. Runs on an isolated network; nothing leaves the site.
We say this plainly because it is the kind of thing a partner should hear from us first. Everything on this site — every screenshot, every figure — comes from AEROE's built-in simulator, which flies the same software the real fleet will. The platform is built against a written specification of several hundred requirements, and an automated gate checks the software against that specification on every change.
AEROE is a software platform that coordinates fleets of autonomous drones and robots from different makers as one fleet. It plans missions, checks every plan against what each vehicle has declared it can do, refuses anything the fleet cannot hold safely, supervises the flight, and keeps a verifiable record of everything that happened. It is developed by Noventis Pvt Ltd in Pune, India.
Any vehicle whose maker or integrator writes a connector against AEROE's published adapter interface and passes its conformance suite. The core of the platform never contains vehicle- or vendor-specific code, which is enforced by an automated check on every change, so mixed fleets from several makers are the normal case.
Each vehicle declares its limits: speed, altitude, endurance, radio delay, how precisely it can hold a position and how well its clock is synchronised. AEROE validates every mission against those declarations before take-off and refuses a plan the fleet cannot hold, stating the measured value, the limit and a value that would work.
Fourteen formation types, including circle, grid, line, wedge, echelon, arc, spiral, polygon perimeter, waypoint path, corridor sweep, flag, wordmark and traced image. Formations can stand upright in the sky, be joined into timed programmes with validated transitions, and be composed for a declared observer viewpoint.
Drone-show and event operators composing sequences for an audience; survey and inspection operators covering large areas; security, patrol and support operations in non-lethal roles; and vehicle makers or integrators who want their vehicles to be fleet-ready. Research programmes that need an inspectable coordination layer are also a fit.
Not yet. Every result published so far comes from AEROE's built-in kinematic simulator, which runs the same software the physical fleet will. A physical flight campaign on a reference vehicle is the next gate: a single vehicle first, then a small fleet.
No. AEROE installs on-site on an isolated network; the console reaches no external host, images are pinned and releases are reproducible with rollback. The optional AI model provider for plain-language mission authoring is the one declared exception, and the console says so on screen when it is configured.
Write to support@noventis.ai. Vehicle makers can integrate through the adapter interface and certify offline; operators can start in simulation with their own formations and site; research programmes can build on a platform with a written specification and traceable requirements.
Write a connector against the published interface, run the conformance suite, and ship with a certificate your customers can verify offline. Your vehicles become part of any AEROE fleet — alongside anyone else's.
Show, survey and security operators with mixed or growing fleets: one console, one plan, one record. Start in simulation with your real formations and site, then move to hardware when the trials clear.
For institutions and programmes that need a coordination layer they can inspect: a written specification, traceable requirements, deterministic evidence, and a core that provably contains no vendor code.