We maintain your website and workflows.

We agree what Planfold handles and what stays with your team, including who responds to incidents and which decisions remain yours.

Example: operating two instances

Monitoring and maintenance during operation

Your application

Instance A

Accepting requests

Instance B

Accepting requests

Monitoring & updatesBackups as agreed

Monitoring, updates and backups are agreed to suit your applications.

Clarify access and handover from the start.

Monitoring and maintenance during operation Monitoring, updates and backups are agreed to suit your applications.

Who takes care of what?

Tasks are defined before work begins. Both sides know what the maintenance covers.

Your systems

WebsiteAutomations

Agreed maintenance

  • MonitoringSignals and notifications
  • BackupsIntervals and recovery
  • UpdatesMaintenance windows and approvals
  • SupportContact person and availability

Your team decides

On business priorities, content and agreed approvals.

Who handles an incident

We agree who checks alerts, handles the repair and keeps you informed.

  1. Detect

    A system check or your team flags an issue.

  2. Take responsibility

    The agreed contact person assesses the incident.

  3. Resolve & follow up

    Restore operation, check it and keep you informed.

Contact availability and response times are agreed for your operations.

Explore the technical foundations
Run applications
Hosting and, where appropriate, container operations suit the application. Redundancy and scaling are planned according to need.
Prepare recovery
Backup intervals, retention and recovery checks form part of the agreed operational scope.
Control changes
Updates, maintenance windows and approvals are coordinated. Handling unsuccessful changes is also defined.
Document access
We record who manages each account and system. Access rights and the involvement of external services are clarified.

Hand operations over to someone else

We document the accounts, instructions and external services your team or another provider needs to take over operations.

Clarify for handover
  • Access & responsible people
  • Data & export options
  • Configuration & documentation
Your own team
Another operator

How we take over maintenance

We start with your existing systems and agree the next steps.

  1. Review systems

    Record systems, data and access.

  2. Agree scope

    Define tasks and responsibilities.

  3. Prepare takeover

    Coordinate and check changes.

  4. Start maintenance

    Hand over the documentation and record responsibilities.

What setup and maintenance cost

Setup and ongoing scope are described separately.

Takeover & setup

Review existing systems, clarify access and establish the agreed foundations.

Ongoing services

Hosting, monitoring, backups, updates and support as agreed.

Systems, usage and maintenance scope form the basis of your proposal.

Discuss operational scope

What would you like to run?

You can commission a website, a workflow or maintenance for existing systems. We check which connections the work needs.

Project examples from IT operations

Two anonymised examples cover setting up a Kubernetes platform and standardising recurring administration tasks.

Controlled Kubernetes delivery across development, staging, and production

Multiple Kubernetes clusters on vSphere used GitLab CI, ArgoCD, Rancher, Helm and Kustomize. Consistent rollouts made the platform easier to work with.

View implementation story

Standardizing infrastructure operations across Linux and Windows environments

Inventories in GitLab, Ansible and Semaphore replaced improvised administration steps with documented workflows for Linux and Windows.

View implementation story

Questions about operations and ownership

Who manages our access?

This is defined for the relevant accounts and systems. We document responsibilities and the access Planfold needs for the agreed maintenance.

Can someone else take over operations?

Handover requirements are discussed for the project. These include the necessary access, documentation and dependencies on external services.

Can existing systems be taken over?

We review applications, data, access and dependencies. This identifies what maintenance is possible and what preparation is needed.

Are fixed response times included?

Response times and contact availability are explicitly agreed and documented in the operational scope.

Do I need a complete package?

Operational scope is agreed for your project. We clarify which services you need and which tasks remain with your team.

What would you like help maintaining?

Describe your website or automation and the tasks you need support with.

Discuss operations