What is our primary use case?
My main use case for Rocky Linux is for QA and development, such as setting up environments, running automated test suites, validating services, and troubleshooting application behavior in a RHEL compatible environment.
I also use Rocky Linux to validate CI/CD workflows, containerized applications, and deployment-related issues in environments that are close to production.
What is most valuable?
The best features Rocky Linux offers in my experience are its stability, RHEL compatibility, strong security with SELinux, and reliable package management with DNF. It is also very useful for building QA environments that closely match production.
Compatibility has made the biggest difference, allowing me to reproduce production-like, RHEL environments for QA and catch deployment and configuration issues earlier, reducing environment-specific failures.
For QA, Rocky Linux's strong community support and predictable updates are highlights that make it easier to maintain consistent and reliable test environments over time.
Rocky Linux has impacted my organization positively by helping to create stable, production-like environments for QA and development, thus improving consistency, reducing environment-related issues, and making deployments more predictable. We have seen fewer environment-related issues and less time spent troubleshooting differences between QA and production, which has made testing and deployments more consistent.
What needs improvement?
Rocky Linux could improve its documentation and onboarding for newer users, especially around troubleshooting SELinux and system configuration.
The documentation and example configurations regarding SELinux and network configuration can sometimes be difficult to troubleshoot, especially for people coming from other Linux distributions. More practical examples and clearer error guidance would help solve these issues faster.
For how long have I used the solution?
I have used Rocky Linux for approximately four years, mainly in RHEL compatible environments for development, testing, and server administration.
What do I think about the stability of the solution?
Rocky Linux is stable and reliable for workloads, especially for QA and development environments.
What do I think about the scalability of the solution?
Scalability in Rocky Linux is very good, and it works well as workloads grow, particularly in virtualized and containerized environments, allowing us to scale resources without introducing major OS-level issues.
How are customer service and support?
Customer support for Rocky Linux is good, and I remember that the team was helpful with various scenarios, questions, and issues. The community is very active with helpful forums.
Rocky Linux has a great community, and it is usually easy to find documentation, forums, and RHEL compatibility solutions while troubleshooting the most common issues, making it straightforward to solve problems.
Which solution did I use previously and why did I switch?
We previously used CentOS and Ubuntu, but we noticed performance issues, leading us to explore options and find that Rocky Linux has great performance, especially in workloads, which prompted us to switch.
What was our ROI?
We have seen a positive return from eliminating OS licensing costs and reducing maintenance overhead. We save time through fewer environment-related issues and more consistent QA and deployment processes.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for Rocky Linux is good because there are no licensing fees. The main costs are infrastructure setup, maintenance, and internal support rather than the operating system itself.
Which other solutions did I evaluate?
Before choosing Rocky Linux, I evaluated options including AlmaLinux, CentOS Stream, and RHEL. In the end, Rocky Linux was a good fit because of its RHEL compatibility, stability, and open-source model.
What other advice do I have?
I would improve the documentation, troubleshooting tools, and integration guidance for modern DevOps, container, and AI workloads. Better migration guides and more real-world examples would also help teams adopt Rocky Linux faster.
The learning curve for Rocky Linux is moderate. If you already have experience with RHEL or CentOS, Rocky Linux feels very familiar, but areas such as SELinux and network configuration can take more time to master.
In my experience, update and patch management in Rocky Linux is straightforward and reliable. DNF makes it easy to manage packages and security updates, allowing us to test patches in QA before promoting them to production-like environments.
I would rate Rocky Linux's performance and resource efficiency under heavy workloads very well. It has been stable and resource-efficient with predictable CPU and memory usage, which is very important for QA and development environments.
It is relatively easy to integrate Rocky Linux with CI/CD tools, Docker, Podman, and Kubernetes, enabling us to build consistent environments for automated testing and deployment with minimal compatibility issues.
Rocky Linux provides a strong foundation for compliance through SELinux, with regular security updates, auditing, and system hardening. Meeting regulatory requirements still depends on how the organization configures and manages the environment.
Compared with CentOS Stream, Rocky Linux feels more predictable for stable enterprise environments because it focuses on RHEL compatibility. Updates are consistent and the community support is strong, even though commercial support options are not as extensive as RHEL.
My advice for those looking into using Rocky Linux is to ensure good infrastructure. Start by testing in a non-production environment and validate your applications, security policies, and automation workflows.
Rocky Linux has been a reliable and cost-effective platform for us, and its RHEL compatibility, stability, and strong community make it a solid choice for QA, development, and private cloud environments. I would rate this product a ten out of ten.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?