Lifecycle and patch management
We assess updates and security advisories, check dependencies between Proxmox, Ceph, backup and hardware, and plan the maintenance sequence. Tests, approvals and post-update checks are documented.
PROXMOX IN ENTERPRISE ENVIRONMENTS Your infrastructure.
Your infrastructure.
Our platform operations.
A management platform and operations team for your Proxmox environment.
Through our management platform, we take ongoing operational responsibility for more than 10,000 systems. Monitoring, maintenance and incident handling belong together. We agree which tasks we take on for your environment.
Discuss your operating modelSYSFACTSPLATFORM OPERATIONS
YOUR PROXMOX INFRASTRUCTURE
Site A
Site B
Further sites
THE SHARED OPERATING LAYER
Sysfacts management platform
Monitoring
Updates & patches
Backup & restore
Automation
THE SYSFACTS OPERATIONS TEAM
Assesses alerts.
Resolves incidents. Implements changes.
EXPERIENCE IN LIVE OPERATIONS+ 10,000 systems.
+ 10,000 systems.
Under our responsibility.
We manage them continuously through our management platform, with a team that knows the environment and looks after it.
SYSFACTS PLATFORM OPERATIONS
PLATFORM AND TEAM
One coordinated operation.
Our management platform provides a common basis for support. The Sysfacts team assesses alerts, handles incidents and implements agreed changes. Technical tools and operational responsibility are part of the same service.
Your IT team retains control. We define scope, approvals and escalation routes together.
- 01 · DETECT
Record system status and relevant alerts.
- 02 · ASSESS
Assess impact and prioritise the response.
- 03 · ACT
Handle incidents or implement agreed changes.
- 04 · FOLLOW UP
Check the result and document the status.
TECHNICAL OPERATIONS
What we take on.
Scope depends on your environment and team. Platform operations, guest operating systems and applications are clearly distinguished in the agreement.
Backup and recovery
We monitor backup jobs, resolve failures and test agreed recovery procedures. Retention and separate backup copies are aligned with your requirements.
Monitoring and response
We define measurement points, thresholds and alert routes. For each relevant alert, we agree who takes ownership and how it is handled.
Automation and changes
We standardise recurring tasks and document configurations. Changes are assessed, agreed and implemented with a clear record.
SERVICE AND VENDOR SUPPORT
We agree service hours, response times, maintenance windows and escalation routes to match your needs. A Proxmox subscription and Sysfacts operational services are different services. We align them.
THE RIGHT OPERATING MODELWho looks after
Who looks after
what?
The infrastructure and decisions about it remain yours. You choose how far Sysfacts supports technical operations.
Your team takes over.
Your experts run the environment. We document it, train the team and provide agreed support for specialist topics, maintenance or version upgrades.
We complement your IT team.
We take on defined tasks such as cluster maintenance or resolving backup failures. Responsibilities and handovers between teams are documented.
Sysfacts runs the platform.
We continuously manage the agreed infrastructure components. Your IT team controls requirements and approvals. Contacts, reports and coordination are part of the agreement.
A SINGLE PROJECT
Is the next upgrade approaching?
You can commission a cluster upgrade without handing over ongoing operations. We assess the starting point, plan the steps and carry out the upgrade with your IT team.
Upgrade Proxmox and Ceph clustersBEFORE TAKING OVER OPERATIONSWhen an incident occurs,
When an incident occurs,
responsibility is clear.
We document which systems we manage, when we are available and who acts when something fails. Platform monitoring does not automatically include round-the-clock support.
- Alerts and response
- Who receives alerts and incident reports? We agree reporting channels, service hours, response times and escalation outside those hours. A response time is not a guaranteed resolution time.
- Platform and applications
- We name the owners of clusters, storage, networking, guest operating systems and applications. We also agree approvals and handovers with your IT team and application partners.
- Recovery
- We agree who initiates, performs and validates recovery. Together, we define recovery time and data-loss objectives, as well as test scope and frequency.
GETTING STARTEDTaking on
Taking on
an existing environment.
We also support platforms we did not build. Before taking over, we assess their condition and establish what work is still needed.
- 01
Assess the estate
Record versions, cluster health, capacity, backup and documentation. Identify outstanding risks.
- 02
Prepare for support
Connect the environment to our management platform. Set up access, monitoring and alert routes. Agree services, responsibilities and service hours.
- 03
Begin operations
Check prerequisites together, take over tasks and start regular coordination.
A FUTURE HANDOVER IS ALSO DEFINED
Your environment remains transferable.
At onboarding, we agree how the environment can be handed to your IT team or another provider: documentation, configurations, administrative access and disconnection from our management platform. Rights and dependencies for automation are clarified separately. The scope, effort and timeline of a future handover are recorded.
YOUR OPERATIONSWhere does your team
Where does your team
need support?
We clarify which tasks you want to delegate and what is still needed before we take over. This includes the condition of the environment, access and interfaces with your team. Scope and service hours are then agreed.
Discuss operational support Still planning the move from VMware? Architecture, implementation and operations