Beacon 5.0 and Beacon Studio 1.0: The Rebuild That Finally Connected Everything

Beacon 5.0 and Beacon Studio 1.0

8:55

It's 12:30 a.m. on a Friday and I'm writing this instead of sleeping, which is apparently just what Beacon does to me.

This started as a weekend experiment. A tiny Wi-Fi server. Wearable, sort of. Useful, maybe. I wanted to see what would happen if you could wear a Wi-Fi network the way you wear a name tag — except the name tag loads a webpage, and the webpage is you.

That was the origin. Ankle monitors, a real estate agent's jaw drop at a networking event, a food truck discovering it could broadcast its menu from a parking lot. A coach who said he wanted a Wi-Fi whiteboard for his youth team. Gen Z are Wi-Fi bloodhounds, he told me. He wasn't wrong.

A lot has happened since then.

Beacon 5.0 is shipping. Beacon Studio 1.0 — a native macOS application — is shipping alongside it. And for the first time since I started building this thing, the whole system makes sense as a system.

Let me explain what I mean by that.

Beacon has always been hard to explain if you reach for the wrong comparison. It's not a better NFC card. It's not a long-range QR code. NFC works from millimeters — someone physically taps it. A QR code works from a few feet — someone points a camera at something they can see.

Beacon works from 100, sometimes 200 feet. Someone notices a Wi-Fi network, connects, and a locally hosted profile loads. No internet. No app. No account.

The finished hardware can do all three. Rewritable NFC tag. Editable QR code. Wireless Beacon profile broadcasting from your pocket. Tap it. Scan it. Or let it find people from across the room before they ever walk up to you.

That's the third layer. That's what Beacon actually is. Every version has made the device more capable. 3.0 added NFC and a universal hardware platform. 4.0 introduced full .BCN backup files — a single portable package containing every profile, every image, every setting on a device. Flashing used to mean starting over. After 4.0, flashing was just a step. Flash. Restore. Done. I wrote that post at 3:15 a.m. too. There's a pattern here.

4.0 was the moment the device grew up. But there was still a gap.

I'd built a browser-based manager alongside 4.0. It could edit profiles, prepare images, generate QR codes. It worked. But it was becoming something it wasn't designed to be — a desktop application trapped inside a browser tab. Image processing was constrained. Local device communication was awkward. File handling was worse than it should have been. And it was adding cloud complexity to a device whose entire value proposition is that it operates locally, offline, without depending on anyone else's infrastructure.

So I stopped trying to make the website do everything. The website can be a website. It can explain Beacon, support the community, show examples, share profiles. Device management belongs somewhere else. That somewhere else is Beacon Studio.

Beacon Studio 1.0 is a native macOS application. No account required. No cloud layer between you and the device. No browser tabs, no uploads, no managing images on a four-inch mobile screen.

You open the application. You build the card. You connect to the Beacon. You deploy it. The left panel shows your connected device — or the lack of one, clearly, without drama. Four profiles listed below it, color-coded, keyboard shortcuts assigned. The center panel is the editor: content, images, appearance, device settings. The right panel is a live preview, switchable between phone and desktop layouts, showing exactly what someone will see when they connect.

That image processing piece matters more than it sounds in a spec sheet. An ESP32 doesn't have the storage headroom of a laptop. A photo from a modern phone can be several megabytes — larger than the practical budget for an entire Beacon profile. Studio preprocesses the image before it ever touches the device. Corrects orientation. Resizes. Reencodes when appropriate. Compresses. Shows you the resulting dimensions and file size before you commit. The Beacon receives an asset prepared for the hardware instead of struggling with something designed for a retina display.

The connection model is simpler now too. In Node Mode, a Beacon connected to a local network is reachable at beacon.local — a human-readable address instead of an IP you have to hunt down and remember. Studio looks for it there. It either finds it or it doesn't, and it tells you plainly either way.

5.0 also tightened something I'd been thinking about for a while: the boundary between using a Beacon and managing one.

In normal operation, the configuration is locked. Someone who connects to see your profile can see your profile. They cannot access configuration data, replace files, change credentials, or reprogram the device. To manage it, you press and hold the physical button. The light changes. Setup mode opens. You do your work. Long-press again to close it. Management endpoints lock.

That's it. No countdown timers. No pairing codes. No app authentication dance. It's a physical boundary that anyone can understand: hold the button to manage it, hold it again when you're done. I'm not trying to turn an ESP32 business card into a bank vault. I'm trying to make the security model legible without making it complicated.

The .BCN file is still the center of everything. It's a portable copy of a Beacon — all four profiles, their templates, colors, text, links, media paths, and associated image assets in a single package. Studio can import one from your Mac, import one directly from a URL, or export a new one from scratch. You can back up a device before changing it, edit it on a Mac, restore after a factory reset, clone a configuration onto a fleet of Beacons, build a profile before the hardware even arrives, or hand a complete Beacon design to someone else.

The file belongs to you. It lives on your computer, or your drive, or wherever you choose. No subscription. No account. No expiration.

There are two upgrade paths now for existing devices. Safe upgrade installs 5.0 without touching the user-data partition — existing profiles, credentials, and settings stay exactly where they are. Factory installation is the full wipe: bootloader, partition table, application firmware, local filesystem, everything. For new hardware, device recovery, or intentionally starting fresh. Make a .BCN backup first if you can.

The last piece I want to name is OpenProfile, because the relationship finally makes structural sense.

OpenProfile is the web-based side of the same idea — a digital identity with a link, a QR code, and an NFC destination you can update without replacing anything physical. It's been part of what I've been building since 2024. Beacon extends that into physical space. OpenProfile works when someone taps or scans. Beacon works when someone notices a signal from across the room.

Beacon Studio 1.0 doesn't integrate OpenProfile. There's no account requirement, no forced cloud sync, no profile import from the platform. The first release is focused on doing the local workflow well, and doing it completely, before adding anything else. But the product structure is finally clear. OpenProfile is the online identity and destination. Beacon is the local wireless extension. Beacon Studio is the tool for managing the hardware. I was missing that framing for a long time. Now I have it.

Version 4.0 made the device portable. Version 5.0 makes the system coherent.

There's a firmware, a file format, a native application, and a clear relationship between the hardware, the software, and the broader ecosystem it fits into. That's not where I thought I was headed when I was hot-gluing an OLED to a dev board and wondering if the thermals were going to be a problem. But here we are.

Beacon 5.0 is ready. Beacon Studio 1.0 is ready for macOS. The experiment that refused to stay a hobby is starting to look like an actual product.

Let's build something worth broadcasting.

---

Rich Washburn is a technologist and strategist working at the intersection of AI, infrastructure, and capital. He is Managing Partner and Chief AI Officer at Eliakim Capital and CIO of Data Power Supply.