The Vates Alliance Network is open: 28 technology partners around Vates VMS, in one place
van.vates.tech is open. Members, the Solutions list, Solution Briefs and Solution Guides for Vates VMS now live in one place, so you can discover how far the Vates VMS ecosystem will take you.
Today, October 27, 2026, the Vates Alliance Network opens at van.vates.tech. For the first time, the technology partners, solutions, Solution Briefs and Solution Guides around Vates VMS sit in one public place. Before you build your infrastructure on a combination of products, you can see how they work together, what has been checked and where to start.
When we introduced the VAN in March, we described what it would do. Today, you can use it.
Building a product that works with Vates VMS? Apply to join the VAN. Membership is free.
Why we built it: nobody runs a hypervisor alone
A virtualization platform never lives in isolation. Vates VMS, the platform made of XCP-ng and Xen Orchestra, always runs inside an environment:
- it runs on servers and stores data on arrays;
- it is protected by backup tools and secured by security software;
- it is watched by monitoring platforms;
- it is installed by integrators and often operated by a service provider.
That environment is not a detail around the product. It is where the product lives.
So when an organization moves to Vates VMS, whether it is leaving VMware or building a new cluster, it is not buying a hypervisor. It is building a complete solution, and every choice raises the same question: does this combination work, and is it written down somewhere?
Until now, the answer was scattered across our documentation, the XCP-ng forum, vendor PDFs and partner announcements. The VAN puts it in one place, in the open, for anyone to check.
Jb Piacentino
How we look at business: open, interoperable, together
The VAN is more than a website. It is a statement of how Vates wants to do business:
- Open. Open source is how we build our platform. The same principle applies to our ecosystem: what works with Vates VMS, and how, should be public and verifiable, not locked in a sales deck.
- Interoperable. Customers should be free to choose the best server, storage, backup or security product for their needs, and to know it fits. Our job is to make Vates VMS work well with the technologies they already trust, not to pull them into a closed stack.
- In partnership. No single vendor delivers a complete solution alone. We work with our members to integrate, validate and improve, so that the combination is better than its parts, and so that technology moves forward faster together.
The ecosystem is our substrate: the ground our platform grows in. The stronger the network around Vates VMS, the more value every customer gets from it. That is why the network matters as much as the product.
What is already on the VAN
The platform opens with:
- 28 technology partners, from server and processor makers to storage, backup, security, networking and observability vendors;
- dozens of solutions that work with Vates VMS, and
- Solution Briefs, each built around one concrete use case;
- Solution Guides for complete architectures, and partner news.
It covers 24 technology areas, with partners active in North America, EMEA, APJ and LATAM. Backup and disaster recovery, storage, security, networking, observability, compute and AI are all there.
The platform holds several types of content, from a single solution entry to a full reference architecture:
| Content | What it answers | Who it's for |
|---|---|---|
| Members | Which vendors and service providers work with Vates VMS? | Buyers shortlisting a stack, integrators |
| Solutions | Which solutions work with Vates VMS? Has this product been tested with XCP-ng and Xen Orchestra, and on which versions? | Architects, admins, procurement |
| Solution Brief | How do two or more products work together, and what was tested? | Technical evaluators |
| Solution Guide | How do I design, deploy and run a complete architecture built from tested components? | Integrators, project teams |
The website is the tip of the iceberg
What you see at van.vates.tech is the visible part of the work. Underneath, our Alliance team works with VAN members on two fronts:
- With their product and engineering teams, to evolve our integrations, so that customers get the best out of the combined solutions, release after release.
- With their sales and marketing teams, to make sure the value of the combined solutions is clearly visible to end users and channel partners.
Every page on the VAN is backed by that relationship. And every document is honest about where it stands.
How a solution gets on the VAN: validate, document, activate
Every VAN solution follows the same three steps:
- Validate. The partner and Vates engineers test the integration against real customer requirements.
- Document. The result becomes a Solution Brief, an entry in the Solutions list or a contribution to a multi-partner Solution Guide. If it isn’t documented, it isn’t on the VAN.
- Activate. Once a solution is validated and documented, we promote it together: joint announcements, webinars, events and case studies.
We keep that order on purpose. A logo on a partner page tells a buyer that two companies signed something. A Solution Brief tells them what was tested, on which versions, and where the limits are.
How to use the platform
If you’re planning a move to Vates VMS, start from the VAN before you settle on the rest of your stack:
- Search the Solutions list for what you need, or for the products you already run or plan to buy: servers, storage arrays, backup, monitoring.
- Open a Solution Brief for each match to see how the products work together, what was tested and on which versions.
- If a Solution Guide covers your use case, use it as your reference architecture. It saves you from assembling the design yourself.
- If a product you depend on is missing, tell us. Gaps in the list show us which validations to prioritize next.
For the broader picture of what already works around XCP-ng (hardware, storage, backup, VDI, network, hosting), our documentation keeps an ecosystem overview.
This is only the beginning
Today is not the finish line, it is the starting line. Every partner who joins, every integration we deepen and every integrator who can deliver a complete, documented solution makes the whole ecosystem stronger, and Vates VMS more valuable for everyone who runs it.
We built the VAN because we believe infrastructure should be open, interoperable and built together. Now that belief has a home.
FAQ
Is joining the Vates Alliance Network free?
Yes. VAN membership is free, and there’s no commitment until both sides see a clear path to collaborate.
Is the Solutions list public?
Yes. Anyone can check on van.vates.tech which products work with XCP-ng and Xen Orchestra, and what has been validated.
What’s the difference between a Solution Brief and a Solution Guide?
A Solution Brief documents how two solutions work together and the value of combining them. A Solution Guide describes a complete deployable architecture: design, deployment and operations.
Is the VAN the same as the Vates partner program?
No, and a company can be part of both:
- The VAN is for technology and solution vendors whose products integrate with Vates VMS.
- The Vates partner program is for companies that resell, integrate or operate Vates VMS for their customers, with reseller, integrator and MSP tracks.