Get early access to Tarmac

The ops layer above your GCS — remote fleet telemetry, async control, and point-and-click custom payload integration for ArduPilot. Tell us about your setup and we'll bring you on as access opens.

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.