Subscribe to GEN
Login to GEN
GEN have run Proxmox in production in our own UK data centres since 2015, and supported it for enterprise customers for just as long. The engineers who keep that estate running are the engineers who take your call, on service levels from 4 hours during business hours through to 30 minutes, 24 hours a day, every day of the year. We support Proxmox for clients worldwide, and those 24 hour service levels apply in every time zone.
We choose our partnerships carefully and work only with vendors who leave us completely free in what we advise, so the advice you get here is genuinely independent. There is no contract either: you buy hours, you use hours, and you stay because the support is worth paying for.
We choose our partnerships carefully, and support only those companies who give us complete freedom in what we advise and recommend: no targets pushing us to sell or sign you up, no restrictions against competitors, and no licensing entanglement tying you to a specific service. A customer running Proxmox alongside VMware, Hyper-V or HPE VM Essentials needs a provider who can say which platform suits each workload, and that is only possible when nothing has decided the answer in advance.
Proxmox is open source. Whether you support the project is entirely your decision, and not one we will make for you. If you do choose to, with a subscription or a donation, buy it directly from Proxmox Server Solutions, so the money reaches the people writing the code rather than enriching a reseller.
Our reputation is protected the way enterprise customers want and rarely get: a bulletproof, bidirectional NDA. Section 5 of our Framework Agreement makes the relationship itself confidential in both directions, along with your sites, your people and your infrastructure, and it survives the end of the agreement. This page names no customers, which equally means we will never be naming you.
Across 2021 and 2022, through the VMware exodus that followed the licensing changes, GEN engineers migrated 3,900 nodes from ESXi to Proxmox. Estates of every size, from a single host to multi-site clusters, and we have been doing it ever since, from initial planning through to fine tuning once you are live.
Most migration pain arrives after the virtual machines have transferred. We deal with the post-transfer issues in networking, disks and storage across both Windows and Linux guests, so your transfer succeeds the first time and with the minimum of downtime.
Migration work can be delivered as a project, or rolled into an ongoing support or maintenance agreement so the same team that moves you onto Proxmox carries on running it. Full detail is on our VMware to Proxmox migration page.
Independence is only worth anything if you can act on it. Proxmox is not the only hypervisor we support, and that is precisely what makes our advice on it worth having. A provider whose only competence is Proxmox has only one recommendation available to it, whatever your requirement turns out to be.
That breadth is what lets our engineers tell you where Proxmox is the right fit, where another platform serves you better, and where a mixed estate is the honest answer. Most of our customers run at least two of these side by side, and we support the result as one estate either way.
GEN offer a comprehensive portfolio of enterprise support for the Proxmox Virtual Environment (PVE), including pay-per-use support, hybrid support, on-site support and out of hours emergency cover, all provided in-house by GEN's technical teams.
Maintenance agreements provide a fixed cost for hybrid or fully managed outsourcing, and service levels can be mixed and matched across your virtualisation infrastructure, so the cluster carrying your production workloads is covered by our 30 minute SLA while a development node sits on something lighter.
There is no contract to sign: you buy hours at our published rates and use them when you need them, and a maintenance agreement is your choice on commercial grounds, not a condition of being supported. Every fault is worked through our SAPR method, and how GEN support works sets out both in full.
Any competent provider can log into a Proxmox cluster and fix what is broken. These are the things we have built around the platform since 2015, and they arrive with the support whether you are on an SLA or paying by the hour.
Our Oversight infrastructure monitor is a deep dive Proxmox monitoring solution for clusters, assessing guest and host utilisation, disk space, disk performance, IO queue, network activity and much more. Data is logged over time so our engineers can assess trends and predict issues, while triggers raise events on our system and automatically allocate an engineer to resolve them. See how it fits together.
Cluster-wide Proxmox notifications are sent to our API webhook, where our systems analyse them for problems, failures, warnings and operational exceptions. Failed backups, replication or sync issues, migration problems and clone failures are assessed automatically and, where needed, converted into HelpDesk tickets for engineering review. Nobody has to sit and watch every backup run.
An extensive suite of diagnostic scripts written specifically for Proxmox over a decade of real faults. A single command on the affected node collects the evidence and submits it straight to the HelpDesk: system state, cluster and quorum status, storage and Ceph health, networking, guest configuration and the relevant logs. Nobody wastes the first hour of an outage asking you to paste command output, and it is the single largest reason our response times hold up in practice as well as on paper.
Synchronise your Proxmox Backup Server (PBS) backups to GEN's data centres for high availability offsite storage. In a crisis our Cloud restore takes your PBS backup and builds a cloud hosted instance of your VM or CT in minutes. We can sync daily, bi-daily, hourly or continuously, with flexible retention and prune, so there is always a secure offsite copy of your critical virtual machines and containers.
We build and support the configurations the installer will not give you: GFS2 and other clustered filesystems, SMB and CIFS backed storage, unusual iSCSI, NFS and multipath arrangements, non-standard network and SDN topologies, custom hook scripts, kernel and driver work for older or awkward hardware, and integration with storage and backup platforms Proxmox has no native support for. If it can be made to work we will tell you honestly whether it should be, and then make it work.
A decade of Proxmox problems, and their solutions, written down. Our technical knowledge base is curated by the engineers who resolved the cases, not copied from upstream documentation, and covers what the manual does not: storage that will not mount, quorum that will not form, migrations that stall. Cheat-sheets, checklists and configuration references are in our customer downloads area.
Oversight, our infrastructure monitoring service, watches a Proxmox estate from three sides. The API, the host and the package list each show what the other two cannot, so none of them replaces another.
A read-only token, with nothing installed on the nodes. Quorum and membership with the offline nodes named, and every VM and container as its own reading, so a backup or migration reads as the expected state it is and a guest that has vanished reads as not found rather than passing quietly. A node removed from the cluster raises a warning, even though the cluster looks healthy without it. Ceph health comes the same way, and anything else the API answers, guest utilisation included, can be tracked and charted.
The API reports what Proxmox believes. The agent on each node, and on your Backup Servers, reports what the machine is doing: an array member running far slower than its siblings, a mount missing or gone read-only, an NFS server that has stopped answering, a bond member down, a link renegotiated to a lower speed, a service crash-looping. Its processor and storage figures chart host utilisation over time, and it understands ZFS memory use, so a healthy ZFS host does not read as out of memory. It runs unprivileged and has no way to run a command.
Every package on every host, in one search. openssh* < 9.9 lists every host still behind, across distributions, and one click upgrades them all, with each result back in minutes and no SSH or open port. Hosts carrying guests stay out of a bulk upgrade unless chosen deliberately, so nobody reboots a cluster by accident. On a Proxmox node, Proxmox and Ceph packages, corosync and the kernel are left for an engineer, the node is never rebooted for you, and each host can lock down further what may be touched. Every change is logged, along with who made it.
When something goes wrong you get one message, not fifty. A fault is only raised once the evidence agrees, it is reported once with everything it has taken with it, and a node that has gone raises one alarm rather than one for every sensor on it. The alarm goes to whoever you choose first. If nobody acknowledges it in time it moves on to the next step, whether that is a call to your on-call or a ticket on our HelpDesk with the charts and poll log attached, for our engineers to pick up under your support agreement.
Backup runs report for themselves. Proxmox's own event notifications come to our webhook, where they are analysed and any failure or concern becomes a HelpDesk ticket. If you would rather handle them inside Oversight, the log sender picks out the lines that matter and sends them there instead.
Slower trouble is caught too. Behaviour analysis watches the sensors you choose for what no threshold notices, such as a volume filling or a response time climbing over days, and flags the drift while there is still time to plan the fix, rather than leaving it to become a crisis on a Friday afternoon. How Oversight works, and what it costs, is on its own page.
GEN runs its own in-house development team, and a great deal of what it writes sits on top of Proxmox. Very few support providers can say that, and it is the difference between a provider who can configure your cluster and one who can automate it.
We work directly against the Proxmox REST API rather than around it, so anything the web interface can do can be driven programmatically, and a good deal that it cannot. Ansible playbooks handle configuration, patching and repeatable operational tasks across a whole cluster. Terraform provisions virtual machines, containers, storage and networking as code, with cloud-init templates behind it, so an environment is described in a repository rather than assembled by hand.
On top of that we write shell and Perl against the node itself, middleware connecting Proxmox to the systems your business already runs, and monitoring pipelines feeding our own response tooling. It is the same framework we use to run our own estate, and we will build on it for yours, or hand it over and train your team to run it.
Proxmox VE's clustering allows high availability across multiple nodes and locations. GEN provide dedicated Proxmox VE nodes in our data centres that you can join to your existing clusters, giving you off-site replication, failover and high availability even when you only have one site. See our Proxmox virtualisation services for GEN Cloud, Edge and Converged Virtualisation.
This does not need expensive private circuits or SD-WAN. Many of our customers run hybrid clusters successfully over business grade broadband, though for high traffic clusters, and especially with Ceph, a dedicated connection is recommended.
Proxmox fits equally well into small business deployments and large scale enterprise estates, and the same support, monitoring and tooling applies at either end of that range. A three node cluster in one office gets the diagnostic scripts, the knowledge base and the 24/7 engineers, exactly as a multi-site estate does, and on exactly the same terms.
We offer structured Proxmox training across three levels, with specialist courses in storage and networking, built around your operational needs. Some teams only need day-to-day operations, while others need deeper focus on storage or networking, so we tailor the content and course structure to suit your environment.
Beyond Level 3 we teach Proxmox at source code level, and as far as we are aware nobody else in the UK does. Because the platform is open, we can take an engineering team past the administration guide and into what the code actually does: how the cluster filesystem and the Corosync layer behave when a node drops, what a given daemon does on the way to the error message you are looking at, where the Perl and C boundaries sit, how the REST API is implemented underneath the web interface, and how to read the upstream repository to establish whether a behaviour is a bug or a design decision. Teams that have sat through it stop guessing at faults, and the calls they do raise with us arrive already diagnosed. No proprietary hypervisor can be taught this way at any price.
Courses are delivered remotely or on-site across the UK, and full details are on our Proxmox training courses page.
Proxmox Virtual Environment (Proxmox VE or PVE) is an open source virtualisation platform for hyper-converged infrastructure. It combines KVM with QEMU hardware emulation for full virtual machines and Linux Containers (LXC) for lightweight containerisation, all hosted on Debian Linux, and it offers several benefits over proprietary platforms such as VMware or Hyper-V.
Proxmox is free to use, with optional paid support available. This significantly reduces licensing costs compared to VMware's subscription model or Hyper-V's potential licensing fees, and removes much of the financial risk of scaling up.
As an open source solution built on Debian Linux, Proxmox can be modified and adapted to an organisation's specific needs with almost no limit. That flexibility is not available with closed source alternatives.
Being based on the KVM hypervisor and LXC containers, Proxmox does not lock you into its own solution. Virtual machines move easily to any other KVM based system, and can be migrated to other platforms.
A very active community contributes to testing and development and provides peer support, which leads to faster bug fixes and feature improvements. Proxmox has always been receptive to community feedback and requests, and the platform keeps moving forward.
Proxmox support, even fully managed by GEN, is very competitive and significantly less than comparable support from VMware or Microsoft. An open platform gives us far better access to technical data and source code, so issues are resolved far quicker, and over many years we have built an entire catalogue of our own tools to diagnose, manage and troubleshoot it.
Proxmox supports both virtual machines and containers, high availability clustering and integrated backup, and its extensive API allows custom solutions to be built around the platform with ease.
VMware and Hyper-V are quick to drop support for older hardware and to mandate minimum requirements that are sometimes out of reach for a small business. Proxmox, KVM and LXC run on a far wider range of hardware, and fully support vendors like HPE from G8 right through to G11.
Proxmox and Debian on server infrastructure from the likes of HPE can deliver lower power consumption and real energy savings, an important consideration for any estate today.
GEN provide enterprise Proxmox support across the UK, with a 30 minute SLA available 24 hours a day, every day of the year. GEN have run Proxmox in production in their own UK data centres since 2015, and have been in enterprise IT for 37 years. Support is delivered by in-house UK engineers with no outsourced first line.
Yes. GEN support Proxmox estates for clients across Europe, the Americas and Canada, the Middle East, Africa, India and the Far East, as well as the UK. Support is delivered remotely by the same in-house engineers, and the 24 hour service levels, including the 30 minute SLA, apply in every time zone, so a fault at 3am local time is answered at 3am local time.
No. GEN's support is independent of any Proxmox subscription. A subscription buys the enterprise repository and support from Proxmox Server Solutions themselves, and whether to buy one is entirely the customer's decision. Anyone who does is best to buy it directly from Proxmox, so the money reaches the developers rather than a reseller. It is not a condition of being supported by GEN.
GEN's fastest service level puts an engineer on a critical fault within 30 minutes, 24 hours a day, every day of the year. Service levels run from 4 hours during business hours up to that 30 minute response, and different levels can be applied to different parts of the same estate.
Yes. Across 2021 and 2022 GEN engineers migrated 3,900 nodes from ESXi to Proxmox, and have carried on doing that work since. A migration covers planning and sizing, storage and network design, virtual machine conversion, guest driver and boot work on Windows and Linux, cutover scheduling, post-migration tuning and operational training.
No. There is no support contract, no minimum term and no notice period. Customers buy hours at published rates and use them as they are needed. A fixed cost maintenance agreement is available for anyone who prefers a predictable annual figure, but it is optional.
Yes, and GEN run their own data centre estate on it. Proxmox VE provides high availability clustering, live migration, Ceph and ZFS storage, software defined networking and integrated backup through Proxmox Backup Server. It is not the right answer for every workload, and GEN will say so where another platform fits better.
Yes. GEN engineers support VMware vSphere and ESXi, Microsoft Hyper-V, XCP-ng, HPE VM Essentials and bare metal KVM/QEMU alongside Proxmox VE and Proxmox Backup Server, including mixed estates running several of these platforms at once.
Yes. GEN deliver structured Proxmox training at three levels, from day to day operation through to advanced diagnostics, with specialist courses in storage covering LVM, NFS, iSCSI and Ceph, and in networking including SDN. Training can go down to source code level. Courses are delivered remotely or on site across the UK.
Our engineers are UK based and in-house, with no offshore outsourcing: the specialist who takes your case is the specialist who works it, and they hold the production experience to match the equipment in front of them. Risk is assessed before anything is changed, the SAPR method is applied to every fault, and five shifts a day mean an overnight handover is a conversation between two engineers rather than a note left in a ticket. Our AI runs on our own hardware in our own data centres, and it never writes a word you read.
There is no support contract, no minimum term and no notice period. You buy hours at our published rates, use them when you need them, and what you do not use carries over. How GEN support works sets all of it out in full.
