Cloud Service Agreement
Customized Agreements
Cloud Service Agreement
Contract for identified infrastructure, platform, hosted-storage, managed-operations, or related cloud resources through coordinated provisioning, accounts, regions, capacity, quotas, consumption pricing, committed use, service levels, shared security and operational responsibilities, data locations, backups, recovery, deprecation, migration, export, retention, and deletion across six substantive schedules.
Also called: cloud services contract, iaas agreement, managed cloud services agreement.
What you walk away with
A clean multi-page PDF and DOCX after you finish — not a web-form dump. Preview the document before you pay.
- PDF export
- DOCX export
- E-sign included
- No subscription
Electronic contracting, taxes, privacy, security, incidents, data transfers, export controls, regulated workloads, warranties, indemnity, liability, suspension, retention, and deletion duties vary by governing law, parties, resources, data, regions, and actual operations.
Jurisdiction details
See how this document starts in your state
Choose the state where the document will be used. The state page shows the maintained coverage level, local-rule limits, and a builder link with the canonical state code already selected.
When this fits
Use this document when…
- Virtual infrastructure, networking, compute, or related IaaS resources
- Managed databases, containers, runtimes, serverless functions, or other PaaS services
- Hosted object, file, block, archive, or backup storage
- Managed cloud operations with specifically assigned configuration, patching, monitoring, backup, or incident tasks
Before you start
Information you will need
- Provider, customer, selected service models, resources, regions, zones, accounts, projects, environments, governing jurisdiction, and term
- Provisioning, capacity, scaling, metrics, limits, quotas, customer configurations, administrators, acceptable use, dependencies, and acceptance
- On-demand rates, committed use if selected, consumption, overages, invoices, taxes, credits, budgets, alerts, and enforceable spending controls if supported
- Availability formula, covered resources, maintenance, exclusions, support, severity, response, monitoring, service credits, fee base, cap, and evidence
- Shared responsibility for infrastructure, network, identity, encryption, keys, patching, logging, backups, recovery, incidents, customer data, images, software, regions, subprocessors, IP, migration, retention, deletion, and signatures
What you receive
- One customized Cloud Service Agreement
- Schedule A cloud service and resource inventory
- Schedule B pricing, usage, commitments, overage, credit, and spending-control record
- Schedule C availability, maintenance, support, exclusion, measurement, and credit record
- Schedule D provider-customer shared-responsibility matrix
- Schedule E data, region, replica, subprocessor, export, retention, and deletion record
- Schedule F suspension, resource change, deprecation, migration, termination, and exit record
- PDF and DOCX export with electronic signature capability
Document questions
Questions about this document
What is a Cloud Service Agreement?
Contract for identified infrastructure, platform, hosted-storage, managed-operations, or related cloud resources through coordinated provisioning, accounts, regions, capacity, quotas, consumption pricing, committed use, service levels, shared security and operational responsibilities, data locations, backups, recovery, deprecation, migration, export, retention, and deletion across six substantive schedules.
How do I create a Cloud Service Agreement?
Virtual infrastructure, networking, compute, or related IaaS resources; Managed databases, containers, runtimes, serverless functions, or other PaaS services; Hosted object, file, block, archive, or backup storage
What should a Cloud Service Agreement include?
Provider, customer, selected service models, resources, regions, zones, accounts, projects, environments, governing jurisdiction, and term; Provisioning, capacity, scaling, metrics, limits, quotas, customer configurations, administrators, acceptable use, dependencies, and acceptance; On-demand rates, committed use if selected, consumption, overages, invoices, taxes, credits, budgets, alerts, and enforceable spending controls if supported; Availability formula, covered resources, maintenance, exclusions, support, severity, response, monitoring, service credits, fee base, cap, and evidence; Shared responsibility for infrastructure, network, identity, encryption, keys, patching, logging, backups, recovery, incidents, customer data, images, software, regions, subprocessors, IP, migration, retention, deletion, and signatures
Special situations
- IaaS, PaaS, hosted storage, and managed operations use different layer-by-layer responsibility paths rather than one generic service description.
- Budget notices become hard spending caps only where the selected service actually supports enforcement.
- Snapshots, replication, backups, and disaster recovery remain separate commitments with actual scope, retention, testing, and supported recovery objectives.
- Every primary, replica, backup, log, metadata, support-access, and subprocessor copy is reconciled with selected region and lifecycle terms.
Frequently asked questions
How is this different from a SaaS Agreement?
It focuses on cloud infrastructure, platform, storage, configurations, meters, regions, backups, recovery, and shared operational layers rather than one end-user software application.
Does the provider manage every layer?
No. The responsibility matrix assigns infrastructure, operating system, runtime, code, network, identity, encryption, keys, patches, logs, backups, and incident tasks.
Can it include committed-use pricing?
Yes. The conditional path records resources, regions, duration, payment, usage application, discount, shortfall, rollover, modification, transfer, termination, and credits.
Does it guarantee restoration?
No. It records actual backup and recovery services, scope, frequency, retention, testing, restore process, and supported recovery objectives.
Can migration assistance be included?
Yes. The selected path defines resources, data, images, configurations, source, destination, tools, transfer, downtime, validation, dependencies, security, fees, and acceptance.
Related documents
Not legal advice
Locke Direct helps structure documents and workflows. It does not replace a qualified lawyer for complex, unusual, or high-risk situations.
Last reviewed August 2, 2026.