Helios

Origin

Helios is HashiCorp's design system for the cloud-infrastructure product portfolio — Terraform, Vault, Consul, Nomad, Boundary. It crystallized publicly around 2022 after years of internal use, codifying patterns that appeared across HashiCorp's growing product surface.

Governance

Centralized design-systems team owns Helios; product teams contribute through a public RFC process documented on the Helios docs site. Components ship as Ember Octane add-ons today, with React versions in development. Strong release-note discipline and explicit deprecation paths.

Known for

• Operational density — the system is built for surfaces where users monitor, configure, and recover from real infrastructure problems.
• Documentation rigor — every component lists accessibility expectations, content guidelines, and integration patterns, not just visual specs.
• First-class dark mode — the canonical surface for infrastructure tooling is the dark variant, treated as primary not afterthought.

Underrated

• The form patterns include real treatments for long-running operations: progressive disclosure, async validation, partial-save recovery — the kind of forms infra UI demands.
• Color tokens are HashiCorp-product-aware: each product family (Terraform purple, Vault yellow, Consul magenta) ships as a documented sub-theme, not a fork.

Watch out for

• Heavy on Ember-specific ergonomics today; React adopters need to track the parallel implementation roadmap.
• Patterns assume infrastructure operators as the user — long sessions, expert knowledge, complex state. Lifting them onto consumer tools imports those assumptions.