Skip to main content

Help us improve the Digital Marketplace - send your feedback

Google Cloud EMEA Limited

Media Services (Live Stream, Transcoder)

APIs for live encoding, batch media conversion, and dynamic ad insertion (Video Stitcher).

Features

  • YouTube infrastructure; global delivery, low latency.
  • Transcodes live, on-demand video; formats for all devices.
  • AI/ML automates metadata, moderation; personalized viewer recommendations.
  • Robust security, DDoS protection, content encryption; Cloud Armor compliance.
  • Video Stitcher API; optimized stream monetization; dynamic ad insertion.
  • Service Extensions; customizable logic, custom code execution at edge.
  • Scalable Cloud Rendering; thousands of cores for massive jobs.
  • Real-time logging, metrics; observability, cache hits, security.
  • Deeply tiered edge caching; industry-leading offload rates.
  • Modern protocols (QUIC, TLS 1.3); reduce latency; better experience.

Benefits

  • Deliver high-quality, low-latency live; global on-demand video streams.
  • Quickly convert, package video/audio files for optimized on-demand streaming.
  • Live Stream API delivers smooth, high-quality live stream experiences.
  • Transcoder API converts files for optimized streaming; broadens audience reach.
  • Ensure content compatibility across the widest possible range of devices.
  • Adaptive bitrate streaming ensures buffer-free, high-quality playback.
  • Automatically create multiple video files; various resolutions, bitrates.
  • Slash complex VFX rendering from days to hours; faster creation.
  • Automate video analysis, metadata generation; content becomes fully searchable.
  • Optimize costs; pay only for necessary resources using flexible pricing.

Pricing

Service documents

Request an accessible format
If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at ps-frameworks@google.com. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 15

Service ID

6 6 4 4 9 6 7 6 8 3 8 0 8 7 7

Contact

Google Cloud EMEA Limited UK Public Sector Team
Telephone: cloud.google.com
Email: ps-frameworks@google.com

About your service

Service categories

PaaS

Integration and Orchestration

  • Integration software

Service scope

Service constraints
VPC Service Controls can restrict access to required storage services.
System requirements
  • Windows 8.1+, macOS 10.12+, or supported Linux OS required.
  • X86\_64 processor architecture needed for client tools.
  • Basic SDK/CLI needs minimum 200MB storage.
  • Cloud SDK requires Python 3.8 to 3.12.
  • Google Cloud CLI 345.0.0+ required for Media CDN.
  • Enable Network Services API; Certificate Manager API must be enabled.
  • Compute Engine supports many Linux, Windows Server OS.
Cloud deployment model
Public cloud

User support

Email or online ticketing support
Yes
Support response times
Initial response times

Standard Support
P2 cases: 4 hours
P3 cases: 8 hours
P4 cases: 8 hours

Enhanced Support
P1 cases: 1 hour
P2 cases: 4 hours
P3 cases: 8 hours
P4 cases: 8 hours

Premium Support
P1 cases: 15 minutes
P2 cases: 2 hours
P3 cases: 4 hours
P4 cases: 8 hours
User can manage status and priority of support tickets
Yes
Online ticketing support accessibility
EN 301 549
Phone support
Yes
Phone support availability
24 hours, 7 days a week
Web chat support
Yes
Web chat support availability
24 hours, 7 days a week
Web chat support accessibility standard
EN 301 549
Web chat accessibility testing
Google Accessibility Rating (GAR): GAR is Google's internal standard for measuring a software product's level of technical accessibility. It is used to evaluate products and features during development and testing before launch.

GAR Assessment: The GAR assessment process involves creating a GAR self-assessment sheet, defining use cases, and performing accessibility tests. If the product's score is not GAR 4, the issues flagged during testing need to be fixed.

Accessibility Conformance Report: https://belonging.google/accessibility-conformance-reports/
Onsite support
No
Support levels
Basic Support
Billing support.

Standard Support
Recommended for workloads under development, kickstart your cloud journey with unlimited access to tech support. Troubleshoot, test, and explore.
Minimum spend of $29.00
or -
3% of monthly Cloud charges.

Enhanced Support
Designed for workloads in production, with fast response times and additional services to optimize your experience with high-quality, robust support.
Minimum spend of $100.00
or -
10% of monthly Cloud charges for the first $0 - $10K
7% of monthly Cloud charges from $10K - $80K
5% of monthly Cloud charges from $80K - $250K
3% of monthly Cloud charges over $250K

Premium Support
Designed for enterprises with critical workloads, with the fastest response time, Customer Aware Support, and Technical and Accounts Manager Services.
Minimum spend of $15,000.00
or -
10% of monthly Cloud charges for the first $0 - $150K
7% of monthly Cloud charges from $150K - $500K
5% of monthly Cloud charges from $500K - $1M
3% of monthly Cloud charges over $1M

Charges will be at least the minimum charge of $15,000.00 or the result of the calculation, whichever is higher.
Support available to third parties
Yes
AI chatbot
Yes

Onboarding and offboarding

Getting started
Google Cloud offers a comprehensive set of onboarding services and resources for new users, ranging from free financial credits and always-free usage to structured learning paths, guided technical workshops, and direct support setup.

Additional Services are available from the Google Professional Services Organisation (PSO) or via our vast network of accredited Delivery Partners.
Service documentation
Yes
Documentation formats
  • HTML
  • PDF
  • Other
Other documentation formats
API
End-of-contract data extraction
Users can extract their data using a collection of readily available tools, please see below for an overview:

Google Cloud Migration Services:

Storage Transfer Service (STS):
A fully managed, highly scalable service for the bulk transfer of unstructured or semi-structured data (files, objects) into Cloud Storage.
Primary tool for online data movement from other cloud providers, on-premises file systems, and web-accessible sources.
Transfer Appliance (TA):
A physical, high-capacity storage device for offline data transfer, especially for massive datasets (terabytes to petabytes) when network bandwidth is limited.

NOTE: Customers can apply for a free data egress costs when migrating away from Google Cloud.
End-of-contract process
Google Cloud End-of-Contract Data Process:

1. Data Export and Migration Period: The customer must export any data they wish to retain, utilizing standard GCP tools and APIs.Migration Support: Google offers Migration Period (at least 30 days, or longer if technically necessary) during which the customer can move their workloads and production data out of the platform.

2. Data Deletion Timeline: Once the contract expires or the customer issues a final deletion instruction, Google initiates its formalized data deletion pipeline.PhaseDurationProcess and MechanismRecovery PeriodUp to 30 days post-termination.A grace period where the customer may still be able to retrieve recently deleted data.Logical DeletionUp to ~2 months after the recovery period.Remaining customer data is purged from active systems using Cryptographic Erasure (destroying encryption keys).Final Backup ExpirationMaximum of 180 days. Customer data is removed from all long-term disaster recovery and backup snapshots.

3. Post-Termination Assurance Final Deletion Guarantee: Google commits to deleting all Customer Data within a maximum of 180 days from the end of the term, unless legally required to retain it.Physical Sanitization: The data is guaranteed to be irrecoverable through secure media sanitization and the physical destruction (shredding/crushing) of retired hardware, aligning with NIST SP 800-88 standards.This entire process is contractually backed.
Documentation accessibility standard
EN 301 549

Using the service

Web browser interface
Yes
Using the web interface
Cloud APIs are exposed as network API services to customers. Each Cloud API typically runs on one or more subdomains of googleapis.com, such as pubsub.googleapis.com, and provides both JSON HTTP and gRPC interfaces to clients over public internet and Virtual Private Cloud (VPC) networks. Clients can send HTTP and gRPC requests to Cloud API endpoints directly or by using client libraries.

Limitations:
- Requires Application Credentials to authenticate to the API interface during initialization of Client Libraries.
Web interface accessibility standard
EN 301 549
Web interface accessibility testing
Google Accessibility Rating (GAR): GAR is Google's internal standard for measuring a software product's level of technical accessibility. It is used to evaluate products and features during development and testing before launch.

GAR Assessment: The GAR assessment process involves creating a GAR self-assessment sheet, defining use cases, and performing accessibility tests. If the product's score is not GAR 4, the issues flagged during testing need to be fixed.

Accessibility Conformance Report: https://belonging.google/accessibility-conformance-reports/
API
Yes
What users can and can't do using the API
Cloud APIs are exposed as network API services to customers. Each Cloud API typically runs on one or more subdomains of googleapis.com, such as pubsub.googleapis.com, and provides both JSON HTTP and gRPC interfaces to clients over public internet and Virtual Private Cloud (VPC) networks. Clients can send HTTP and gRPC requests to Cloud API endpoints directly or by using client libraries.

Limitations:
- Requires Application Credentials to authenticate to the API interface during initialization of Client Libraries.
API automation tools
  • Terraform
  • Other
Other API automation tools
  • GCloud SDK
  • Client Libraries
API documentation
Yes
API documentation formats
  • Open API (also known as Swagger)
  • HTML
  • PDF
  • Other
Command line interface
Yes
Command line interface compatibility
  • Linux or Unix
  • Windows
  • MacOS
  • Other
Using the command line interface
The Google Cloud CLI (gcloud) is a management and automation tool used for the platform's control plane, not a user interface for data manipulation or graphical interactions.

Can Do: Provision, configure, and delete cloud resources (VMs, networks, databases); manage IAM roles; run BigQuery queries; and execute automation scripts (gsutil, gcloud projects).

Cannot Do: View graphical dashboards; perform real-time, low-latency application data entry; or complete administrative tasks that require web-based verification (e.g., strong MFA recovery).

Scaling

Independence of resources
Google Cloud Platform (GCP) guarantees resource availability and ensures workload demands are not negatively affected by other customers primarily through its fault-tolerant physical infrastructure architecture and a layered system of virtual and logical isolation and resource management mechanisms.
Usage notifications
Yes
Usage reporting
  • Email
  • Other
Other usage reporting
Reporting dashboard
Optimising consumption
Yes
Automatic scaling
Yes

Analytics

Infrastructure or application metrics
Yes
Metrics types
  • CPU
  • Disk
  • HTTP request and response status
  • Memory
  • Network
  • Number of active instances
  • Other
Other metrics
  • Service health
  • Storage
  • Usage statistics
Reporting types
  • API access
  • Real-time dashboards
  • Regular reports
  • Reports on request
Resource tagging
Yes
FOCUS resource tagging
Yes

Resellers

Supplier type
Not a reseller

Staff security

Staff security clearance
Conforms to BS7858:2019
Government security clearance
Developed Vetting (DV)

Asset protection

Knowledge of data storage and processing locations
Yes
Data storage and processing locations
  • United Kingdom
  • European Economic Area (EEA)
  • Other locations
User control over data storage and processing locations
Yes
Datacentre security standards
Complies with a recognised standard (for example CSA CCM version 4.0)
Penetration testing frequency
At least every 6 months
Penetration testing approach
‘IT Health Check’ performed by a CHECK service provider
Protecting data at rest
  • Physical access control, complying with CSA CCM v4.0
  • Physical access control, complying with SSAE-18 / ISAE 3402
  • Physical access control, complying with another standard
  • Encryption of all physical media
  • Scale, obfuscating techniques, or data storage sharding
  • Other
Other data at rest protection approach
Encryption Algorithm: Google uses the AES algorithm for data at rest. This is typically AES-256 and, in most cases for storage systems like Cloud Storage, utilizes Galois/Counter Mode (GCM).

Layered Protection: Data is often encrypted at multiple layers.

Key Management: Encryption keys are managed by Google's hardened key management systems.

Per-Chunk Keys: Each data chunk is encrypted with an individual, unique Data Encryption Key (DEK), no two chunks will have same key.

Envelope Encryption: DEKs are themselves encrypted (wrapped) by a set of higher-level keys and stored separately from the data.

Compliance: Google uses the FIPS 140-2 in production environment.
Data sanitisation process
Yes
Equipment disposal approach
Complying with a recognised standard, for example CSA CCM v4.0, CAS (Sanitisation) or ISO/IEC 27001
Data sanitisation type
  • Deleted data can’t be directly accessed / Cryptographic Erasure
  • Data Erasure
  • Explicit overwriting of storage before reallocation / Secure Erase
  • Physical Destruction / Hardware containing data is completely destroyed

Backup and recovery

What’s backed up
  • VM
  • Files
  • Application
  • Data
Backup controls
Users control backups in Google Cloud by creating backup plans and associating them with specific resources like Cloud SQL or Compute Engine instances. Control is managed through backup rules, where users define the frequency (hourly, daily, weekly, or monthly) and a start window of at least six hours.

Additionally, users determine retention periods, ensuring data is kept for a specific duration before automatic deletion. Security is managed by directing backups to specific backup vaults, which dictate data residency and encryption (CMEK). While primarily automated, these plans support both scheduled and on-demand execution to meet specific recovery objectives.
Datacentre setup
Multiple datacentres with disaster recovery
Scheduling backups
Users schedule backups through a web interface
Backup recovery
Users can recover backups themselves, for example through a web interface
Backup and recovery
Yes
RPO/RTO
Yes

Data-in-transit protection

Data protection between buyer and supplier networks
  • Private network or public sector network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Other
Other protection between networks
All communication from an end user (client application, browser, etc.) over the internet to Google Cloud services is secured using standard protocols:

Transport Layer Security (TLS): Requests sent over HTTPS, HTTP/2, or HTTP/3 are secured with TLS encryption.

Google Front End (GFE): The GFE system terminates the TLS connections from the internet. It uses BoringSSL (Google's open-source, FIPS 140-3 Level 1 validated implementation of the TLS protocol) to handle encryption and decryption.

Public Certificates: The data is secured using HTTPS with a certificate from a web (public) certificate authority.
Data protection within supplier network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Other
Other protection within supplier network
Virtual Network Encryption (IP Layer): Google Cloud's virtual network automatically encrypts, integrity-protects, and authenticates private IP traffic between virtual machines (VMs).

Application Layer Transport Security (ALTS): This is Google's own service-to-service security protocol, used for Remote Procedure Calls (RPCs) between services running in Google's infrastructure.

Authentication and Key Exchange: ALTS performs a handshake to authenticate the identities of the communicating services and compute a shared traffic key.

Encryption: Data is encrypted in transit using the shared traffic key, typically employing AES-128-GCM encryption. Encryption in ALTS is provided by BoringSSL or PSP (Private Security Protocol).

Availability and resilience

Guaranteed availability
Google Cloud Platform (GCP) provides a detailed Service Level Agreement (SLA) for each of its core services, guaranteeing a Monthly Uptime Percentage (SLO). This uptime guarantee varies depending on the specific service, the service tier, and the customer's architectural configuration (e.g., single-zone vs. multi-zone deployment).

If GCP fails to meet the guaranteed SLO, the customer is eligible to receive Financial Credits applied to future bills, which serves as the customer's sole and exclusive remedy for any failure to meet the SLO.

Key SLA Uptime Guarantees (SLOs)
The guaranteed uptime is expressed as a Monthly Uptime Percentage. "Downtime" is typically defined as a high rate of HTTP 5XX server-side errors (usually 1% or 5% or 10% Error Rate, depending on the service) over a consecutive period.
Approach to resilience
Google Cloud Platform (GCP) service resilience is guaranteed through a deep, layered strategy that combines global physical infrastructure redundancy with automated, data-driven system management and security protections to ensure continuous operations and rapid recovery.

The GCP Datacentre resilience framework uses geographic distribution to eliminate single points of failure, adhering to the principle of "disaster avoidance".

Regions and Zones: GCP's global infrastructure is segmented into Regions (geographically separate areas). Each region contains multiple Zones, which are independent failure domains with their own power, cooling, and networking.

Fault Tolerance: Deploying application components across multiple zones within a region protects against localized failures like power loss or network partitioning.

Disaster Recovery (DR): Deploying across multiple regions provides the highest level of aggregate resilience against large-scale, region-wide disasters (e.g., natural disasters).

Same Infrastructure as Google: GCP leverages the same robust, self-healing internal architecture that powers high-traffic services like Google Search and Gmail.
Outage reporting
Official Status Dashboards
GCP uses dedicated, centralized dashboards to provide real-time status and historical information:

Google Cloud Service Health (Public Dashboard):
This is the main public status page, which provides status information on services that are part of Google Cloud.

It lists widespread incidents that affect multiple customers and services.

Status can be checked by product and location (regions and multi-regions).

It maintains a record of disruptions and outages for up to five years.

Identity and authentication

User authentication needed
Yes
User authentication
  • Multi-Factor Authentication (MFA)
  • Public key authentication (including by TLS client certificate)
  • Identity federation with existing provider (for example Google Apps)
  • Limited access network (for example PSN)
  • Dedicated link (for example VPN)
  • Username or password
  • Other
Other user authentication
Google Cloud secures various principals through specialized authentication:

Human Users: Protected by MFA, physical Security Keys, and Context-Aware Access, which verifies identity, location, and device health.

Service Accounts: Utilizes Workload Identity Federation and short-lived tokens to eliminate sensitive, long-lived keys, adhering to the Principle of Least Privilege.

Application Security: Identity-Aware Proxy (IAP) centralizes access control for apps and VMs by verifying identity and context without traditional VPNs.

Everything is tracked via Cloud Audit Logs, providing a comprehensive trail for security and compliance. This multi-layered approach ensures robust, identity-centric protection.
Access restrictions in management interfaces and support channels
Google Cloud secures resources using Identity and Access Management (IAM) and the Principle of Least Privilege, ensuring users hold only essential permissions. For the management interface, context-aware access and VPC Service Controls guard against unauthorized entry and data exfiltration.

Access by Google personnel is strictly limited to business-critical justifications. Through Access Transparency and Access Approval, customers gain real-time visibility and the final say over when Google staff can view their data. This combination of granular identity controls and transparency logs ensures robust data sovereignty and security across all channels.
Access restriction testing frequency
At least every 6 months
Management access authentication
  • Multi-Factor Authentication (MFA)
  • Public key authentication (including by TLS client certificate)
  • Identity federation with existing provider (for example Google Apps)
  • Limited access network (for example PSN)
  • Dedicated link (for example VPN)
  • Username or password
  • Other
Description of management access authentication
Google Cloud secures access through tailored authentication for humans and machines:

Humans: Use MFA, physical Security Keys, and Context-Aware Access (Zero Trust) to verify identity, device health, and location.

Service Accounts: Applications use Workload Identity Federation to eliminate risky long-lived keys, opting instead for short-lived tokens and impersonation.

Applications: Identity-Aware Proxy (IAP) acts as a gatekeeper, verifying identity and context for web apps and VMs.

All activity is captured in Cloud Audit Logs for governance. This multi-layered approach ensures robust, auditable security across all principal types.
Devices users manage the service through
  • Dedicated device on a segregated network (providers own provision)
  • Dedicated device on a government network (for example PSN)
  • Dedicated device over multiple services or networks
  • Any device but through a bastion host (a bastion host is a server that provides access to a private network from an external network such as the internet)
  • Directly from any device which may also be used for normal business (for example web browsing or viewing external email)

Audit information for users

Access to user activity audit information
Users have access to real-time audit information
How long user audit data is stored for
User-defined
Access to supplier activity audit information
Users have access to real-time audit information
How long supplier audit data is stored for
User-defined
How long system logs are stored for
User-defined

Security governance

Named board-level person responsible for service security
Yes
Security governance certified
Yes
Security governance standards
  • CSA CSM version 4.0
  • ISO/IEC 27001
  • Other
Other security governance standards
Supplier control
Information security policies and processes
Google Cloud’s security strategy is a centralized, automated framework managed by the Office of the CISO. Enforcement relies on a defense-in-depth approach across two primary pillars:

1. Policy Enforcement
Identity & Resource Control: Utilizing the Principle of Least Privilege (PoLP) via IAM, Google employs Policy Intelligence (Recommender/Simulator) to automate permission adjustments and test changes safely.

Network Security: Cloud Armor enforces Layer 7 protections at the edge.

Operational Automation: Pre-configured Security Blueprints ensure "secure-by-default" deployments, while automated workflows (Cloud Functions) revert unauthorized configuration changes.

2. Reporting and Accountability
Centralized Visibility: Security Command Center (SCC) provides real-time vulnerability scanning and compliance scores (e.g., ISO, NIST).

Audit & Transparency: Cloud Audit Logs track all user activity, while Access Transparency provides near real-time logs of Google personnel actions.

Compliance Access: The Compliance Reports Manager offers on-demand third-party audit reports (SOC, ISO), ensuring validated evidence for auditors.

This structure ensures that technical risks are translated into business context for board-level oversight while maintaining continuous, automated compliance.

Operational security

Configuration and change management standard
Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
Configuration and change management approach
Google manages configuration through Infrastructure as Code (IaC) and GitOps (e.g., Config Sync), enabling self-healing and drift prevention. By prioritizing immutability, Google replaces resources instead of patching them to maintain a stable "source of truth."

Change management is automated via CI/CD pipelines, requiring peer reviews and utilizing canary deployments for safe rollouts. Organization Policies provide centralized guardrails, while Cloud Audit Logs record every action for total traceability. This integrated approach ensures that all changes are codified, reviewed, and auditable, maintaining high security and reliability across the platform.
Vulnerability management type
Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
Vulnerability management approach
Google enforces security via automation and Principle of Least Privilege. Key tools include IAM Recommender, Cloud Armor, and Security Blueprints to ensure secure-by-default configurations.

Threats are identified using Security Command Center (SCC), which monitors logs for anomalies and utilizes Mandiant-enriched intelligence. The response process focuses on minimizing "dwell time" through automated triage and containment playbooks.

Transparency is maintained through Access Transparency logs and post-incident reports, while the CISO provides executive oversight, ensuring continuous improvement based on audit data.
Protective monitoring type
Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
Protective monitoring approach
Google Cloud’s protective monitoring utilizes centralized telemetry aggregation to detect threats in real-time. Systems like Event Threat Detection and Security Health Analytics scan for Indicators of Compromise (IoCs), misconfigurations, and behavioral anomalies, prioritized by Google Threat Intelligence.

Incident response focuses on minimizing dwell time through automated alerts and SOAR playbooks for rapid containment. Response teams adhere to strict SLOs for triage, isolation, and eradication.

Security Command Center provides unified reporting, while Access Transparency ensures auditable Google personnel activity. Detailed post-mortems drive continuous improvement, refining detection rules to prevent future compromises.
Incident management type
Complies with a recognised standard, for example, CSA CCM v4.0 or ISO/IEC 27035:2011 or SSAE-18 / ISAE 3402
Incident management approach
Google's incident management leverages SRE principles and automation to minimize "dwell time." Detection is driven by machine learning, Mandiant threat intelligence, and Security Command Center (SCC), which identifies misconfigurations and behavioral anomalies.

Once triggered, response teams utilize SOAR playbooks for rapid containment—isolating systems and revoking credentials—guided by strict SLOs. Accountability is maintained through Access Transparency logs, detailing Google personnel activity, and comprehensive post-mortems. These lessons are fed back into security blueprints, ensuring continuous platform hardening and a faster Mean Time to Respond (MTTR).
Post-quantum cryptography secure
Yes

Secure development

Approach to secure software development best practice
Independent review of processes (for example CESG CPA Build Standard, ISO/IEC 27034, ISO/IEC 27001 or CSA CCM v4.0)

Separation between users

Virtualisation technology used to keep applications and users sharing the same infrastructure apart
Yes
Who implements virtualisation
Supplier
Virtualisation technologies used
KVM hypervisor
How shared infrastructure is kept separate
GCP relies on KVM virtualization to guarantee strict separation and isolation between all customers.

Each organization runs in a dedicated VM with its own resources. Isolation is enforced through:

KVM Hypervisor: Secures tenants on shared physical hardware.

Logical Controls: VPCs and IAM policies restrict cross-tenant network and resource access.

Hardware Offload: Custom chips prevent "noisy neighbor" performance interference.

Energy efficiency

Energy-efficient datacentres
Yes
Description of energy efficient datacentres
ISO 50001 Certification: Google's EU-owned data centers have developed, implemented, and maintain an Energy Management System (EnMS) certified to ISO 50001 standards. This certification demonstrates a commitment to efficient energy management.

Pricing

Discount for educational organisations
Yes
Free trial available
Yes
Description of free trial
Google Cloud’s Free Trial provides $300 in credit for 90 days plus an "Always Free" tier for 20+ services. This risk-free program allows users to evaluate 100+ products without automatic charges; billing only starts if you manually upgrade. It’s ideal for hands-on learning and testing cloud solutions.
Link to free trial
https://cloud.google.com/free?e=48754805

Discount

Provide your minimum discount applicable to your baseline prices
0%

Formula for calculating price of your services

Formula for calculating price of your services

Which of the core deployment models you intend to offer

Public Cloud

Public Cloud - Formula for calculating price of your services


Total Cost
The Total Cost for a buyer's call off requirement in a Public Cloud Deployment
=
Baseline Pricing
Google Cloud's pricing for Lot 1a is explicitly detailed in the **Pricing Document** attached to this service listing on the Crown Commercial Service (CCS) Digital Marketplace.

Given the dynamic, consumption-based nature of our platform, the Pricing Document incorporates Google Cloud’s publicly available list price, accessible at **[https://cloud.google.com/pricing]**. This ensures customers always utilize the most current and transparent rates for all infrastructure services, including Compute Engine, Cloud Storage, and Kubernetes Engine.

The Pricing Document further clarifies:
1. **Cost Mechanisms:** The specific unit costs (e.g., per vCPU/hour, per GB/month).
2. **Specific product pricing.** Detailed information on product pricing
3. **Calculator:** A recommendation to use the **Google Cloud Pricing Calculator** to model specific scenarios based on these baseline rates. https://cloud.google.com/products/calculator

All prices listed are maximum framework rates, from which further discounts may be deducted.
Baseline Pricing - Web link
https://cloud.google.com/pricing
-
Minimum Discounting
0%
+
Onboarding Activity
Onboarding costs may vary based on your specific requirements, please confirm with suppliers during the clarification process
+
Additional sources of cost
For G-Cloud 15 Lot 1a (Cloud Hosting), there are **no separate onboarding or setup fees** to provision a Google Cloud Platform account. Access to the platform is provided on a self-service basis, and costs are incurred solely based on the consumption of services (e.g., compute, storage) as detailed in the Pricing Document.

However, customers should distinguish between "Platform Access" and "Onboarding Services":

1. **Platform Access (Lot 1a):** Creating an Organisation/Billing Account is free of charge. New customers may also be eligible for promotional credits (e.g., Free Tier) to facilitate initial testing and configuration.
2. **Onboarding Services (Lot 3):** If the customer requires hands-on technical assistance—such as migration support, architecture design, or "landing zone" configuration—this is classified as **Cloud Support**. These services are not included in the Lot 1a unit rates.

Customers requiring professional services for onboarding must refer to Google’s separate **Lot 3** Service Definition ("Google Cloud Professional Services") or engage via an authorized Google Cloud Partner listed on the framework. All professional services are charged according to the Rate Card attached to the respective Lot 3 listing.
-
Additional sources of cost reduction
Google Cloud offers multiple mechanisms to reduce Total Cost of Ownership (TCO) directly within this deployment model. These savings are achieved through both automated billing logic and active management features:

1. **Granular Consumption:** Per-second billing enables buyers to pay only for the exact resources consumed, eliminating the waste associated with over-provisioned hardware or hourly rounding.
2. **Commitment Discounts:** Buyers can access **Committed Use Discounts (CUDs)**, exchanging a 1-year or 3-year resource commitment for significant price reductions (up to 57%) compared to on-demand rates, with no upfront fees required.
3. **Sustained Use Discounts:** For Compute Engine, automatic discounts are applied to resources running for a significant portion of the billing month, requiring no manual intervention.
4. **Spot Instances:** For fault-tolerant workloads (e.g., batch processing), Spot VMs offer savings of up to 91% compared to standard instances.
5. **Intelligent Rightsizing:** The platform’s **Active Assist** utilizes AI to analyze usage patterns and proactively recommend downscaling over-provisioned instances or identifying idle resources (zombie servers) to cut waste.

These mechanisms allow buyers to continuously optimize spend throughout the contract term without renegotiating the framework agreement.

Mandatory certifications

Mandatory certifications

Are you are bidding to offer IaaS and/or PaaS as a reseller or are you in sole control of the infrastructure

Sole Control of the Infrastructure

ISO 9001 certification

Provided

ISO 14001 certification

Provided

ISO 27001 certification

Provided

ISO 20000-1 certification

Provided

ISO 27017 certification

Provided

Are you bidding to provide services under Lot 1b or both Lot 1a and Lot 1b?

Yes

ISO 27018 certification

Provided

Cyber Essentials

Do you have a Cyber Essentials Plus certificate?
Yes
Cyber Essentials Plus certificate Number
756bdb10-bc7a-4f2e-be0a-6d9323f875c3

Non-mandatory Standards and certifications

ISO 28000:2022 certification
No
Quality management systems (QMS)
Yes
CSA STAR certification
Yes
CSA STAR accreditation date
Friday 18 July 2025
CSA STAR certification level
Level 2: CSA STAR Attestation
What the CSA STAR doesn’t cover
Anything not listed in the certificate
PCI certification
Yes
Who accredited the PCI DSS certification
Coalfire Systems, Inc.
PCI DSS accreditation date
Sunday 30 November 2025
What the PCI DSS doesn’t cover
Anything not listed in the certificate
Other security certifications
No

Social value

Section B - Commitment for Future: Delivery
  • Mission: Kick start economic growth. To secure the highest sustained growth in the G7 - with good jobs and productivity growth in every part of the country making everyone, not just a few, better off.

    Policy Outcome 1: Fair work: That offers fair wages and good working conditions. Help people get a job, stay in work, and progress in their careers, with good employment opportunities across the country. Notes: Where there is a large proportion of labour costs in the contract, commercial teams should consider MAC in Outcome 1 as a priority

    • New or retained jobs on the contract workforce in the relevant area that meet the criteria set out in MAC 1b, 1c and 1d
    • Providing opportunities for, and measuring and monitoring of, staff workforce conditions over time, including employee engagement, involvement in decision-making and satisfaction and adapting to any changes in the results, with clear processes for acting on issues identified
    • Employment contracts that reflect actual hours worked; steps taken to ensure employees understand their contracts and have the ability to review and adjust them if actual hours regularly exceed contracted hours
    • Activities that support an environment where staff are educated about and feel empowered to report and address bullying and harassment
    • Offer a pay and leave entitlement to all eligible staff who become kinship carers, ideally equivalent to statutory adoption pay and leave
    • Payment of more than the National Minimum Wage or National Living Wage (as appropriate) to the contract workforce
    • Understanding of in-work progression issues affecting the market, industry or sector relevant to the contract, and in the supplier’s own organisation and those of its key sub-contractors
    • Support for educational attainment relevant to the contract, including training schemes that address skills gaps and result in recognised qualifications
    • Volunteering opportunities for staff
    • Understanding of the modern slavery risks and issues affecting the market, industry, sector or country (of origin or of source) relevant to the contract, and the workforce in the supplier’s own organisation and those of its key subcontractors
    • Measures to identify, mitigate and manage modern slavery risks relating to the contract and how these will be implemented
    • Outline policies and practices to be applied to or put in place for the contract to mitigate and manage modern slavery risks, including: Pre-employment checks, recruitment practices. Workplace conditions, safeguarding plans and processes in place and regular monitoring with relevant groups considered, which may include sampling
    • How to ensure business decisions re: price/cost, short lead times, payment timescales do not create modern slavery risks in the supply chain
  • Mission: Kick start economic growth. To secure the highest sustained growth in the G7 - with good jobs and productivity growth in every part of the country making everyone, not just a few, better off.

    Policy Outcome 2: Skills for growth: Supporting growth sectors and addressing skills gaps.

    • Understanding of employment and relevant skills issues, and of the education and training issues relating to the contract. Illustrative examples: demographics, skills shortages, new opportunities in high growth sectors, geographic/local community and skills/employment challenges
    • Support for educational attainment relevant to the contract, including training schemes that address skills gaps and result in recognised qualifications
    • Activities to support relevant sector related skills growth and sustainability in the contract workforce. Illustrative examples: careers talks, curriculum support, literacy support, safety talks and volunteering
  • Mission: Kick start economic growth. To secure the highest sustained growth in the G7 - with good jobs and productivity growth in every part of the country making everyone, not just a few, better off.

    Policy Outcome 3: Resilient, innovative and flexible supply chains: Support economic growth through enabling resilient businesses, opportunities for small businesses and voluntary, community and social enterprises

    • Understanding of the types of businesses in the market and the level of participation by new businesses, entrepreneurs, start-ups, SMEs, VCSEs and mutuals
    • Activities to identify opportunities to open up sub-contracts under the prime contract to a diverse range of businesses, including new businesses, entrepreneurs, start-ups, SMEs, VCSEs and mutuals
    • Activities that demonstrate a collaborative way to work with a diverse range of businesses as part of the supply chain
    • Structuring of the supply chain selection process to ensure fairness (e.g. anti-corruption) and encourages participation by a diverse range of businesses, including with regard to new businesses, entrepreneurs, start-ups, SMEs, VCSEs and mutual
    • Methods for engaging with different parts of the community (including the education system and charities representing the community) and how communities come together to inform decisions, strategy and projects to leave a positive legacy for future generations
    • Measures to involve local stakeholders and/or users in design (e.g. in the design of services, systems, products or buildings)
    • Plans for positive actions with community groups.
    • Measures for making facilities used in the delivery of the contract available for community groups, education or training
    • Plans to respond flexibly and adapt approaches to community engagement and initiatives
    • Collaborating with anchor institutions and community groups to make facilities available for education, training or community events
  • Mission: Make Britain a clean energy superpower: To cut bills, create jobs and deliver security with cheaper, zero-carbon electricity by 2030, accelerating to net zero

    Policy Outcome 4: Sustainable procurement practices: Reducing carbon footprints, minimising waste, and promoting the use of clean energy and green technologies.

    • Understanding of opportunities for additional environmental benefits delivery in the performance of the contract, including working towards net zero carbon emissions and use of clean energy and green technologies
    • Collaborative ways of working with the supply chain to deliver additional environmental benefits in the performance of the contract, including working towards net zero carbon emissions and use of clean energy and green technologies
    • Delivery of additional environmental benefits through the performance of the contract, including working towards net zero carbon emissions and use of clean energy and green technologies
    • Understanding of how to influence staff, suppliers, customers, communities and/or any other appropriate stakeholders through the delivery of the contract to support climate and nature protection and improvement
    • Activities to reconnect people with the environment and increase awareness of ways to protect and enhance it
  • Mission: Break down barriers to opportunity: By reforming our childcare and education systems, to make sure there is no class ceiling on the ambitions of young people in Britain

    Policy Outcome 6: Employment and training: For those who face barriers to employment

    • Understanding of employment and skills issues, and of the skills and employment shortages of high growth sectors relating to the contract
    • Delivery of training schemes and programmes to address any identified skills gaps and under-representation in the workforce for the contract (e.g. prison leavers, care leavers, kinship carers, disabled people)
    • Inclusive and accessible recruitment practices, and retention-focused activities, including those provided in the Guide for line managers on recruiting, managing and developing people with a disability or health condition
    • Working conditions which promote an inclusive working environment and promote retention and progression
    • Other measures to provide equality of opportunity for disabled people and those with health conditions into employment, including becoming a Disability Confident employer and inclusion of supported businesses in the contract supply chain
    • Understanding of the issues affecting inequality in employment, skills and pay in the market, industry or sector relevant to the contract, and in the supplier’s own organisation and those of its key sub-contractors. Measures to tackle inequality in employment, skills and pay in the contract workforce
    • Inclusive and accessible development practices, including guidance for line managers on recruiting, managing and developing people with a disability or health condition
  • Mission: Break down barriers to opportunity: By reforming our childcare and education systems, to make sure there is no class ceiling on the ambitions of young people in Britain

    Policy Outcome 7: Creating a pipeline of opportunities: For the contract workforce, reducing barriers to entry for under-represented groups.

    • Understanding of the issues affecting the development of new skills by target cohort
    • Understanding of the underlying factors affecting improvements to reduce barriers to entry and training schemes for the target cohort(s) related to the contract workforce
    • Understanding of issues relating to entering the contract workforce
    • Creation of outreach activities to create a pipeline of employees for the future contract delivery
  • Mission: Build an NHS fit for the future: That is there when people need it; with fewer lives lost to the biggest killers; in a fairer Britain, where everyone lives well for longer.

    Policy Outcome 8: Increasing productivity through physical and mental wellbeing: In the supply chain and communities in the relevant area.

    • Understanding of issues relating to health and wellbeing, including physical and mental health, in the contract workforce
    • Understanding barriers to access to health and social care services or employment opportunities e.g. digital inclusion
    • Inclusive and accessible recruitment practices, development practices and retention policies that support-focused activities including those provided in the Guide for line managers on recruiting, managing and developing which support people with a disability or health condition
    • Actions to invest in the physical and mental health and wellbeing of the contract workforce

Service documents

Request an accessible format
If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at ps-frameworks@google.com. Tell them what format you need. It will help if you say what assistive technology you use.