# Helion Inductor Integration

**URL:** <https://dev-discuss.pytorch.org/t/helion-inductor-integration/3302>\
**Category:** compiler\
**Created:** [February 4, 2026, 3:09pm UTC](https://dev-discuss.pytorch.org/t/helion-inductor-integration/3302 "2026-02-04T15:09:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![morrison-turnansky](https://yyz2.discourse-cdn.com/flex036/user_avatar/dev-discuss.pytorch.org/morrison-turnansky/32/3135_2.png) [@morrison-turnansky](https://dev-discuss.pytorch.org/u/morrison-turnansky)\
**Post date:** [February 4, 2026, 3:09pm UTC](https://dev-discuss.pytorch.org/t/helion-inductor-integration/3302/1 "2026-02-04T15:09:06Z")

</div>

I am curious about the plan for Helion support in Inductor. Is there an RFC for this?

For a given graph, is the intention to have the backend be purely triton vs purely Helion or is there a strategy to be able to mix and match. For mixing and matching, is there a discussion about mitigating fusion barriers?

---

<div class="post-metadata">

**Author:** ![jongsok.choi](https://avatars.discourse-cdn.com/v4/letter/j/e495f1/32.png) [@jongsok.choi](https://dev-discuss.pytorch.org/u/jongsok.choi)\
**Post date:** [February 4, 2026, 4:44pm UTC](https://dev-discuss.pytorch.org/t/helion-inductor-integration/3302/2 "2026-02-04T16:44:49Z")

</div>

We’re currently working on Helion + Inductor fusion. Please see RFC here: [[RFC] Helion kernel + Inductor ops prologue / epilogue fusion · Issue #1346 · pytorch/helion · GitHub](https://github.com/pytorch/helion/issues/1346)

---

<div class="post-metadata">

**Author:** ![morrison-turnansky](https://yyz2.discourse-cdn.com/flex036/user_avatar/dev-discuss.pytorch.org/morrison-turnansky/32/3135_2.png) [@morrison-turnansky](https://dev-discuss.pytorch.org/u/morrison-turnansky)\
**Post date:** [February 4, 2026, 5:31pm UTC](https://dev-discuss.pytorch.org/t/helion-inductor-integration/3302/3 "2026-02-04T17:31:19Z")

</div>

Thank you, this is exactly what I was looking for!