On your network

RotorLab TAK Fleet Server

One annual licence per server — add crews without adding licences

One server on your own network that speaks MAVLink to your aircraft and ground stations, publishes the whole fleet to ATAK, and records what happened. Switch on Fleet Server Cloud and it files every flight to RotorLab too.

Request a quote Read the full description

The Fleet Server dashboard: TAK connected, and an airframes table listing HAWK-1 and HAWK-2 via Ridge 1 alongside TALON-1 and ROVER-1 via Ridge 2, each with position, altitude, mode, armed state, battery and satellites. — Two crews, four vehicles, one server. Each aircraft carries its crew's address — **R1-1**, **R2-2** — which is what an ATAK operator types to command it. When two crews fly the same SysID the server says so and refuses to guess.

What it does

The whole fleet on TAK

Every airframe published as a MIL-STD-2525 track — position, heading and the sensor footprint on the ground. Your crews get their own markers too, so the map shows who is where.

Command by ATAK

An approved operator tasks an aircraft by dropping a marker on the map. The ground station decides whether to carry it out — nothing here ever touches an autopilot directly.

Ground stations enroll

A station joins with a code somebody types once, then dials out over TLS. No inbound ports, works across NAT, and any station can be revoked instantly by name.

It is the buffer

A ground station hands over a finished flight and is done. Whether RotorLab is reachable is the server's problem, never the pilot's and never the aircraft's — a durable outbox replays everything when the link returns.

Every run is recorded

Each session is written to an append-only, hash-chained record. Replay the fleet picture at any moment of a call, and re-verify that the recording has not been altered since.

It is the cache

Roster, registry and checklists are pulled from RotorLab and served from the local copy, so a crew picking a pilot and an aircraft never waits on an internet round trip. Stale but present beats absent.

It holds the only key

The one credential lives here, on a server in your building. Nothing downstream — not a ground station, not a vehicle, not the aircraft — carries anything that opens your RotorLab account.

A table of recognized airframes keyed by autopilot hardware UID, each with callsign, tail number, flight count, accumulated hours, and first and last seen dates. — Aircraft are recognized by their autopilot's hardware UID, not by a callsign somebody typed — which is what makes HAWK-1 on one station on Tuesday the same airframe as HAWK-1 on another on Wednesday. Rows appear on their own as flights are filed, and the hours are real flown time.

An OpenTAKServer map showing six live tracks over a city: RIDGE1-UAS1, RIDGE1-UAS2, HAWK-1, HAWK-2, TALON-1 and ROVER-1, each labelled with its crew address. — And the same fleet on the map your team already has open. Standard Cursor-on-Target — here on OpenTAKServer, and identical in ATAK.

Fleet Server Cloud

Not a product and nothing to buy. It is a menu item inside Fleet Server: paste a RotorLab Device Key and the connection to RotorLab switches on.

✓It needs both sides. A licensed Fleet Server and a RotorLab.app subscription linked to it. Neither alone does anything.
✓No extra cost. There is nothing to add to a basket. It is a feature of the Fleet Server you already licensed.
✓One credential, one place. The device key is minted by your own org admin in RotorLab and lives only on the server. It is scoped so it can file flights but cannot spend your analysis credits.
✓Revocable in seconds. Retire the device in RotorLab and the connection stops. The Fleet Server keeps flying, recording and publishing to ATAK regardless.
✓Runs where the callout is. On a laptop at the scene or in Docker in a rack — and it keeps working with no internet at all.
✓Turn it off and nothing breaks. Without a key the Fleet Server is a complete TAK fleet server; the RotorLab half is simply not switched on.

The Fleet Connector screen in RotorLab GC: status Connected to a Fleet Server, publishing to ATAK, with the crew callsign and crew code shown. — A ground station with the Fleet Server connected. One route to ATAK, one crew callsign, and a crew code an ATAK operator can address.

The Who is flying dialog on a ground station, listing pilots from the RotorLab roster with currency lapsed and currency due soon warnings beside two of them. — Your RotorLab roster, at the launch point — currency warnings and all. The crew can still skip it and fly; the flight is logged either way.

What it will never do

✓It cannot stop a flight. Not a lapsed certificate, not a revoked key, not an unreachable RotorLab. Everything it reports is information; if any of it ever blocked a launch that would be a defect.
✓It never touches an autopilot. A Command-By-ATAK order is handed to the ground station, which decides what to do with it. There is no path from the map to your flight controller.
✓It does not send RotorLab your telemetry. Only the record of a flight that has ended — once, after the fact — plus its log if you want it kept.

The product licence screen: a licence key field with Activate, Verify and Deactivate, and a note that a licence problem never stops the server working. — Activate binds a key to a machine; Deactivate frees the slot for another one. The licence is re-checked with a 72 hour offline grace window — and a licence problem never stops the server working, at start-up or mid-incident. (Key obscured here.)

Licence keys are issued through the shop rather than this site's checkout. Tell us what you fly and we will size it with you — request a quote.

RotorLab.app RotorLab GC Fleet Server MAVLink/ATAK Bridge Request a quote