How reliable is the Hyvä compatibility status?

Reliability varies by tier and is colour-coded for a reason:

• hyva_module — built natively for Hyvä, often by Hyvä themselves or a Hyvä-listed partner. Tailwind + Alpine output. Reliability: very high. If this tag is wrong, blame me.
• compatible — I’ve installed it on a Hyvä storefront and it rendered cleanly with no template overrides for the major flows (PDP, PLP, cart, checkout, my-account). Reliability: high. Edge-case admin features may still need theme work.
• partial — works but needs frontend template overrides in your custom Hyvä theme to match the design system. Reliability: medium. Budget 4-12 hours of theme work per module.
• blocker — injects Luma-only JS / KnockoutJS / RequireJS that breaks Hyvä. Reliability: high (avoid).
• unknown — I haven’t personally tested it on Hyvä. Reliability: ask the vendor before committing.

The tag reflects my own integration experience as of this quarter. Vendor-published Hyvä compat claims are taken with a grain of salt — I’ve seen vendors call themselves “Hyvä compatible” when they mean “the admin module works on a Hyvä storefront.” That’s not the same thing.