VE3 GLOBAL LTD

Google Cloud Services

VE3 and Google collaborate to combine industry knowledge with cutting-edge technology to drive large-scale transformation. We offer comprehensive Google Cloud services, covering architectural design, implementation, migration, operations, and support. Our services guide customers through entire cloud journey, facilitating migration of existing systems or development of new cloud-native applications on GCP.

Features

Cloud strategy design including governance, security and organisational readiness.
Google Cloud landing zones with automated guardrails and standards.
VE3 DevOps Platform integrated with Google Cloud services.
Application migration, transformation, refactoring and modernisation on GCP.
Cloud-native architecture and application development using Google frameworks.
Data analytics platforms using BigQuery, AI/ML and advanced modelling.
Managed GCP operations including compute, storage and networking services.
SAP on Google Cloud with global enterprise delivery expertise.
Apigee API management strategy, deployment and development services.
Anthos and GKE solutions for hybrid and multicloud environments.

Benefits

Strategic partnership with Google Cloud and Apigee accelerates transformation.
Faster innovation using scalable, enterprise-grade Google Cloud services.
Build resilient cloud-native applications using Kubernetes Engine and Anthos.
Reduce costs through automation and Google managed service capabilities.
Drive transformation using AI/ML and predictive analytics on GCP.
Improve customer experiences with CCAI and intelligent automation.
Faster insights through advanced analytics, modelling and data pipelines.
Consumption-based pricing eliminates upfront capital commitments.
Infrastructure-as-code enables rapid, consistent environment deployment.
Open-source technologies improve portability, flexibility and long-term cost efficiency.

Education pricing available

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 prime@ve3.global. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 15

Service ID

Contact

VE3 GLOBAL LTD Nikhil Alex
Telephone: 02045520840
Email: prime@ve3.global

About your service

Service categories

PaaS

Analytics and Business Intelligence

Business Intelligence
Advanced Predictive Analytics
Location and Geospatial data management and analytics

Service scope

Service constraints: The service may require scheduled maintenance windows for platform updates, security patches and network changes, which are communicated in advance. Some advanced GCP capabilities depend on specific regions, quotas or supported machine types. Certain workloads may require refactoring before migration to Google Cloud services. High-risk changes such as network reconfiguration or security policy updates must follow controlled change-management processes. Legacy operating systems or unsupported applications may have limited compatibility. Connectivity prerequisites, such as VPN or Interconnect, must be established before onboarding. Availability of new GCP services may vary by region and be subject to Google’s release schedule.
System requirements: Modern web browser required to access Google Cloud Console securely.

Stable internet connection for service provisioning and administration tasks.

Buyer-managed endpoint security and antivirus on connecting devices.

Supported operating systems for deployed Google Cloud workloads.

VPN or Interconnect required for hybrid or private connectivity needs.

Valid Google Cloud project or billing account for resource creation.

IAM roles defined by buyer for controlled administrative access.

API-enabled tools for automation, provisioning and infrastructure integration.
Cloud deployment model: Public cloud

User support

Email or online ticketing support: Yes
Support response times: 24*7
User can manage status and priority of support tickets: Yes
Online ticketing support accessibility: WCAG 2.2 AA
Phone support: Yes
Phone support availability: 9 to 5 (UK time), Monday to Friday
Web chat support: No
Onsite support: Yes, at extra cost
Support levels: Standard (Bronze) – Business hours support (09:00–17:30 UK), incident and request handling, access to cloud support engineers, monthly reporting.

Enhanced (Silver) – Extended hours (e.g., 07:00–20:00), proactive monitoring and improved response SLAs.

Premium (Gold) – 24×7 cover, continuous monitoring, priority P1/P2 handling, regular service reviews.

Managed (Platinum) – Full 24×7 managed service including optimisation, patching, and release management.
Support available to third parties: Yes

Onboarding and offboarding

Getting started: We provide a structured onboarding process to help users begin using Google Cloud Services effectively. This includes initial discovery sessions to understand requirements, followed by guided setup of Google Cloud projects, IAM roles, networking foundations and landing zone configurations. Users receive access to comprehensive documentation, configuration templates, and best-practice guides specifically aligned to Google Cloud architecture standards.

Online training sessions, walkthroughs and virtual workshops are available to help users learn how to deploy resources, manage security, configure monitoring and operate workloads on Google Cloud. We also provide introductions to key services such as GKE, BigQuery, Cloud Storage, Cloud Functions and Apigee where relevant.

Our cloud engineers support customers during initial provisioning, connectivity setup, organisational policy configuration and workload migration preparation. Additional onboarding support such as hands-on enablement, deep-dive training or architecture reviews can be delivered remotely, with onsite enablement available upon request. Throughout onboarding, users can access the support portal, training materials and best-practice checklists to ensure a smooth transition to operational use.
Service documentation: Yes
Documentation formats: PDF
End-of-contract data extraction: At the end of the contract, users retain full ownership of their data and can extract it at any time before service termination. Google Cloud provides multiple built-in mechanisms for exporting data, including downloading objects from Cloud Storage, exporting BigQuery datasets, taking VM snapshots or machine images, exporting databases, downloading logs, and retrieving configuration files. Users may also extract data using APIs, the gcloud CLI, bulk export tools, or automated scripts. VE3 ensures permissions remain active during the offboarding window and provides guidance on the most appropriate export method for each workload. If required, our engineers can support large-scale migrations or data transfers. No data is removed until the customer confirms successful extraction.
End-of-contract process: When the contract approaches expiry, the customer is notified in advance and an agreed offboarding window is provided. During this period, users retain full access to their Google Cloud Console, APIs, CLI tools and VE3 support channels so they can export data, remove resources, migrate workloads or transfer services to another provider. VE3 maintains access rights, monitoring and basic support throughout offboarding to ensure users can safely extract VM images, databases, storage objects, logs and configurations. Once the customer confirms that all required data has been extracted, VE3 schedules the secure deprovisioning and sanitisation of remaining resources in line with Google Cloud’s data-deletion policies.

The contract price includes guidance on offboarding steps, continued portal and API access during the offboarding period, standard support for data extraction questions, and confirmation of secure deletion. Additional costs apply only where users require extended assistance—such as migration engineering, large-scale data transfer support, custom export tooling, or a managed transition project. These activities can be delivered on request as optional professional services.
Documentation accessibility standard: WCAG 2.2 AA

Using the service

Web browser interface: Yes
Using the web interface: Users can use the Google Cloud Console to set up services by creating projects, configuring IAM roles, deploying compute, storage, networking resources and selecting predefined landing zone templates. Through the web interface, they can modify configurations, scale workloads, adjust security policies, manage billing, review monitoring dashboards, configure Cloud Functions, deploy Kubernetes workloads, and manage APIs using Apigee. Users can also update network settings, create VPCs, manage service accounts and configure backups directly from the console.

Most operational tasks can be performed through the interface without requiring CLI or API access. However, some advanced configurations such as complex anthos deployments, custom automation, organisation-level policy enforcement, and specialised networking setups may require CLI, Terraform, or API actions. Role-based access control ensures users only perform actions within their assigned permissions, and certain high-risk changes may need administrative approval.
Web interface accessibility standard: WCAG 2.2 AA
Web interface accessibility testing: Cloud management interfaces provided by Google Cloud undergo regular accessibility testing to ensure compatibility with assistive technologies. This includes validation with screen readers such as JAWS and NVDA, keyboard-only navigation, high-contrast display modes, magnification tools and zoom features. We additionally validate key onboarding and operational workflows to ensure they can be completed by users relying on assistive technologies. No accessibility barriers have been identified for standard provisioning, configuration or monitoring activities. Formal user testing with assistive-technology end-users is not conducted directly by VE3, but we rely on Google’s ongoing accessibility improvements and published testing standards.
API: Yes
What users can and can't do using the API: Users can use Google Cloud’s REST and gRPC APIs, along with the client libraries, to provision and manage resources programmatically. Through the API, users can set up the service by creating projects, configuring IAM policies, deploying compute instances, provisioning storage, creating VPC networks and applying organisation policies. They can also automate deployments using Terraform, Cloud Deployment Manager or CI/CD pipelines.

Users can make changes by updating resource configurations, scaling services, modifying security settings, managing service accounts, triggering Cloud Functions, adjusting load balancers and retrieving logs or metrics. Most GCP services provide full API coverage, enabling end-to-end automation.

Limitations include role-based access restrictions for sensitive operations, API quotas and rate limits, and certain advanced or organisation-level controls that may only be configured via the Admin Console or through Terraform. Some enterprise features, such as hybrid networking or complex Anthos configurations, may require combined API and CLI deployment steps.
API automation tools: Ansible

Chef

SaltStack

Terraform

Puppet
API documentation: Yes
API documentation formats: PDF
Command line interface: Yes
Command line interface compatibility: Linux or Unix

Windows

MacOS
Using the command line interface: A full command line interface (CLI) is available for this service, enabling users to script, automate and manage Google Cloud infrastructure programmatically. Using the gcloud CLI, customers can authenticate to their Google Cloud project, initialise folders or resource hierarchies, deploy compute, storage and networking components, configure GKE clusters and serverless services, and retrieve monitoring, logging or diagnostic data. Users can set up services by installing the Google Cloud SDK, authenticating with MFA-enabled credentials or service accounts, and running standard commands or applying Terraform or Deployment Manager templates. Changes can be made by updating resource parameters, running declarative scripts, or automating deployments through CI/CD pipelines.

Limitations include: some organisation-level features requiring the Admin Console; certain advanced Anthos or hybrid networking configurations needing API or console support; role-based access controls restricting destructive or privileged actions; and applicable API quotas or governance policies. The CLI is fully compatible with automation workflows and is widely used for DevOps, infrastructure-as-code and repeatable environment builds.

Scaling

Independence of resources: Google Cloud provides strong multi-tenant isolation to ensure one customer’s activity cannot affect another. Each user operates within isolated projects and VPC networks, with dedicated allocations for compute, storage and networking. Google’s hypervisor, distributed storage and autoscaling services are designed to prevent noisy-neighbour effects and maintain consistent performance. Network segmentation, quotas and IAM policies enforce strict separation of access and resources. VE3 applies governance guardrails and best-practice configurations to ensure workloads remain isolated, resilient and unaffected by demand from other organisations.
Usage notifications: Yes
Usage reporting: API

Email

SMS
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
Reporting types: API access

Real-time dashboards

Regular reports

Reports on request
Resource tagging: Yes
FOCUS resource tagging: Yes

Resellers

Supplier type: Reseller providing extra support
Organisation whose services are being resold: Google Cloud Platform (GCP) and associated Google Cloud services.

Staff security

Staff security clearance: Conforms to BS7858:2019
Government security clearance: Baseline Personnel Security Standard (BPSS)

Asset protection

Knowledge of data storage and processing locations: Yes
Data storage and processing locations: United Kingdom
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 once a year
Penetration testing approach: ‘IT Health Check’ performed by a CHECK service provider
Protecting data at rest: Physical access control, complying with SSAE-18 / ISAE 3402

Encryption of all physical media

Scale, obfuscating techniques, or data storage sharding
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

Backup and recovery

What’s backed up: Virtual machine images and persistent disk snapshots for full recovery.

Databases with automated backups and point-in-time recovery options.

Cloud Storage objects with versioning and lifecycle retention controls.

Kubernetes persistent volumes and container workload state data.

Application configurations, service accounts and deployment manifests.

BigQuery datasets using export jobs or scheduled snapshots.

Logs, metrics and monitoring data for operational recovery needs.
Backup controls: Users control backups through the Google Cloud Console, CLI or APIs. They can select which resources to protect such as VM disks, databases, Kubernetes volumes, BigQuery datasets or Cloud Storage objects and apply different schedules, retention periods and policies per resource. Backup plans can be created for individual workloads or applied across projects. Users can enable, disable or modify backup rules at any time, including choosing incremental or full snapshots. Tag-based or label-based automation is supported, and role-based access ensures only authorised users can change backup configurations or initiate restores.
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
Data protection within supplier network: TLS (version 1.2 or above)

IPsec or TLS VPN gateway

Legacy SSL and TLS (under version 1.2)

Availability and resilience

Guaranteed availability: We typically align service levels with the underlying hyperscaler (for example Azure, AWS, Google Cloud, Oracle, VMware) and then wrap them in a clear, contract-level SLA. For Lot 1a services, our standard target is **99.9% availability per calendar month** for the managed components within our control (excluding planned maintenance windows agreed in advance, force majeure, and customer-caused issues). Higher targets (for example **99.95% or 99.99%**) can be designed and priced at call-off using multi-zone, active/active, or resilient architectures. If we fail to meet the agreed availability SLA, customers are entitled to **service credits** against the monthly service charges. These are typically tiered (for example, increasing % credits as availability drops further below target) and are applied as a deduction from a future invoice. The precise percentage bands and thresholds are confirmed in the call-off so they reflect the specific design, criticality and cost of the environment.
Approach to resilience: Below is a **strong, reusable, Lot-1a-compliant resilience statement** that fully aligns with Government Security Principle 2 (Asset Protection & Resilience) and is safe to publish on G-Cloud. --- # **Approach to Resilience (G-Cloud Lot 1a – Standard Answer)** Our service is designed to be resilient by leveraging the built-in high-availability and disaster-recovery capabilities of leading hyperscale cloud platforms. All customer environments run across **multiple datacentres (availability zones)** with independent power, cooling, networking and physical security controls. Core components such as compute, storage and networking are designed with **redundancy, automatic failover, and zone-level isolation** to protect against localised failures. Data is stored with **multi-zone replication**, integrity checks and optional cross-region disaster-recovery configurations depending on buyer requirements. The platform continuously monitors infrastructure health and automatically replaces or restarts failed components. Load balancing, autoscaling, and distributed architectures ensure the service remains available during demand spikes or hardware failures. Full details of underlying datacentre architecture and resilience controls are **available on request**, including compliance reports, redundancy configurations, and recovery architecture patterns.
Outage reporting: We use several channels to report outages and degradation so users are informed quickly and transparently: Public dashboard: A cloud status page provides real-time visibility of service health, showing current incidents, affected regions/services and historical uptime. Email alerts: Customers can subscribe to incident and maintenance notifications. During an outage we send initial alerts, updates, and closure messages, including impact, workaround (if any), and estimated time to resolution when available. API / webhooks (Other): For advanced users, incident and health information can be integrated into their own tooling via APIs or webhooks (for example into ITSM, Teams/Slack, or NOC dashboards).

Identity and authentication

User authentication needed: Yes
User authentication: Multi-Factor Authentication (MFA)
Access restrictions in management interfaces and support channels: Access to management interfaces and support channels is restricted using role-based access control (RBAC), least-privilege principles, and multi-factor authentication (MFA). Administrative actions are limited to authorised personnel within defined roles, with segregation between support, operations and security teams. All access is logged, monitored and periodically reviewed. Customer environments are isolated within separate tenancies or subscriptions, preventing cross-tenant access. Support channels enforce identity verification before any change is made, and sensitive operations require elevated approval. Remote access uses secure channels (TLS/MFA/VPN), with Just-In-Time access available where supported to minimise exposure windows.
Access restriction testing frequency: At least once a year
Management access authentication: Multi-Factor Authentication (MFA)
Devices users manage the service through: 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)

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: ISO/IEC 27001
Information security policies and processes: We operate a full Information Security Management System aligned to ISO 27001 and Cyber Essentials Plus, supported by documented policies covering access control, asset management, data protection, secure development, vulnerability management, incident management, business continuity and supplier assurance. Policies are reviewed annually or after significant change. Governance is overseen by the Information Security Lead, who reports to VE3’s senior management. Compliance is monitored through internal audits, automated controls, risk assessments, and mandatory staff training. Technical enforcement includes RBAC, MFA, encryption, network segmentation, logging and continuous monitoring. Security incidents follow a defined process: detection, triage, containment, root-cause analysis and corrective action, with escalation to senior leadership where required. All changes follow a controlled change-management process to ensure policy adherence. We also align to hyperscale cloud security best practices and regularly review our posture against government and industry standards.

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: We follow a controlled, ITIL-aligned configuration and change management process. All components are defined and tracked using infrastructure-as-code templates stored in version control, creating a full audit trail and enabling consistent, repeatable deployments. Assets are registered in a configuration repository and tagged to track ownership, environment and lifecycle. Changes follow a formal workflow: request, assessment, approval, implementation and review. Each change is evaluated for security impact, including access, encryption, network exposure, dependency effects and compliance. High-risk changes require security or CAB approval. All updates are tested in non-production and logged to support audit and traceability.
Vulnerability management type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
Vulnerability management approach: We use continuous protective monitoring across all managed components, including log collection, anomaly detection, threat intelligence feeds and cloud-native security services (for example Azure Security Center, AWS GuardDuty, GCP Security Command Center). Potential compromises are identified through alerts on suspicious authentication, privilege escalation, unusual network activity, configuration drift or malware indicators. All alerts are triaged immediately; critical incidents receive response within 1 hour, with containment, investigation and remediation following a defined incident management process. Actions may include isolating resources, rotating credentials, applying patches and producing post-incident reports with root-cause analysis and corrective controls.
Protective monitoring type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
Protective monitoring approach: We use continuous protective monitoring across all managed components, including log collection, anomaly detection, threat intelligence feeds and cloud-native security services (for example Azure Security Center, AWS GuardDuty, GCP Security Command Center). Potential compromises are identified through alerts on suspicious authentication, privilege escalation, unusual network activity, configuration drift or malware indicators. All alerts are triaged immediately; critical incidents receive response within 1 hour, with containment, investigation and remediation following a defined incident management process. Actions may include isolating resources, rotating credentials, applying patches and producing post-incident reports with root-cause analysis and corrective controls.
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: We operate a formal, ITIL-aligned incident management process with **pre-defined runbooks** for common events (service degradation, access issues, capacity problems, security alerts and backup/restore failures). Incidents can be reported by users via the **service desk portal, email or phone**, and high-severity events may also be raised automatically from monitoring and alerting tools. All incidents are logged, categorised and prioritised with agreed response and resolution targets. We keep users informed through status updates during investigation and resolution. For **major incidents**, we provide a written **incident report** detailing timeline, root cause, impact, corrective actions and preventive measures, typically within an agreed timeframe.
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: Third-party
Third-party virtualisation provider: Hyperscale cloud provider – Azure, AWS, Google Cloud, Oracle, VMware)
How shared infrastructure is kept separate: We use the hyperscaler’s multi-tenant virtualisation and logical isolation controls to ensure complete separation between organisations. Each customer operates within a dedicated tenancy/subscription, isolated virtual networks and resource groups. The underlying platform enforces strong separation through hypervisor-based isolation, container sandboxing, kernel-level security, and memory, CPU and I/O separation that prevents cross-tenant access. Network segmentation, firewalls, security groups and identity boundaries further ensure workloads cannot interact unless explicitly configured. Storage is logically isolated with encrypted, tenant-scoped keys. The provider regularly validates isolation through independent audits, penetration testing and compliance certifications.

Energy efficiency

Energy-efficient datacentres: Yes
Description of energy efficient datacentres: Our underlying hyperscale cloud providers (Microsoft Azure, AWS, Google Cloud, Oracle Cloud, VMware) operate datacentres that follow the EU Code of Conduct for Energy-Efficient Datacentres. They implement industry-leading efficiency measures including: advanced cooling technologies (free-air, liquid, evaporative cooling) energy-efficient power distribution and UPS systems server virtualisation and high-density compute to reduce energy per workload continuous monitoring of PUE (Power Usage Effectiveness) with targets typically ≤1.2 in modern sites renewable energy procurement and carbon-reduction programmes ongoing audits and lifecycle optimisation aligned to EU-CoC best practices

Pricing

Discount for educational organisations: Yes
Free trial available: No

Discount

Provide your minimum discount applicable to your baseline prices: 3%

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: Baseline pricing is usage-based and is determined from published unit rates for the Public Cloud components that make up the buyer’s requirement (for example compute, storage, networking, and managed platform services), plus any VE3 standard service charges that are explicitly priced as part of the service offering. Buyers identify the baseline by selecting the required service components (region, tier, instance/service size, storage class and expected usage volumes such as hours/GB/requests) and multiplying expected usage by the published unit rates shown in the service’s Pricing section. Where a service includes a VE3-managed or professional services element, the applicable unit/day-rate or fixed charge is also shown in the Pricing section of the relevant catalogue entry. Prices are stated in GBP and exclude VAT unless otherwise specified. The minimum discount (as stated in the ‘Discount’ question) is then applied to derive the discounted baseline before onboarding and any other cost factors are added.
Baseline Pricing - Web link: https://www.ve3.global
-
Minimum Discounting: 3%
+
Onboarding Activity: Onboarding costs may vary based on your specific requirements, please confirm with suppliers during the clarification process
+
Additional sources of cost: Additional costs may arise where the buyer’s requirement increases scope or consumption beyond the baseline assumptions. Typical cost drivers include: higher-than-forecast public cloud consumption (for example increased compute hours, storage growth, managed database throughput, or API/request volumes); network and connectivity requirements (VPN/peering/private connectivity where applicable); high outbound data transfer (egress) volumes; enhanced security/compliance controls (for example WAF, SIEM/SOC integration, vulnerability scanning, encryption/HSM, additional audit requirements); backup and disaster recovery requirements (multi-region resilience, longer retention); increased logging/monitoring retention and observability tiers; additional environments (dev/test/stage/perf); premium support hours (24x7) and tighter incident SLAs; third-party software licensing/marketplace subscriptions; and change requests for non-standard configurations or accelerated delivery. Where underlying cloud services are priced in non-GBP currencies, exchange-rate movements may also affect pass-through consumption costs.
-
Additional sources of cost reduction: Cost reductions may apply in addition to the stated minimum discount through: commitment-based discounts offered by public cloud providers (for example Reserved Instances/Savings Plans/Committed Use) and volume-based pricing where applicable; right-sizing and autoscaling to reduce unused capacity; scheduling and shutdown of non-production environments out of hours; use of spot/preemptible capacity where appropriate; storage lifecycle management (tiering to lower-cost storage/archival); consolidation of shared services (logging/monitoring/network components) across workloads; use of existing customer licences (BYOL) where permitted; and sector-specific discounts or service bundling where included in the service pricing. VE3 can also provide FinOps optimisation and continuous cost governance so that reductions identified are reflected in revised run-rate forecasts and monthly charges.

Mandatory certifications

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

Reseller

Cloud service suppliers you intend to resell with evidence

Organisation 1

Organisation name

Microsoft