Frequently Asked Questions

Q: Why Project Mercury?

When setup properly, cloud compute has a lot of hidden fees and unpredictable compute profiles due to heavy overloading and storage setups.

What if we could include everything a client really needed, right on the tin, without expensive additions that you end up bolting on only after you've lost data or had your VM compromised?

Project Mercury is a target specification at this time, it's actively under development so some of what follows will change. At the time of this writing, the expectations for what we hope to deliver can be found in the Project Mercury overview page

Q: What operating systems are supported in Project Mercury?

Currently, any UEFI operating system should be supported. But official testing has been performed with the following:

Linux
    Alpine
    RedHat
        Alma
        RHEL
        Rocky
    Debian
        Debian
        Ubuntu LTS
    Suse
        Suse Leap
        SEL
BSD
    FreeBSD
    OpenBSD
    NetBSD
    Dragonfly
Illumos
    OmniOSce
Windows
    Windows 10
    Windows Server 2016
    Windows Server 2019
    Windows Server 2022

Q: How is hardware allocated?

All hardware is allocated in increments of 1 CPU / 4GB Memory / 160GB SSD. Some Operating systems (notably Windows) have only been tested with a minimum of 4 CPU cores / 16GB Memory / 160GB SSD. Our testing shows this design for Windows hosts