Skip to content
Let’s talk
Menu
PRACTICAL GUIDANCE

What managed infrastructure includes

“Managed” is only useful when everyone knows what the agreement contains.

Read the guide
ILLUSTRATIVE CONCEPT
01

Separate hosting from the work of running a system

Hosting provides the environment in which a service runs. Infrastructure management describes the agreed work needed to maintain that environment and its supported systems. Buying a server or cloud subscription does not, by itself, explain who updates the application, investigates an alert or restores business data.

Start with an inventory of the services your business depends on, including domains, databases, external providers and account owners. Mark which items are included in the management agreement. Anything outside that list needs an identified owner rather than an assumption that someone else will handle it.

02

Ask what happens after an alert

Monitoring can reveal that a service needs attention. Responding requires a person, access, a procedure and agreed coverage. Ask which events are monitored, how noise is controlled and who receives an alert. Establish the route for a problem reported by a customer when automated monitoring has not detected it.

Distinguish response targets from resolution targets. The first concerns when work begins; the second depends on the fault, access and external dependencies. Skulbyte's coverage hours and any service commitments are agreed explicitly. Do not assume that a general enquiry creates an emergency response engagement.

03

Turn responsibility into named actions

A practical responsibility list states an owner, approver and escalation contact for each task. The exact allocation depends on the provider and contract. The following is an illustrative starting point to discuss, not a default service promise.

  • Your business: prioritises services, authorises access and agrees acceptable maintenance windows.
  • The hosting provider: supplies the contracted hosting facilities and handles incidents within its own scope.
  • The management partner: performs the agreed updates, monitoring review, documentation and incident tasks.
  • The application owner: validates important customer journeys after changes and decides whether behaviour is correct.
04

Define recovery in business terms

Identify which data, application files and configuration are needed to restore a useful service. Agree how much recent data the business could tolerate losing and how long an interruption could be managed. Those objectives guide backup frequency, retention, storage and recovery work; they are not guarantees created by enabling a backup schedule.

Ask for a documented restore procedure and evidence from an agreed test. Check who can access the backups if the main account or server is unavailable. Include the dependencies needed after restoration, such as DNS, credentials and third-party connections.

05

Plan changes and the eventual handover

Separate routine maintenance from major upgrades, migrations and new features. Agree approvals, rollback limits, reporting and external charges. Your business should know where documentation and credentials are held and how another authorised operator could take over. Send Skulbyte your service inventory, current providers and coverage needs. A scoped proposal can then define supported assets, responsibilities and recovery tasks before ongoing management starts.

04 / LET’S MAKE SOMETHING USEFUL

What’s your
next move?

Bring an idea, a problem, or a process that could work better.

+31 20 532 4825

REMOTE COLLABORATION / CLEAR SCOPE / HUMAN CONVERSATION

Let’s start with your idea.

Tell us what you have now, and what you want to change.

Enquiry topic: What managed infrastructure includes

Preparing the enquiry form…

At least 20 characters. Please leave out passwords and sensitive data.

No account needed. No payment required to enquire.