01 / BUILD
Rendered for your estate
Node count, storage topology, cluster identity and site parameters baked in at build time. The image you boot is the image you were issued.
Download
Free to download, and to keep using.
umx will be free for anyone to download and run, with no feature gating and no expiry. AXS Systems makes money on support, certification, enterprise integrations and services — not on the core being crippled.
Not downloadable yet. There is no artefact behind this page today, so there is no download button — only a way to be told when there is one. We would rather say that than ship a link that goes nowhere.
The commitment
What "free" means, precisely.
Vague promises about future pricing are worth nothing, so this is stated plainly enough that you could hold us to it.
What is free, without exception
- The hypervisor, clustering, storage arbitration and VM lifecycle.
- GPU passthrough and the full inference path.
- The MCP fabric and its security model.
- The API, CLI and web console.
- All of it, in the same build — not a reduced edition.
There is no community edition with features removed. An artificially hobbled free tier is not a community edition, and the people most likely to try infrastructure software are exactly the people who will notice.
What we will charge for
- Production support and an SLA.
- Certified hardware and validated GPU configurations.
- Long-term support releases and security advisories.
- Enterprise identity, backup and observability integrations.
- Migration tooling, automated upgrades, fleet management.
- Professional services — architecture review, deployment, workload tuning.
We are not saying the software will always be free. We are saying umx Community is free, and that the commercial business is the things around it. If that changes you will find out before you are depending on it, not after.
How delivery will work
A per-site image, not a shared one.
The artefact is likely to be rendered for your site rather than shipped as one generic ISO. That is the same design property as the product: boot a node and it is already configured for its role, with nothing to install and nothing to trust but the image you were given.
02 / VERIFY
Checksummed and signed
Every artefact carries a published digest and a signature you can verify before boot, so the first thing a node does is authenticate what it was given.
03 / BOOT
PXE, then production
Power on a machine with a PXE ROM pointed at the site. It joins the cluster and schedules work. No installer, no controller, no enrolment console.
Still being decided: whether rendering happens on registration or on request, and whether delivery is instant or attended for a first site. Both are implementation choices behind this page rather than reasons for it not to exist.
Community
Built in public.
umx came out of a specific frustration: enterprise infrastructure had become unnecessarily complicated, and the complexity was concentrated exactly where it was least useful — in machinery that was supposed to be running a model.
That is a problem the people who run infrastructure will recognise immediately, and they are the people this is for. Discussion, issues and integration requests will be public.
Community forums
Architecture discussion, deployment help, integration requests. Opening soon.
Issue tracking
Bugs and enhancement requests in the open, with triage visible. Opening soon.
Source access
We intend to make enough of the codebase inspectable that serious engineers can evaluate and trust it. The licence is not settled and we would rather decide that deliberately than rush it.
These links are not up yet. We would rather show an honest "opening soon" than a link to an empty room. When they are live they will be here, without an announcement you have to go looking for.
Get told when the first build is available.
Early access means the people who shape the first release. If you have a specific model, a specific storage topology, or a specific thing you need it to do — say so, and that shapes what gets built rather than what gets announced.