THE BACKGROUND

A different kind of builder

Most ham radio dashboards are built by hams, for hams — which is exactly why they look and behave the way they do. Helioclock started somewhere else: with a background in broadcast meteorology and broadcast systems design, not just amateur radio experience.

That background shows up in places a typical “ham clock” wouldn’t go. A live GOES satellite cloud overlay, animated in the same layered pattern used in broadcast weather graphics. Live Weather Radar at four selectable animation speeds. A base map that actually changes month to month — real seasonal Blue Marble imagery, not a static tile. Live lightning strike data pulled from the same GOES GLM sensor networks broadcast meteorologists rely on. Volcanic ash and eruption tracking sourced from VAAC, USGS, and individual national volcano observatories queried and aggregated directly, worldwide. Wildfire detection straight from NASA FIRMS. Tropical cyclone tracking. Sea surface temperature and anomaly maps. NWS alerts, integrated the way a broadcast station’s severe weather system would handle them — not bolted on as an afterthought.

None of that is standard ham radio dashboard territory. It’s standard broadcast weather systems territory, applied to a shack display for the first time. That’s not a coincidence — it’s the whole reason Helioclock exists in the form it does.

THE APPROACH

Built differently, on purpose

Helioclock is also built differently than either of the free tools it gets compared to. Most importantly, it uses the tremendously flexible HTML5 for its display. Paired with modern CSS, HTML5 layouts seamlessly adapt their shape, size, and order to fit any screen — from mobile phones to ultra-wide desktop monitors to big-screen 4K TVs.

The original HamClock was one person’s hand-written C++, compiled to a handful of fixed screen resolutions, developed over years. OpenHamClock is a genuinely excellent modern rebuild — but it’s built the traditional open-source way: dozens of contributors, each submitting their own panel or plugin, reviewed and merged over time. That’s a real strength for breadth, and a real limit on coherence — a dockable layout assembled from many people’s individual contributions inevitably feels like what it is.

Helioclock is a single, continuous vision, built end-to-end by one person working in tight iteration with modern AI development tools — not as a gimmick, but as how a solo builder can now move at a pace and cohesion that used to require either a decade of nights and weekends, or a thirty-person volunteer team. That’s why every part of Helioclock — the Mini Panel / Detail Panel system, the Carousel Mode, the color palette, the alert design — follows the same design language throughout, instead of feeling like a patchwork of separately-built pieces. It’s also why the feature set is unusually broad for a product this young: Best Band Now’s full prediction-versus-confirmation logic, an entire broadcast-grade meteorology layer, Dst/DRAP space weather depth, and a next-generation 4K visual design, all shipped and refined in months, with a public, dated build log to show the actual work behind that pace — not just a claim about it.

THE PITCH

The pitch

Helioclock isn’t “the AI one.” It’s the one where a single person’s broadcast-systems background, paired with tools that let one person build like a team, produced something neither a lone hobbyist working alone nor a large volunteer project working by committee was likely to build: a coherent, next-generation shack display with a weather-graphics depth no ham radio dashboard has had before.

Since Helioclock is highly configurable, it can shed its ham roots just as easily and work for EOCs, NOCs, boardrooms, corporate lobbies, or any place a world situational-awareness display is needed. And there’s no setup — it’s truly plug-and-play. Whether you choose a preloaded SD card for the Raspberry Pi 4/5, our live USB stick, or one of our ready-to-run hardware appliances, you can be certain it will run.

Helioclock — it just works.

— KA9NWM