The page navigation is complete. You may now navigate the page content as you wish.
Skip to main content

Documentation versions

Other versions
HDS components v7.0.0 is now available! Learn more about the changes in this major release

From Helios to Carbon

While adopting the "carbonized" version of the Helios Design System (HDS) is not strictly required, we strongly recommend that teams start planning for it.

Aligning with IBM's design language

As HashiCorp products integrate into the IBM ecosystem, adopting a shared design language ensures a seamless, familiar experience for users—no matter where they are in that ecosystem.

What this means for Helios

Helios is migrating to IBM's design language by aligning with the Carbon Design System, the foundation of IBM's product ecosystem. Because HDS remains foundational to HashiCorp products, Helios is not going away.

Instead of starting from scratch, we are shifting to a local system model. Helios remains the official design system for HashiCorp products, but it is now built on IBM's design language. Your products will look and feel like IBM products while running on the same technology stack.

In practical terms:

What this means for our consumers

Your day-to-day workflow remains largely unchanged:

We continue to support and maintain HDS, prioritizing bug fixes and critical updates.

What changes for designers

Product Designers currently using HDS will see minimal impact on day-to-day workflows, but keep a few key updates in mind:

See the Carbonization for designers migration guide for details.

What changes for engineers

Products are not required to migrate from Ember to React; framework decisions remain product-driven.

The three biggest changes at code level introduced with the "carbonization" of the design system are:

These changes impact only the visual styling of the HDS components: their APIs and interaction behavior remain unchanged.

That said, because these updates to the tokens introduce breaking changes, the HDS packages have been released as new major versions, and this requires specific migration steps.

After migrating, developers will need to start testing their application across the different themes to catch theme-specific issues.

For more details, see Carbonization for engineers.

New design system ecosystem

Introducing the Carbon Design System visual language via the Helios v7.0.0 release shifts the existing design system ecosystem for HashiCorp products.

What design systems are available to use?

Which system should you use?

Can they be used together?

It depends.

Once a team has upgraded to HDS v7.0.0+ and started to use the light and dark modes, the product will look like a part of the larger IBM portfolio and thus the Carbon Design System.

There may be instances where the Carbon Design System offers a component or pattern that the Helios Design System does not, such as Charts or AI experiences. When this happens, Designers will need to speak with their Engineering and Product teams to understand the level of effort for implementation. In Figma, use the Carbon Design System components directly. In code, there are two paths:

FAQ

Why not adopt Carbon directly?

Most HashiCorp products use Ember.js, which Carbon does not support (Carbon only provides React and Web Components). We explored bringing Carbon's Web Components into our Ember codebases, but encountered fundamental architectural incompatibilities with Ember's routing, data flow, rendering, and lifecycle models.

Will HDS be deprecated?

No. We are transitioning to a local system model where Helios remains the official implementation for HashiCorp products while aligning visually and semantically with Carbon.

Can I still submit feature requests and bug fixes?

Absolutely. Send requests to the HDS team for triage. While we focus on the Carbon migration, we may prioritize fewer new features, but we will continue to prioritize bug fixes.

Get in touch

Contact us on Slack at #proj-hds-carbon or visit the support page for other ways to get in touch with us.


Related