Much confusion is done on community projects Linux OpenStack foundation and Apache which are the best known and represented on the chart by a number (1).

Importantly they are not finished products and so are called projects coordinated by these foundations for cooperative development by various companies and developers community is cohesive. There is no guarantee to use them in business because they are not certified, or stabilized, and there is also no guarantee the life cycle. Formal support, no way! Support only through interactions in mailing lists and on the websites of the foundations.

already software vendors based on Open Source projects integrate dozens of projects to create a product, which in the first stage version called “upstream”, represented in the drawing as number two (2). Therefore, there is an effort in order to be properly integrated, and functional. This is where the development of engineering works mainly: This product continues to receive contributions from other companies and developer communities, but are coordinated by the manufacturer. This “upstream” version can be classified as a version of “roadmap” of the products.

It is not yet stabilized and should not be used in production. It should be treated, therefore, as a “beta”: use it to meet new product features and learn about features that are being developed that have the potential to turn the final product


The final product is represented by the number three (3), and is the version that the customer receives when purchasing a subscription to the manufacturer and this version is paid annually. From the “upstream”, it creates the enterprise version that goes through a quality engineering team that stabilizes the code is stringent safety testing, scalability, make the software with hardware manufacturers and other software to correct any problem compatibility. In fact, more important than the certificate stamp, support contracts are set so that in the event of a problem in production manufacturer of engineering work together with the Hardware or certified software to deem the resolution of this problem and evolve the product to make it more and more robust. This process does not exist in version “upstream” (2) and much less on the Community design (1) which, of course, have no certification and no support from major manufacturers behind.

Complementing the value of the version enterprise, in addition to the product manufacturer’s support together with certified manufacturers, there is access to the user portal with all the documentation, including corrections, updates, support based on SLA (service level ), and continued maintenance policies.

Many are curious to know what is included when you purchase a subscription empresarial.Como example’m listing what is included in Red Hat subscriptions:

  • Access to certified products: binary and source code , documentation, new releases, product upgrades and patches.
  • Flexibility: a subscription is not tied to a specific version, so earlier versions are also available and supported as well as the next versions
  • .

  • Customer Portal: View and track problems, customize patch or upgrade alerts, download patches and updates certified
  • .

  • Specialized Support: Unlimited support for expert engineers for incidents to cover 24 hours a day, 7 days a week with 1 hour response time for critical incidents
  • .

  • stability in the long term:. Continued product support and updates, and security patches policies
  • Open Source Assurance: assistance in the event of any legal risk
  • .

  • Transfer of knowledge, assistance and certification: easy to understand training, large network of consultants, systems integrators and software partners
  • .

For all these reasons I can assure that only an Enterprise version is suitable for use in production environments and has the quality to support typical loads and critical environments professional datacenters.

Subscribe to our channel and learn about technology!

Boris Kuszka

Boris Kuszka is the Director of Solution Architect at Red Hat.