[frequent]

We distinguish between must vs should.

Open Service means we must be transparent about what suppliers, components and procedures are used to provide a cloud (or any other) service, so that anyone can use/study/copy/operate the service. Used components should be open-source on the other hand. We cannot guarantee them to be in order to provide the service.

Open Hardware is the same. It must be transparent regarding components being used, so bill of materials, PCB design files etc must be available so that anyone can rebuild a product. All components then should be open-source, but it cannot be guaranteed that they are.

When you instead insist on "must be open-source" you may end up without a solution or something very expensive or very slow for which there may be no market. Or you can make a competitive product, which must be transparent, can be replicated and should be open. Then invest over time to open-source the remaining non-open components. The openRRH project fits into this principle.

More info on https://www.fdl-lef.org/FDL-Hyper.Open.Initiative

[RaitoBezarius]

The question was more like, have you explored running servers with actual open hardware such as RISC-V CPUs, Alibaba seems to be putting out a non-toy RV64GC (https://conferences.computer.org/isca/pdfs/ISCA2020-4QlDegUf...), and I guess they will want to apply it for their clouds. At least, it is based on an open source ISA, that's closer to open hardware than Intel CPUs, AFAIK.

Also, it's unclear whether secure boot / TPM are available on your servers based on your website.

[frequent]

re Alibaba: We're aware of the Alibaba CPU and are following it. It is indeed very interesting. But we also visited one of the factories where their servers are produced. Everything is secret and there seems to be no open-source culture, so we don't have much hope. We tried working with OpenPower servers, but when testing with real workloads, they were ~4x slower than x86 or ARM.

re Secure Boot: We use secure boot / TPM only in Capri servers and it causes of lot of work with suppliers. We are working on a drakut uefi boot with secure boot and are slowly sloving BIOS issues. Linuxboot bios is used on some servers, but it's not maintained and no secure boot, plus the information from Intel to maintain linuxboot is secret with NDA. In general, securing the boot process requires hopping piggyback on larger companies with the same issues and the bargaining power to speak with AMD or Intel, because NDAs are a dead end and without bargaining power, your mileage is short.

If you're interested to discuss in more detail, send me an email and I'll connect you with my boss who knows a lot more.