Available worldwide · fresh installs and updates. Compatible ARM64 Linux with APT/dpkg, systemd and resolvable dependencies. Tested Pi models are examples, not an installation allowlist. Receiver 0.1.0-63 requirements and downloads.

Receiver software

Layer400 for
ARM64 Linux

Put your Pi to work listening for drones and aircraft.
Start here, then finish setup in your browser.

ComputerCompatible Raspberry Pi or ARM64 Linux computer

Operating systemARM64 Linux APT/dpkg + systemd

ConnectionInternet access Set up on your local network

Install Layer400

Open Terminal on your Pi. Paste this command and press Enter.

On your Raspberry Pi

curl -fsSL https://layer400.com/install | sudo bash

Leave the terminal open while it installs. You’ll see progress updates along the way.

Connecting from a laptop?

Open Terminal on macOS or Linux, or PowerShell on Windows. Connect to your Pi first:

ssh YOUR_PI_USER@YOUR_PI_ADDRESS

Use your Pi’s username and hostname or IP address. Check the SSH fingerprint belongs to your Pi before accepting a first connection. Then run the installer command above.

If asked for your Pi password, type it and press Enter. No characters appear as you type; that’s normal.

When it’s finished

Open the address printed in the terminal.

Use a browser on the same network as your Pi. Its welcome page takes you to Layer400 to sign in, choose your receiver’s location and download a setup file. Upload that file to your Pi to connect it.

Already installed? Connect your receiver

If your browser shows a certificate warning

Your Pi uses a device-local certificate. Check the address matches the installer’s output and belongs to your Pi before continuing, and use a trusted local network. To print the address again, run sudo layer400 setup on the Pi.

Free for personal use. Software terms and privacy apply when you install and connect.

A quick check before you start

You can start on a desk. The radio and antenna you connect determine what your Pi can hear.

Drone Remote ID: A compatible monitor-mode Wi-Fi adapter or Bluetooth controller.
Aircraft / ADS-B: A compatible SDR, or an existing local decoder feed.

Already running a receiver? Layer400 can share supported feeds without taking over the other software’s radios.

Check hardware compatibility

Storage & support limits

The installer checks actual download and package space requirements, available storage, required system capabilities and signed files. Keep additional room for saved observations.

This public ARM64 package is available to everyone. It can install on compatible Raspberry Pi models and other ARM64 Linux systems with APT/dpkg, systemd and resolvable dependencies. Board names and distribution labels do not restrict public installation. This build is not for Windows, macOS, x86 or 32-bit systems.

Radio support depends on the driver, firmware and permitted channels. Shared listening follows the existing scanner’s channel and PHY coverage. A detected Bluetooth controller alone does not prove Remote ID reception; see the test notes below.

Prefer to download the installer?

The one-line installer above is the simplest option. If you prefer the archive, download it here and transfer it to your Pi.

Download version 0.1.0-63 for Raspberry Pi

On the Pi, open a terminal in the folder containing the download. Check the archive before extracting it:

printf '%s  %s\n' '5a7704045ccdaa8b24d915999f50c28e996b306dee5dd782e565c8f23e940a74' 'layer400-receiver-0.1.0-63-arm64.tar.gz' | sha256sum -c - &&
layer400_dir=$(mktemp -d) &&
tar -xzf 'layer400-receiver-0.1.0-63-arm64.tar.gz' -C "$layer400_dir" &&
bash "$layer400_dir/install-signed-receiver-release.sh" --bundle "$layer400_dir" --expected-version 0.1.0-63 --public-key-spki-sha256 35a1d41a912ca8281c758c4824eb1e679319124f4e93ec14661f265be50914ac --verify-only

Run these commands in order. Stop if the checksum is not OK or verification fails. After the script reports SIGNATURE VERIFIED, install from the same terminal:

sudo bash "$layer400_dir/install-signed-receiver-release.sh" --bundle "$layer400_dir" --expected-version 0.1.0-63 --public-key-spki-sha256 35a1d41a912ca8281c758c4824eb1e679319124f4e93ec14661f265be50914ac

This requires a compatible ARM64 Linux host with APT/dpkg, systemd and internet access for system packages. The archive is not a disk image. Keep its contents together; don’t install the enclosed package on its own.

Next: connect it to your account →

Release files and checksums

Version 0.1.0-63 · 194,162,626 bytes

Archive SHA-256:

5a7704045ccdaa8b24d915999f50c28e996b306dee5dd782e565c8f23e940a74

The installer checks this checksum and the release signature before installation.

Already running Layer400?

Open Updates & rollback on your receiver and choose Check for updates.

Automatic updates are on by default. With the standard schedule, eligible updates install within two days while the receiver is online and ready, between midnight and 3am local time. You can change the schedule or install sooner.

Your receiver’s identity, location and settings stay in place.

Help with updates and recovery

Need an update file?

Download it here, then upload it on your receiver’s Updates page.

Download update

0.1.0-63 · .layer400update

How to upload it

On the same local network, open your receiver’s Updates page. Under Have an update file?, select the .layer400update file, then Upload and verify. Once compatibility checks pass, choose Install update.

Wait for it to finish before closing or restarting the receiver. Use the update file here, not the .tar.gz installer archive.

Updating from an older release

Use the signed installer command for a supported older installation. Legacy update clients can instead install the matching immutable .39 bootstrap below, then check for .57 on the normal all-platform update channel. From .39 onward, use the main offline update file or online updates. Choose by installed OS, not Pi model.

Full version compatibility

Receiver 0.1.0-63 uses one signed update for compatible ARM64 Linux systems worldwide. Tested Pi and OS examples are not eligibility restrictions. Layer400 can listen alongside an existing Wi-Fi monitor and active Bluetooth scanner without changing their channels, radio settings or services. Shared reception follows that scanner’s channel and PHY coverage. Compatible drivers, power and connectivity are still required. Windows, macOS, x86 and 32-bit systems are not supported by this package.

For compatible ARM64 Linux systems worldwide with APT/dpkg, systemd and resolvable dependencies; tested Pi models and OS versions are qualification examples, not an allowlist. Older clients need the matching bootstrap in the older-release notes. This update accepts installed versions 0.1.0-39 or 0.1.0-46 or 0.1.0-47 or 0.1.0-48 or 0.1.0-49 or 0.1.0-51 or 0.1.0-52 or 0.1.0-53 or 0.1.0-54 or 0.1.0-55 or 0.1.0-56 or 0.1.0-57 or 0.1.0-58 or 0.1.0-59 or 0.1.0-60 or 0.1.0-61 or 0.1.0-62. Version 0.1.0-63 is an automatic stable release. Automatic updates are on by default, with a two-day cadence and a staggered midnight–3am local maintenance window when online and ready. You can change the schedule or install sooner on the receiver’s Updates page. If your version is not listed, contact the team before updating.

Need a hand?

The Pi guide covers setup and day-to-day use. If something isn’t right, start with troubleshooting or get in touch.

Previous releases & recovery

Live radar and receiver reliability 0.1.0-63

Full-screen radar, regional units, continuous display and individual SDR assignments for 978 MHz UAT or 1090 MHz, alongside Wi-Fi and Bluetooth Remote ID.

Testing and offline operation

Exact signed upgrades passed on Pi4 and Pi5 with identity, settings, queues and FR24 preserved. Native ARM64 Debian 12/13 installation and recovery passed. Pi5 1090 MHz reception verified; live 978 MHz and two-radio RF testing remain pending.

Local radar works offline with a coordinate grid. Uncached street maps require internet. Reception depends on supported hardware and nearby transmissions; 978 MHz does not cover every drone. SENSE and central fault notices remain unreleased.

Compatible ARM64 Linux requires APT/dpkg, systemd and resolvable dependencies. Tested boards are evidence, not an installation allowlist.