Skip to main content
Trust CenterStatusDocsDevelopersEventsContact salesSign in
On your network

RotorLab TAK Fleet Server

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.

Contact sales → Request a quote

One annual license per server: add crews without adding licenses. Read the full description.

MAVLink HTTPS, enrolled CoT, live Fleet Server Cloud Your aircraft Ground stations Fleet Server on your network ATAK RotorLab.app

What it does

Every crew's station reports into one hub, and the hub holds the only key.

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: 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, and it holds the only key

Roster, registry and checklists are served from the local copy, so a crew never waits on an internet round trip. The one credential lives here, on a server in your building.

The shipping build, running

Real screenshots of the product against live aircraft: no mockups, and no on-screen value edited.

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 serverEach 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.
An OpenTAKServer map showing six live tracks over a city: RIDGE1-UAS1, RIDGE1-UAS2, HAWK-1, HAWK-2, TALON-1 and ROVER-1, each labeled with its crew address.
The same fleet on the map your team already has openStandard Cursor-on-Target: here on OpenTAKServer, and identical in ATAK.
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 recognized by hardware UIDNot by a callsign somebody typed: HAWK-1 on one station on Tuesday is the same airframe as HAWK-1 on another on Wednesday. Rows appear as flights are filed, and the hours are real flown time.
The product license screen: a license key field with Activate, Verify, and Deactivate, and a note that a license problem never stops the server working.
Licensing that never stops the serverActivate binds a key to a machine; Deactivate frees the slot. The license is re-checked with a 72 hour offline grace window, and a license problem never stops the server working, at start-up or mid-incident.

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.

FLEET SERVER CLOUD rl_895bEDCo… RotorLab Device Key ✓ Roster and registry sync ✓ Flight filing, keyed so a retry never duplicates ✓ Checklist completions against those flights ✓ The log file, kept with the flight
The Fleet Server Cloud screen: connected to RotorLab.app, showing the device key by prefix only, the scopes it holds, the RotorLab version and when the registry and roster last synced.
The menu item itselfThe key is shown by prefix only, its scopes are named, and the first line under the title is the rule the whole product is built on: nothing here can prevent a flight.
  • It needs both sides. A licensed Fleet Server and a RotorLab.app subscription linked to it. Neither alone does anything.
  • No extra cost. 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, 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.

Seen from the crew's end

What a ground station shows once a Fleet Server is connected. Both are real screenshots of the shipping build.

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 connectedOne 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 pointCurrency warnings and all. The crew can still skip it and fly; the flight is logged either way.

What it will never do

Everything it reports is information. If any of it ever blocked a launch, that would be a defect.

It cannot stop a flight.

Not a lapsed certificate, not a revoked key, not an unreachable RotorLab.

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.

LicensingOne annual license per server. Add crews, stations and aircraft without adding licenses. Keys are issued through the shop rather than this site's checkout.
Runs onA laptop at the scene or Docker in a rack. Works with no internet at all; the RotorLab connection is optional.
Goes withRotorLab GC on every crew's station, or any MAVLink ground station. One station and no mutual aid? The MAVLink/ATAK Bridge is the smaller product.

Tell us what you fly and we will size it with you.

Crews, stations, aircraft and whether the server lives at the scene or in a rack.

Contact sales →Request a quote