O Programa de Certificação AlmaLinux
Hardware and software, certified to work with AlmaLinux. Certification is free and the suite is open source, so vendors, the Foundation, and our community all run the same tests.
Compatibilidade em que você pode confiar para desempenho, confiabilidade e estabilidade #
For users
Check a specific server, component, or application in the catalog before you commit to it, and see who verified it and when.
Validation is recorded for each AlmaLinux major version separately, so you can see what has been tested on the release you are deploying.
You can test anything yourself in a few minutes and add it, whether it is missing from the catalog or already there and worth confirming.
For vendors
Certification is free and self-service: no contract, no scheduling, no waiting on us. You run the same open source suite we do and publish the results under your own name. We want officially supporting AlmaLinux to be easy for you.
Hardware and software certification both live in the same catalog, under the same account.
How to certify #
- Boot our regular live media on the system you want to certify, or run the suite on an existing AlmaLinux installation. Nothing needs to be wiped or reinstalled.
- Install the suite from the
extras repository
and run it. Nearly all hardware finishes a certification run in under 10 minutes.
dnf install alma-certify - Publish your results to the catalog with a free AlmaLinux Account, or keep them to yourself. Everything published goes through review before it appears.
You only need an AlmaLinux Account if you want to publish what you find. If you are not sure what to run, run
alma-certify
with no arguments and it will walk you through the options.
The certification suite is open source and developed in the open by the Certification SIG.
Certifying software #
Software certification works differently, because there is no suite to run against an application the way there is against a machine. A software listing names the AlmaLinux major versions a product is certified for, and each of those versions carries its own evidence.
If you publish software, list your product in the catalog and cite the AlmaLinux releases it supports. If your company is not in the catalog yet, you can add it from the same form.
If you use software, sign in and confirm that a product works on the release you are running. Confirmations are counted one per person per release, and they sit alongside a publisher's certification. If you are running a product on a release its publisher has not cited, you can report that too.
Certify or confirm softwareValidation levels #
Every entry in the catalog includes the level of validation, which tells you who ran the test. Validations are cumulative: a vendor, the AlmaLinux OS Foundation, and any number of community members can all attest to the same listing, and each one adds to the confidence in it.
Community validated
Submitted by a community member. For hardware it is backed by real certification suite data, the same suite the vendors and the Foundation run. For software it is a confirmation that a product works on a given release. Community validation is just as valuable to us as a vendor listing.
AlmaLinux validated
Tested and certified directly by the AlmaLinux OS Foundation.
Vendor validated
Published by the vendor and backed by their own testing data. This is the path for hardware and software providers who want to state compatibility officially.
Certification here is a statement about compatibility. It says that AlmaLinux runs correctly on a piece of hardware, or that a piece of software runs correctly on AlmaLinux. This is not a regulatory or security certification. AlmaLinux OS 9.2 has those separately: FIPS 140-3 validated cryptographic modules and a Common Criteria certification.
The AlmaLinux Catalog #
Certified systems, components, and software all live in the catalog, along with benchmarks and validation history.
Go to catalog.almalinux.orgCertifying as a vendor #
Hardware and software providers who want an official listing should start with the program document, which covers what certification asserts, how results are reviewed, and how long a certification stays current.
Certifications published under the previous program carry over. Nothing needs to be recertified.
Hardware that has not been announced yet can be certified too. Mark the submission as pre-release with the date its results become public, and until then it is not listed anywhere.
