# Filebeat vs filebeat-oss

**URL:** <https://discuss.elastic.co/t/filebeat-vs-filebeat-oss/373464>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [January 21, 2025, 3:54pm UTC](https://discuss.elastic.co/t/filebeat-vs-filebeat-oss/373464 "2025-01-21T15:54:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rihards](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rihards/32/136322_2.png) [@Rihards](https://discuss.elastic.co/u/Rihards)\
**Post date:** [January 21, 2025, 3:54pm UTC](https://discuss.elastic.co/t/filebeat-vs-filebeat-oss/373464/1 "2025-01-21T15:54:55Z")

</div>

Is there any documentation on which functionality in filebeat is proprietary (Elastic-licensed)? As in, not included in filebeat-oss.

filebeat on-disk (8.16.1, Linux) is 50+% bigger than filebeat-oss.  
Has anybody compared other usage, like RAM etc - are the non-oss components loaded or otherwise invoked?

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [January 21, 2025, 4:17pm UTC](https://discuss.elastic.co/t/filebeat-vs-filebeat-oss/373464/2 "2025-01-21T16:17:25Z")

</div>

I don't think that a documentation exists.

But in the github repository you can see which inputs are available only on Elastic License.

If I'm not wrong, the inputs available in filebeat oss are [here](https://github.com/elastic/beats/tree/main/filebeat/input), and the inputs available with an Elastic license are [here](https://github.com/elastic/beats/tree/main/x-pack/filebeat/input).

---

<div class="post-metadata">

**Author:** ![Rihards](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rihards/32/136322_2.png) [@Rihards](https://discuss.elastic.co/u/Rihards)\
**Post date:** [January 22, 2025, 8:22am UTC](https://discuss.elastic.co/t/filebeat-vs-filebeat-oss/373464/3 "2025-01-22T08:22:22Z")

</div>

Thanks, that indeed seems to be the best source right now.
