Skip to content
HXES — Heytronix Ecosystem
Journal

Naming

Why HXES — eight letters, ten pillars

The story behind the ecosystem name, and why ten pillars beat one monolith.

2 min read

When you're building software for the long term, names carry weight. Acronyms especially — they travel on business cards, in procurement documents, in API endpoints. Getting one wrong is expensive to fix.

We deliberated on this longer than most people would expect for eight letters.

What we needed the name to do

The Heytronix product portfolio was always going to be more than one thing. Early on we knew we were building operations software (eQuinox), and we knew that wouldn't be the last product. We needed a container — a brand envelope — that could hold ten distinct products without becoming meaningless.

Three criteria drove the decision:

  • Short. Four to six characters, ideally pronounceable. Long acronyms get mangled in conversation.
  • Expandable. The name had to work whether we shipped two pillars or ten.
  • Owned. No collision with existing trademarks in our category.

Why not "HxOS"

We used HxOS in early internal docs. It felt right for a while — the OS suffix implied an operating system metaphor, which matched how we thought about the platform.

But it created a positioning problem. "OS" implies you replace the existing infrastructure. We don't. We sit alongside it, connect it, and make it legible. Calling ourselves an operating system was technically inaccurate and strategically overreaching.

We retired the name internally and ensured it doesn't appear in any customer-facing surface.

HXES — Heytronix Ecosystem

HXES is short for Heytronix Ecosystem. It works because:

  1. It doesn't overclaim. An ecosystem implies a set of connected parts, not a monolith.
  2. It namespaces well. Every pillar gets an HX- prefix: HX-Ops (eQuinox), HX-Learn, HX-Connect and so on.
  3. It's memorable in conversation. Two syllables. "hex" rhymes.

Ten pillars, one standard

The ten HXES pillars aren't arbitrary. Each maps to a distinct operational domain — from asset management and field operations through to learning, analytics and integrations. They share:

  • A common design language (same component library, same token system).
  • A shared authentication layer.
  • A shared data model for assets, locations and personnel.
  • A unified licensing agreement.

You can deploy one pillar. You can deploy ten. The HXES label tells your team they're part of the same engineering standard regardless.

That's the job the name needed to do. We think it does it.