Cloud computing: scope, responsibility and costs
Cloud services can provide computing, storage or a managed platform. Define the job they should perform and work remaining with the business. More technical options do not automatically mean less work or lower costs.
Start with the actual business task
Describe applications, data and work to support. Advice, setup, optimisation and ongoing operation are different assignments. An existing service can remain if suitable.
An office suite or data-only migration differs from infrastructure operation. Define the assignment before ordering capacity.
Compare included management
Identical capacity does not mean identical responsibilities. Check who updates systems, manages access and investigates problems.
| Service type | Also clarify |
|---|---|
| Computing | Operating system, applications and maintenance |
| Storage | Access, backup, retention and export |
| Platform | Supported applications and limits |
| Support | Monitoring, response and permitted interventions |
Plan capacity and usage
Current usage and expected peaks help more than vague size classes. Testing, transfers, logs and backups can also consume resources.
Agree who approves additions and how unused services end. Flexibility does not require unlimited scaling.
Check availability and data responsibility
Define what must keep working after an outage and how data recovers. Data-centre availability does not prove a working business process.
Review processing locations, suppliers and permissions for confidential or personal data. A location label does not replace that assessment.
Introduce services with clear boundaries
A representative pilot can show performance and dependencies. Name access and change owners; approve production interventions before execution.
- Describe. Applications, environment, data and priorities.
- Compare. Equivalent capacity, responsibilities and billing.
- Pilot. Usage, restoration and cost visibility.
- Handover. Document operation, rights, changes and exit.
Control ongoing spending
Compare base fees, consumption and extras. Cost reporting can lag behind usage. A budget alert alone is not a hard spending stop; an effective applicable mechanism must be verified.
| Cost item | Comparison question |
|---|---|
| Setup | Which configuration and documentation are included? |
| Capacity | Fixed commitment or actual consumption? |
| Extra usage | Traffic, backups, logs and retention? |
| Support and exit | Support, export and contract end separate? |
Prepare acceptance and contract end
Record included services, response times and exclusions. A response time does not guarantee repair time.
- Control. Usage and bills are understandable to the business.
- Operation. Owners and change limits are defined.
- Exit. Export, notice periods and deletion are clear.
Frequently asked questions
Must I know technical capacity?
No. Describe applications and usage; known quantities help and uncertain values can be assessed.
Is maintenance automatic?
No. The service and extra support define who maintains systems, applications and access.
Is cloud always cheaper?
No. Consumption, contracts, extras and support determine the total.
Does a budget alert stop spending?
Not automatically. A stop must fit the provider and resources and be verified.
Is a Swiss site enough for data protection?
No. Processing, contracts, access and other parties also matter.
Can I change later?
Check exports, formats, notice periods and costs before signing.
