I spend a lot of time talking to people who are excited about System-on-a-Chip devices — Raspberry Pi boards, NVIDIA Jetson modules, Orange Pi, Radxa Rock, and dozens of others — but who run into an immediate wall the moment they try to actually set one up. That wall is called "headless setup," and for most people it is where the excitement starts to drain away.
The problem is not that these devices are complicated. It is that the traditional setup process assumes you have a spare keyboard, a spare monitor, a USB adapter, the patience to edit config files on the SD card before first boot, and enough knowledge of network configuration to get SSH working before you can do anything useful. That is a lot of prerequisites for what should be a five-minute job.
awaBerry Connect eliminates all of it.
How Bespoke Installer Works
Instead of downloading a generic OS image, burning it to a card, and then fighting with configuration files, awaBerry gives you a Bespoke Installer — a custom-built OS image generated specifically for your hardware and pre-configured for your awaBerry account. Here is the entire setup process:
- Go to the Connect New Devices section of your awaBerry dashboard and select your device type — we support a comprehensive library of popular SoC boards.
- Configure your build options (architecture, base OS version, any additional packages you need).
- Monitor the build job in real time — pending, in progress, ready to download.
- Download your custom installer along with your secure device licence, and follow the built-in guide to flash it to an SD card or USB stick.
- Insert the media, power on the device — and it appears in your dashboard, ready to use.
That is genuinely all. No keyboard. No monitor. No SSH key exchange. No network configuration. No firewall rules. The device establishes an outbound HTTPS connection to awaBerry's infrastructure the moment it boots — zero inbound exposure, zero configuration required on your router.
Already Running a Device? Add It in Minutes.
If you already have a machine running — a Windows desktop, a Mac, or an existing Linux server — you do not need to reinstall anything. The Add Existing Device flow walks you through a single-click initialisation from the dashboard that registers your device in minutes without creating new media or touching your network configuration. It is the fastest path onto the platform for devices that are already up and running.
There is also a Docker Deployment path for teams already running containerised environments — ideal for NAS devices or any existing infrastructure stack where you want to avoid host OS modifications.
What Comes After Setup: Remote Desktop and Web-to-Local
Getting a device online is only the beginning. Once your device is registered in awaBerry, the full remote access layer unlocks — and two features in particular have changed the way our customers work.
Remote Desktop (VNC and RDP) gives you pixel-perfect graphical control over your device from anywhere, with no VPN and no open ports. Whether you are running a Windows machine, a Mac, or a Linux desktop environment on your SoC, you can see and control the screen directly from your browser — or from a native client like Apple Screen Sharing or Microsoft Remote Desktop for the lowest possible latency.
Web-to-Local is the feature I get the most excited reactions about in demos. It lets you securely reach any application running locally on your remote device — a database admin interface, a development server, a Jupyter notebook, a custom web application — directly in your browser, over an encrypted zero-trust tunnel, without exposing a single port to the internet. If it runs on localhost on the device, you can reach it from anywhere with Web-to-Local.
Together, Remote Desktop and Web-to-Local mean that once a device is in your awaBerry account, you essentially have a full remote working environment. The device's screen, its terminal, its file system, and all of its locally running applications are available to you wherever you are.
Who This Is For
I have seen awaBerry Connect used by a remarkable range of people. Twelve-year-old Leo using it to set up his first SoC board and start programming motors and lights in Python — without needing to borrow his parents' monitor. University researchers deploying headless compute nodes in lab environments without IT involvement. DevOps teams onboarding embedded devices in manufacturing facilities at scale. And remote workers giving themselves seamless access to their office machines from a hotel room, using Remote Desktop via awaBerry as comfortably as if they were sitting in front of the screen.
The common thread is this: awaBerry removes the technical barriers to entry that have always made device setup more painful than it needed to be.
If you want to see it in action, start with the video above — then head to the awaBerry Connect product page for a full technical walkthrough, or try it free today.
