When we make new features we ask ourselves, is this feature **more relevant for organizations that have more than 100 potential users**?
If the answer is yes the feature is likely to be exclusive to EE.
There are no features that are only useful to larger organizations, so for every EE features there will be smaller organizations that also need it. We're not saying that there are no small organizations that need the EE feature, just that we think that larger organizations are more likely to need it. As a guideline, features which improve on ease-of-use should be considered for CE. All the while, features which either improve on efficiency and complexity or add non-essential functionality should be considered for EE.
There are no features that are only useful to larger organizations, so for every EE features there will be smaller organizations that also need it. We're not saying that there are no small organizations that need the EE feature, just that we think that larger organizations are more likely to need it. As a guideline, features which improve on the ease-of-use and simplicity of major [features](https://about.gitlab.com/direction/#scope)should be considered for CE. All the while, features which either improve on efficiency and complexity or add non-major functionality should be considered for EE.
It is hard to get CE vs. EE right, and if we put something in EE that should be in CE we won't hesitate to [open-source](https://about.gitlab.com/2016/12/24/were-bringing-gitlab-pages-to-community-edition/)[it](https://news.ycombinator.com/item?id=10931347).
