The problem you're facing
Proxmox is powerful and accessible, which is its trap: a cluster set up quickly, without tested backups, without monitoring, and without an update plan becomes a time bomb. Virtualisation simplified usage, not operations.
Our answer
We design and administer Proxmox clusters in production: architecture (Ceph or ZFS storage, network, quorum), tested backups (Proxmox Backup Server), monitoring, no-downtime upgrades, and hardening.
What LaMeDuSe takes care of
- Proxmox cluster architecture: nodes, storage, network
- Setup or takeover of an existing cluster
- Proxmox Backup Server: encrypted and tested backups
- Monitoring (Prometheus, Grafana) and alerting
- Planned upgrades (no downtime)
- Hardening: access, network, isolation
- Training your teams in Proxmox administration
Our methodology
- 1
Context audit
Understanding of how you use the technology: volumes, constraints, existing setup and goals.
- 2
Tailored architecture
Argued recommendations, adapted to your context rather than copied from a textbook case.
- 3
Implementation
Deployment, configuration and industrialisation by teams who run the same stack in production.
- 4
Skills transfer
Documentation, reviews and knowledge transfer so your teams gain autonomy.
Relevant technologies
Security
Every implementation follows our hardening standards: baseline configuration, managed secrets, monitoring and backups.
Hosting & infrastructure
We operate these technologies on our own European infrastructure: expertise is proven by operations, not by certification.
Maintenance
Version tracking, security watch and support by the teams who administer the same stack every day.
Why LaMeDuSe
Our European cloud runs on Proxmox VE: hundreds of VMs and containers carrying our platforms and our clients'. We know Proxmox in production, under load, in incidents : not just in a lab.
Frequently asked questions
Since Broadcom's VMware licensing changes, Proxmox has become a serious and economical alternative for most uses. We administer both, and we also support VMware-to-Proxmox migrations.
Yes : it's what we use in production. Provided the rules are respected: correct quorum, replicated storage (Ceph or ZFS), tested backups, and monitoring. A well-designed Proxmox cluster is a solid foundation.
Yes: VM inventory, staged migration plan, machine conversion, rehearsal and cutover. Migration can proceed VM by VM to limit risk, with cohabitation during the transition.
Proxmox Backup Server: encrypted incremental backups, deduplication, defined retention, and regular restore tests. Full VM restoration is rehearsed : not just assumed to work.