# Hosting your own Elastic Package Registry **URL:** \ **Category:** Elastic Observability\ **Tags:** fleet\ **Created:** [September 27, 2021, 12:20pm UTC](https://discuss.elastic.co/t/hosting-your-own-elastic-package-registry/285230 "2021-09-27T12:20:41Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![zx8086](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zx8086/32/94917_2.png) [@zx8086](https://discuss.elastic.co/u/zx8086)\ **Post date:** [September 27, 2021, 12:20pm UTC](https://discuss.elastic.co/t/hosting-your-own-elastic-package-registry/285230/1 "2021-09-27T12:20:41Z")
It is not abundantly clear in any of the documentation that this is a feature that requires an Enterprise License. For something that is in Beta, Experimental and might not make it into GA anytime soon, why would this be so. A lot of bandwidth, network or security conscious tech enthusiasts that sit outside enterprises do have this requirement, for such a set-up, so it would be good to know before hand when investing time into a solution that you only realize is an enterprise feature via the error logs. ---
**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\ **Post date:** [September 30, 2021, 1:00pm UTC](https://discuss.elastic.co/t/hosting-your-own-elastic-package-registry/285230/2 "2021-09-30T13:00:19Z")
This should help: [Remove Enterprise license requirement from EPR · Issue #736 · elastic/package-registry · GitHub](https://github.com/elastic/package-registry/issues/736) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 4, 2022, 8:32am UTC](https://discuss.elastic.co/t/hosting-your-own-elastic-package-registry/285230/3 "2022-11-04T08:32:30Z")