What are the differences between the Kibana 'oss' and 'non-oss' build?


I build my own custom Kibana packages. I've noticed the introduction of a oss only build of Kibana. Could you please explain to me the precise difference between the oss and the non-oss builds? Does the non-oss build just include x-pack, graph and the licensed Elastic stuff? Or is there something else?

Is the package that is released up to the public Elastic repositories the oss or the non-oss build?

edit. I think I've just found a page that explains the differences: https://www.elastic.co/guide/en/kibana/6.0/docker.html. I'm still keen to get the answer to my question about the packages that are released. Are they the 'oss' build?

Many thanks!

https://www.elastic.co/products/x-pack/open should clarify what you are after :slight_smile:

1 Like

Thanks Mark,

By sending me that link, I assume you're telling me the 'oss' version of the package contains none of the paid-for Elastic features. This is fine.

I can see that when I build the 'oss' version of the packages, it adds a '-oss' to the name, yet the publicly released packages do not include this. E.g

My build creates: kibana-oss-6.4.2-x86_64.rpm
Publicly release package: kibana-6.4.2-x86_64.rpm

Can you tell me why there is a difference in the naming? Am I right to assume the publicly released package is the 'oss' version? Is there an easy way for me to drop the '-oss' from my builds? No biggy if I can't.


1 Like

This is the default release that contains the commercially licensed code. The release that contains only open source will have the-oss appended to it.

1 Like

Thanks Mark.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.