# How do I upstream a brand-new hardware backend to 🤗 Transformers/Optimum?

**URL:** <https://discuss.huggingface.co/t/how-do-i-upstream-a-brand-new-hardware-backend-to-transformers-optimum/161297>\
**Category:** 🤗Optimum\
**Created:** [July 1, 2025, 10:33am UTC](https://discuss.huggingface.co/t/how-do-i-upstream-a-brand-new-hardware-backend-to-transformers-optimum/161297 "2025-07-01T10:33:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![halflucifer](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/halflucifer/32/50048_2.png) [@halflucifer](https://discuss.huggingface.co/u/halflucifer)\
**Post date:** [July 1, 2025, 10:33am UTC](https://discuss.huggingface.co/t/how-do-i-upstream-a-brand-new-hardware-backend-to-transformers-optimum/161297/1 "2025-07-01T10:33:36Z")

</div>

Hi everyone! 👋

I’m part of the team behind **xThought** , an upcoming AI accelerator hardware for LLM inference. We’ve already built a working Transformers extension (xthought\_transformers) that ships:

- XThoughtConfig + XThoughtModel classes
- Basic safetensor export + runtime bindings
- Examples and tests

We’d like to integrate xThought with the HFT ecosystem and open-source the stack so a wider community can use it—hence my question about the correct path to upstream our backend into the main Hugging Face GitHub repositories.

I’ve studied the Optimum ecosystem and noticed most vendor backends live in **separate repos** like `optimum-nvidia`, `optimum-intel`, `optimum-executorch`, etc. That looks like the right pattern for us, so the plan is to open-source an `optimum-xthought` repo that mirrors those structures and then PR any Transformers-side hooks if required.

What’s the very first step? Should I open an RFC-style issue in the main `Optimum` repository, or is there another channel where I can submit my own `optimum-xthought` GitHub repo for an initial review?

If anyone has gone through this journey (e.g. Optimum-NVIDIA/-Executorch/-TPU maintainers 👋), I’d really appreciate your war stories and any gotchas you hit along the way.

Thanks a ton!

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\
**Post date:** [July 1, 2025, 10:48am UTC](https://discuss.huggingface.co/t/how-do-i-upstream-a-brand-new-hardware-backend-to-transformers-optimum/161297/2 "2025-07-01T10:48:32Z")

</div>

Hmm… For now I found it.

> **[Introducing Optimum: The Optimization Toolkit for Transformers at Scale](https://huggingface.co/blog/hardware-partners-program)**
>
> We’re on a journey to advance and democratize artificial intelligence through open source and open science.

> If you would like to see new hardware and features be supported in Optimum, or you are interested in joining us to work at the intersection of software and hardware, please reach out to us at [hardware@huggingface.co](mailto:hardware@huggingface.co)

---

<div class="post-metadata">

**Author:** ![halflucifer](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/halflucifer/32/50048_2.png) [@halflucifer](https://discuss.huggingface.co/u/halflucifer)\
**Post date:** [July 2, 2025, 2:37am UTC](https://discuss.huggingface.co/t/how-do-i-upstream-a-brand-new-hardware-backend-to-transformers-optimum/161297/3 "2025-07-02T02:37:46Z")

</div>

@John6666 Thank you for bringing this to my attention! I’ll reach out to them via email shortly.

Thanks!