ALPON X5 AI OS
ALPON X5 AI OS
ALPON X5 AI ships with a pre-installed, Sixfab-maintained Linux image tuned for the Raspberry Pi CM5 and the DEEPX DX-M1 AI accelerator. This page covers what's included in the OS, how to access the device on first boot, and how to keep it up to date.
The ALPON X5 AI runs ALPON OS, a Sixfab-customized 64-bit Linux distribution based on Raspberry Pi OS (Debian). The image is pre-installed at the factory and includes the DEEPX DX-M1 runtime, Docker, the Sixfab Connect agent for remote management, and cellular/Wi-Fi connectivity drivers. The OS is optimized for the CM5 compute module and runs on the arm64 architecture.
Overview
ALPON OS is a minimal, hardened Debian-based image maintained by Sixfab. It is built on top of the Raspberry Pi OS base so that the familiar apt package manager, Docker tooling, and the broader Raspberry Pi ecosystem work out of the box on this edge AI computer.
Base Image
ALPON OS — Debian (arm64) · CM5Customized by Sixfab for the Raspberry Pi CM5 compute module. Shipped pre-installed with the Sixfab Connect agent, DEEPX runtime, Docker, and cellular connectivity stack.
What's pre-installed
The image is ready to boot and register with ALPON Cloud without additional setup. Key components already on the device:
dxrt)
Docker & Docker Compose
ModemManager & NetworkManager
OpenSSH server
mDNS / Avahi
Hardware watchdog
Uninstalling the pre-installed Sixfab Connect agent, the DEEPX runtime, or the alpon system user will break remote management, AI inference, and OTA updates. You can freely install and remove your own applications; Sixfab cannot guarantee stability if its own components are removed.
Architecture
The ALPON X5 AI runs on a 64-bit ARM architecture (arm64 / aarch64). All custom binaries, containers, and third-party packages must be compiled for or compatible with arm64. x86 / amd64 binaries are not supported.
Use multi-arch images or pin the platform explicitly: docker pull --platform linux/arm64 <image>. Most official images on Docker Hub publish arm64 variants.
First boot & setup
The device is ready to use the moment it's powered on. On first boot it will bring up networking, register with Sixfab Connect (if provisioned), and start the DEEPX runtime. From there, you set up user access so you can log in for day-to-day administration.
Default credentials
Every ALPON X5 AI ships with a factory-configured system user. Use these credentials for initial login only — you must change them before deploying to production.
Default Username
alponDefault Password
sixfabThe default alpon / sixfab credentials are shared across all ALPON X5 AI devices. Change the password or create a new admin user before connecting the device to any untrusted network.
alpon userThe alpon account is used internally by Sixfab Connect and other system services. Change its password, but keep the account. If your security policy requires a separate admin identity, create a new user (see Step 4) and keep alpon intact.
Device hostname
Each ALPON X5 AI has a unique hostname derived from its primary MAC address, in the format:
The MAC address is printed on the device label. This ensures multiple ALPON devices on the same network never conflict, and it lets you reach the device over mDNS as alpon-<MAC>.local without knowing its IP.
Set up user access
Provision the device in Sixfab Connect
Before you can reach the device remotely, it must be registered to your Sixfab Connect organization. If you haven't done this yet, complete the Quick Start first.
Open a shell on the device
You have two ways to get a shell. The remote terminal is the fastest on first boot because it works from any browser and doesn't require the device to be on your local network.
- Remote terminal (recommended for first access): log in to Sixfab Connect, open your device, and click Terminal.
- SSH over LAN: if the device is on the same network as your computer, connect via mDNS (see Step 5).
- HDMI + keyboard: attach a display and keyboard directly to the device (see Step 6).
Secure the default alpon user
Immediately change the default password. Do not delete the account.
passwd alpon
Enter the current password (sixfab), then your new password twice.
Create a new admin user Recommended
For production use, create a dedicated admin account alongside the alpon service user.
sudo adduser <username>
Set a password when prompted, then grant passwordless sudo:
echo "<username> ALL=(ALL) NOPASSWD: ALL" | sudo tee /etc/sudoers.d/<username>
Replace <username> with your chosen name. For example, for a user named ops:
sudo adduser ops echo "ops ALL=(ALL) NOPASSWD: ALL" | sudo tee /etc/sudoers.d/ops
Connect via SSH
Once your user exists, connect from any machine on the same network using mDNS:
ssh <username>@alpon-<MAC>.local
Example — user ops, device hostname alpon-2ccf67319374:
ssh [email protected]
alpon for the default.alpon-<MAC>.local (MAC printed on device label)22 (default SSH)The .local suffix uses mDNS (Bonjour / Avahi). If your network blocks mDNS, use the IP address directly: ssh ops@<IP_ADDRESS>. You can find the device IP on the Sixfab Connect device page.
Connect a local display Optional
Plug an HDMI display and USB keyboard into the ALPON X5 AI to log in locally. The HDMI 2.0 port supports up to 4Kp60 output. Connect the display before powering the device on.
System updates
ALPON OS uses standard Debian package tooling. Apply security patches and upgrades with apt, and manage deployed applications separately through Docker or the ALPON Cloud fleet update flow.
How do I update ALPON OS?
From a shell on the device, run the standard Debian update cycle:
- Refresh the package index with
sudo apt update. - Apply available upgrades with
sudo apt upgrade -y. - Reboot if a kernel or firmware package was upgraded.
# 1. Refresh package lists sudo apt update # 2. Apply available upgrades sudo apt upgrade -y # 3. Reboot if the kernel or firmware was updated sudo reboot
When updating a fleet, stagger the rollout. Reboot one device, confirm it comes back online in Sixfab Connect, and only then proceed to the next. This protects you from regressions in upstream packages.
How do I update deployed applications?
Application updates are separate from OS updates. Use the method that matches how the app was deployed:
- Containers deployed through ALPON Cloud: push a new image tag from the Manage & Deploy Applications dashboard. Sixfab Connect orchestrates the pull, restart, and rollback.
- Manually-run containers:
docker pull <image>:<tag>on the device, then recreate the container withdocker compose up -dordocker run. - System packages:
sudo apt install --only-upgrade <package>.
Firmware and modem updates
Modem firmware, the DEEPX runtime, and the Sixfab Connect agent are delivered through the normal apt channel and, where applicable, through Sixfab Connect OTA. You don't need to manage them manually. When a Sixfab-maintained package is updated, apt upgrade will pull it in.
Avoid apt autoremove unless you know exactly what it's about to remove. If it lists sixfab-*, dxrt, or modemmanager as removable, cancel the operation. Removing those packages will disconnect the device from ALPON Cloud and break AI inference.
OS image & re-flashing
The ALPON OS image is pre-installed at the factory on every ALPON X5 AI and is not distributed as a public download. Shipping the OS on the device avoids the edge cases and hardware-specific quirks that come with end-user flashing of industrial edge AI computer images.
If your device is in a state where you believe the OS needs to be re-flashed — for example, it won't boot after a failed upgrade, or it has been misconfigured beyond recovery — contact Sixfab support. We'll confirm whether a re-flash is actually needed and walk you through the recovery path that matches your device's serial.
Need to recover the OS? Contact Sixfab support.
Have your device serial number ready. Support will verify the fault and provide the recovery procedure.
Many "broken OS" symptoms are actually recoverable over a working shell session:
- Use the Sixfab Connect remote terminal — it works even if LAN/SSH are misconfigured, as long as the cellular link is alive.
- If a recent upgrade broke something, check
journalctl -xeandsudo apt install --reinstall <package>. - For Docker-related failures:
sudo systemctl restart docker.
Updated about 8 hours ago
