Installation
Aithernet is invitation-only. Packages are delivered through the authenticated portal after your access request is approved — this public site hosts no binaries, keys or credentials.
The customer sequence
- Request access by emailing adityapawar@aithernet.online. Self-service signup is not available during early access.
- Get approved — an administrator reviews the request and sends a one-time invitation email.
- Create your account from the invitation link and sign in to the portal.
- Download the signed release (Debian package, plus wheel/sdist) from the portal's Downloads page.
- Verify the release: check the detached signature over the manifest with the published verification key, then verify each artifact checksum.
- Install the package and run setup.
Verify & install (Ubuntu 24.04 amd64)
After downloading the release directory (manifest, signature, checksums, package and the public key) from the portal:
# 1) verify the signed manifest, then the artifact checksums
openssl pkeyutl -verify -pubin -inkey aithernet-release.pub \
-rawin -in manifest.json -sigfile manifest.sig
sha256sum -c SHA256SUMS
# 2) install the node package
sudo apt install ./aithernet_<version>_amd64.deb
# 3) the documented CLI is now on PATH
aithernet --help
Set up, enroll and start
# prepare state + node identity
aithernet setup --node-name "my-sdr-node"
# install a hardware profile of SIGNED distribution packages (no source build)
sudo aithernet hardware install --profile pluto
aithernet hardware doctor # read-only readiness + remediation
# enroll to the hosted control plane with a one-time code from the portal
aithernet enroll --base-url https://app.aithernet.online/api --code <ENROLLMENT_CODE>
# enable and start the service, then check status
sudo systemctl enable --now aithernet-node
aithernet hosted status
aithernet hosted heartbeat
The RF backend is a pinned, signed GNU Radio MCP component installed into a
managed location — never a developer checkout. See
RF component & source notices.
Receive-first & permissions
- The node is receive-first; transmission is disabled by default.
- Non-root SDR access uses udev + the
plugdev/dialoutgroups; the installer configures these. - The node makes only outbound connections to the control plane. It opens no inbound ports and never exposes its local API to the Internet.
Exact versioned commands and the verification key are provided with your release
in the portal. Commands on this page show <version> as a stand-in you replace
with your actual release version.