Two halves, two answers

The control app is a universal binary: it runs natively on Apple Silicon and on Intel, with no translation. The servers it drives are prebuilt binaries from an existing open-source distribution, compiled for Intel, so on an Apple Silicon Mac they run through Rosetta 2, which macOS installs the first time something needs it. Everything works, and has since the M1, but the servers are translated rather than native.

Support by Mac processor
Mac Control app Servers Works
M4, M4 Pro, M4 MaxNative arm64Rosetta 2Yes
M3, M3 Pro, M3 Max, M3 UltraNative arm64Rosetta 2Yes
M2, M2 Pro, M2 Max, M2 UltraNative arm64Rosetta 2Tested
M1, M1 Pro, M1 Max, M1 UltraNative arm64Rosetta 2Yes
Intel, 2017 and laterNative x86_64Native x86_64Yes

Apple Silicon rows are one behaviour, not five: every M-series chip is arm64 and Rosetta 2 treats them the same way, so Pro, Max and Ultra variants make no difference to any of this. Development and testing happen on an M2 running macOS 26.3; the other rows follow from the architecture rather than from a machine we have in the room, and it seemed more useful to say so than to imply a lab full of Macs.

What is needed

macOS13 Ventura or later
Disk321 MB to download, and more once it is unpacked: a disk image is compressed, the installed folder is not
Rosetta 2Apple Silicon only. macOS offers to install it at first launch, or run softwareupdate --install-rosetta
Admin passwordAsked whenever VXOST changes its own files or services: starting and stopping, a new project or a port, the PHP version, the network exposure, the certificate, an update. Asked by sudo when you edit a configuration file by hand. Never stored
NetworkNot needed. The app asks vxost.com once a day whether a new version exists, which can be switched off from the menu bar icon, reads the list of PHP versions when you open that window, and after a check for updates if an extra PHP version is installed, and downloads an update or a PHP version only when you click Install

Checking it yourself

You do not have to take any of this on trust. lipo -info on a binary prints the architectures it holds: the app answers x86_64 arm64, and the servers answer x86_64. That is the whole of the story above.