TarmacTarmac
Our story · Pan Robotics

From open-source airframes to a fleet you can actually run

Tarmac is built by Pan Robotics — robotics engineers and drone operators who got tired of running fleets through SSH sessions, scattered scripts, and a different tool for every task.

Tarmac didn't start as a product. It started as the hub software running on the Raspberry Pi companion computers of open-source ArduPilot aircraft — the on-board service that streamed telemetry, pulled logs, flashed firmware, and ran mission jobs while the aircraft was in the field.

As those airframes grew from a single quadcopter to heavy-lift hexacopters — and from one vehicle to small fleets — the hub had to grow with them: multi-vehicle, multi-operator, and reachable from anywhere, not just a laptop on the same network. Tarmac is that hub, rebuilt from the ground up for multi-tenant, production-grade use.

Built on open-hardware lineage

Tarmac cut its teeth on open-source ArduPilot aircraft. The companion services that fly on Quiver- and Caribou-class vehicles are the same lineage that powers the hub today — which is why Tarmac speaks ArduPilot natively and treats the companion computer as a first-class part of the stack.

Build in the open. Best idea wins.— the open-source ethos Tarmac inherits and carries into how the platform is built.

What makes Tarmac different

Companion-first

A Raspberry Pi companion is a first-class citizen, not an afterthought — telemetry, jobs, OTA and custom payloads all flow through it.

Natively ArduPilot

Built around ArduPilot from day one — MAVSDK telemetry, MAVFTP/HTTP log pull, firmware OTA and mission upload across fixed-wing, multirotor, VTOL and rover.

Multi-tenant by design

Role-based access control and per-org data isolation, so you can run separate client fleets cleanly from one place.

An app store for payloads

Write a Python parser, drag-and-drop a UI, and any custom sensor becomes a live dashboard widget — no backend to build.

Open standards, no lock-in

REST + WebSocket + SocketCAN/DroneCAN under the hood. The data is yours; the protocols are open.

Where we're headed

The hosted version of Tarmac exists so operators who'd rather not run their own infrastructure can get airborne in minutes — and so the work keeps funding the open tooling underneath it. The aircraft get more capable every release; the hub that flies them should too.

Get in touch

Sales, support, and everything else: info@panrobotics.xyz

Request early access