# Using custom ByteCodeProvider in Hibernate 6?

**URL:** <https://discourse.hibernate.org/t/using-custom-bytecodeprovider-in-hibernate-6/7160>\
**Category:** Hibernate ORM\
**Created:** [January 18, 2023, 12:51pm UTC](https://discourse.hibernate.org/t/using-custom-bytecodeprovider-in-hibernate-6/7160 "2023-01-18T12:51:56Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![beikov](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.hibernate.org/beikov/32/258_2.png) [@beikov](https://discourse.hibernate.org/u/beikov)\
**Post date:** [November 10, 2025, 12:04pm UTC](https://discourse.hibernate.org/t/using-custom-bytecodeprovider-in-hibernate-6/7160/6 "2025-11-10T12:04:05Z")

</div>

`BytecodeProvider` was turned into a Java `ServiceLoader` contract via [HHH-17643](https://hibernate.atlassian.net/browse/HHH-17643) in 6.2.21, so you can plug your own version if you want to maintain it. The Hibernate Team will only focus on one implementation.

Note that there are many potential reasons for why an application might start up slower. A lot has changed in the bootstrap of Hibernate ORM, so this could very well be due to something else.

If application startup time is important to you, you should consider doing the bytecode enhancement at build time or switch over to Quarkus directly, which does that out of the box and also allows you to compile to a native image, further lowering the startup time into the range of milliseconds.

---

_[View the full topic](https://discourse.hibernate.org/t/using-custom-bytecodeprovider-in-hibernate-6/7160)._