VE3 GLOBAL LTD

Oracle Cloud Native Platform Service

VE3’s Agile Innovation Platform (AIP) provides a secure platform for developing enterprise applications using modern cloud-native architectures and principles.

Features

Full support for the adoption of Microservice Architecture
Secure and scalable solutions based on Cloud infrastructure
Rapid platform provisioning using Infrastructure as Code (IaC)
Adoption of Continuous Integration and Continuous Delivery (CI/CD)
Full observability: Logging, Monitoring, and Alerting
AIP supports Oracle Verazzanno for migrating Weblogic applications to Cloud

Benefits

Increased agility to respond quickly to market threats and trends
Product centric development, eliminating long timescales associated with project-based development
Release of software in smaller batches to expediate delivery
Develop new business models in response to emerging consumer demands
Breakdown of large monolithic, brittle applications into loosely coupled services
VE3 has a wealth of experience developing microservices and APIs
Commitment to cost reductions using VE3’s Rightshore delivery model

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

Data Management

Data integration and intelligence

Service scope

Service constraints: The service may require scheduled maintenance windows for platform upgrades, security patches or network changes; these are agreed in advance with customers. Some advanced configurations may depend on specific cloud-provider features or supported hardware instance types. High-risk changes, such as network reconfiguration or security policy updates, may require controlled change-management approval. Certain legacy operating systems or unsupported applications may have limited support. Service availability may vary by cloud region based on provider capacity. Connectivity dependencies, such as VPN or Direct Connect/ExpressRoute links, must be established before onboarding. Customers remain responsible for workloads deployed outside recommended architectures.
System requirements: Modern web browser required to access management and monitoring portals.

Stable internet connection for provisioning and administrative operations

Buyer-managed endpoint antivirus and device security controls.

Supported operating systems for deployed virtual machines and workloads.

VPN or private connectivity for hybrid or on-premise integration.

Valid cloud subscriptions or projects for resource provisioning.

SSH or RDP client for virtual machine access.

SSO or identity provider supporting SAML or OIDC authentication.

IAM roles defined by buyer for administrative privilege management.

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

User support

Email or online ticketing support: Yes
Support response times: We provide 24×7 email and online ticketing support. Standard enquiries are acknowledged within 30 minutes, with response times faster for priority incidents. Weekend and bank-holiday response times remain the same for supported customers under Enhanced and Premium SLAs
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: We provide four support tiers: Standard, Enhanced, Premium and Managed. Standard includes business-hours support, incident handling and access to cloud support engineers. Enhanced adds extended-hours cover, proactive monitoring and improved response SLAs. Premium provides full 24×7 support, priority incident handling, continuous monitoring and scheduled service reviews. Managed offers a fully managed 24×7 service including optimisation, patching, lifecycle management and operational governance. Support pricing varies by tier and is charged as a monthly managed-service fee based on scope and SLA. Customers selecting Enhanced, Premium or Managed tiers receive access to a Technical Account Manager or Cloud Support Engineer for architectural guidance, optimisation recommendations and ongoing assistance.
Support available to third parties: No

Onboarding and offboarding

Getting started: We provide a structured onboarding process that includes guided setup sessions, access to detailed user documentation, and configuration templates for common deployment patterns. Users receive an introduction to the management portal, identity setup, networking prerequisites, and recommended best practices for building their environments. Online training and remote walkthroughs are available to support teams during initial configuration. Our cloud engineers assist with account readiness, connectivity, governance policies and initial resource provisioning to ensure a smooth start. Onsite enablement can be arranged if required.
Service documentation: Yes
Documentation formats: PDF
End-of-contract data extraction: At the end of the contract, users retain full control of their data and can extract it at any time before service termination. Data can be exported using native cloud-provider tools, including VM images, database backups, file and object-storage exports, logs, and configuration files. Users may also extract data through APIs, CLI commands, bulk export utilities or automated scripts. VE3 ensures required access remains available during the offboarding period and provides guidance on suitable export methods. If requested, our engineers can support large-scale data transfers or migrations. No data is deleted until the customer confirms successful extraction.
End-of-contract process: At contract end, we notify the customer in advance and provide an agreed offboarding window to extract data, export configurations or migrate workloads. Users retain access to the management portal, APIs and support channels during this period so they can remove resources, export VM images, databases, files and logs, and complete any required transitions. Once the customer confirms that all data has been successfully extracted, we schedule the secure shutdown and sanitisation of remaining environments in line with cloud-provider and organisational data-deletion policies. The contract price includes: offboarding guidance, access to documentation, continued portal access during the transition period, and confirmation of secure data deletion. Additional costs apply only if customers require extended migration support, large-scale data transfer assistance, specialist engineering resources, custom export tooling or a managed transition project.
Documentation accessibility standard: WCAG 2.2 AA

Using the service

Web browser interface: Yes
Using the web interface: Users can set up their cloud infrastructure through the web interface by provisioning compute, storage, networking components and selecting predefined configuration templates. The portal allows users to modify resources, scale environments, adjust security policies, manage identities, configure backups, and view monitoring dashboards. They can also review cost and usage information, raise support tickets, and access documentation. Most day-to-day operations can be completed directly through the interface without requiring API or CLI access. However, certain advanced configurations such as complex networking, custom integrations, enterprise connectivity, or high-privilege security changes may require API/CLI commands or assistance through the change-management process. Access is role-based, ensuring users only perform actions permitted by their assigned permissions.
Web interface accessibility standard: WCAG 2.2 AA
Web interface accessibility testing: Cloud management portals provided by major cloud vendors (AWS, Azure, Google Cloud, Oracle, VMware) undergo regular accessibility testing to ensure compatibility with assistive technologies. These include screen readers such as JAWS and NVDA, keyboard-only navigation, high-contrast modes, magnification tools and zoom features. We additionally validate key onboarding and operational workflows to confirm they function correctly for users relying on assistive technologies. No barriers have been identified for standard provisioning, configuration or monitoring activities. Formal user testing with assistive-technology end-users is not currently performed, but cloud-provider accessibility updates are continuously reviewed and incorporated.
API: Yes
What users can and can't do using the API: Authorised users can use our REST/JSON APIs and the underlying cloud-provider APIs to provision and manage cloud infrastructure. Through the API, users can set up the service by authenticating, creating or selecting subscriptions/tenants, defining resource groups or projects, and deploying parameterised templates describing compute, storage, networking and security components. Changes are made through API calls that create, update or delete resources, adjust configuration parameters, scale environments, manage identities, tags and policies, and retrieve monitoring, logging and cost data. These operations can be fully automated using infrastructure-as-code tools and CI/CD pipelines, enabling repeatable, version-controlled deployments. Limitations include role-based restrictions, where destructive or security-sensitive actions are limited to appropriate administrative roles; provider-imposed rate limits and quotas on API usage; and a small number of advanced or provider-specific features that may only be exposed via the management console or controlled change-management processes rather than the public API.
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: Users can use the command line interface (AWS CLI, Azure CLI, gcloud CLI and supported SDKs) to authenticate, create subscriptions or projects, define resource groups and deploy infrastructure templates to set up the service. Through the CLI, they can create, modify or delete compute, storage and networking resources; update configurations; manage identities, tags and policies; retrieve logs and metrics; and integrate commands into automation pipelines. Most configuration and lifecycle actions can be completed directly through CLI scripts or infrastructure-as-code tools. However, certain advanced functions such as complex networking topologies, enterprise connectivity, privileged security changes or provider-specific features may only be available through the web console or require approval through change-management processes. Role-based access controls restrict sensitive or destructive operations to authorised administrators.

Scaling

Independence of resources: We ensure resource independence through strict multi-tenant isolation and cloud-native virtualisation. Each customer operates within their own subscription, project or account, with dedicated allocations for compute, storage and networking that prevent workloads from affecting other tenants. Capacity across regions and availability zones is continuously monitored, and auto-scaling mechanisms ensure increased demand from one user does not degrade another’s performance. Network traffic is isolated through VPCs/VNETs, security groups and segmentation policies. Storage performance tiers and IOPS controls prevent “noisy-neighbour” effects. Role-based access controls and governance guardrails ensure buyers’ environments remain isolated, protected and unaffected by other users’ demand patterns.
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

Other
Other metrics: Database performance metrics including queries, throughput and latency.

Application response times and end-to-end transaction latency.

Storage capacity utilisation and IOPS performance trends.

Network packet loss, jitter and connection stability indicators.

Load balancer request counts and health check results.

Disk read/write throughput and latency statistics.

Container workload status, resource utilisation and pod health.

API call success rates and error response codes.

Security event logs including authentication and policy changes.

Cost and usage metrics across resources and services.
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 features and support
Organisation whose services are being resold: Oracle

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
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 CSA CCM v4.0

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

Physical Destruction / Hardware containing data is completely destroyed

Backup and recovery

What’s backed up: Virtual machine images and incremental snapshots for full system recovery.

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

File systems and shared storage volumes across cloud environments.

Object storage buckets with versioning and lifecycle retention policies.

Application configurations and environment settings for rapid restoration.

Container workloads and persistent volumes in managed Kubernetes platforms.

Network configurations including firewalls, load balancers and routing tables.

Identity, policy and access-control definitions for IAM environments.

Logs, metrics and monitoring data for operational recovery.

Infrastructure templates and deployment definitions for automated rebuilds.
Backup controls: Users control backups through the cloud console, CLI or API. They can select which resources to protect such as virtual machines, databases, storage volumes or applications and assign different schedules, retention periods and backup types. Backup policies can be applied per resource or across groups, with options for incremental or full backups. Users can enable, disable or modify policies at any time and automate backups using tag-based rules. Role-based access ensures only authorised users can change backup settings or initiate restores. VE3 provides recommended templates, but users retain full control over what is backed up and how frequently.
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

Availability and resilience

Guaranteed availability: Our Cloud Infrastructure Services follow the availability SLAs of the underlying cloud providers (AWS, Azure and Google Cloud). Core compute, storage and networking services typically provide 99.9% to 99.99% availability, depending on the chosen architecture—for example, single-zone, multi-AZ or regionally redundant deployments. VE3 designs environments using high-availability patterns such as load balancing, autoscaling, distributed storage and multi-zone resilience to help customers meet their required uptime objectives. Availability is measured monthly. If uptime falls below the guaranteed SLA for the relevant cloud service, customers are eligible for service credits, which are passed through in accordance with the cloud provider’s official SLA policy. These credits scale based on the severity and duration of the outage. In addition, VE3 provides incident reporting, impact assessment and recommendations to prevent recurrence. Customers selecting enhanced support tiers receive prioritised communication during outages, root-cause summaries and proactive remediation guidance. This combined model ensures availability commitments are achieved and customers are compensated appropriately if they are not.
Approach to resilience: Our service is designed with multi-layer resilience across infrastructure, networking and operations. Workloads are deployed on hyperscale cloud platforms that use multiple geographically separated datacentres (regions and availability zones), providing fault tolerance and continuity in the event of a hardware failure or site-level disruption. Core services such as compute, storage, networking and databases support multi-AZ redundancy, synchronous replication, distributed storage and automated failover to maintain service availability. Network resilience is achieved through redundant routing paths, load balancing, health checks and automated service healing. Storage platforms offer durability through distributed replication, integrity validation and automated recovery. Autoscaling and capacity monitoring ensure increased demand is handled without service degradation. Operational resilience includes automated backups, defined disaster-recovery options aligned with customer RPO/RTO requirements, and infrastructure-as-code to support rapid environment rebuilds. Protective monitoring, incident response processes and regular testing further strengthen continuity. Detailed information about underlying datacentre architecture and resilience controls provided by AWS, Azure and GCP is available to buyers on request.
Outage reporting: Our service provides comprehensive reporting of outages through multiple channels to ensure customers receive timely and accurate information. The underlying cloud platforms (AWS, Azure and Google Cloud) maintain public service-status dashboards that provide real-time visibility into regional and service-specific incidents. These dashboards show issue descriptions, affected services, progress updates and resolution timelines. In addition to public dashboards, VE3 provides email alerts to designated customer contacts for customer-specific issues, high-severity incidents, planned maintenance and any event that may impact service availability. Alerts include incident details, severity, potential impact, mitigation steps and further updates until resolution. For customers requiring automated or programmatic access, cloud-provider status APIs can be integrated into monitoring tools, ticketing systems or SIEM platforms to consume real-time incident and health data. VE3 also publishes notifications through the support portal, allowing users to track active incidents, review historical data and access post-incident reports. Following any significant outage, we perform a root-cause analysis and share remediation actions to prevent recurrence, ensuring transparency and continuous service improvement.

Identity and authentication

User authentication needed: Yes
User authentication: Multi-Factor Authentication (MFA)

Username or password
Access restrictions in management interfaces and support channels: Network Filtering, Intrusion Prevention Systems, Web Application Firewall, 2-Factor Authentication, Network Admission Control Proxies, Content Filtering, and Advanced Threat Management are all part of VE3's comprehensive security measures.
Access restriction testing frequency: At least every 6 months
Management access authentication: Multi-Factor Authentication (MFA)

Username or password
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)

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: At least 12 months
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 follow an information security management framework aligned to ISO 27001, Cyber Essentials Plus, and the cloud security controls of AWS, Azure and Google Cloud. Our policies cover access control, change management, incident response, data protection, vulnerability management and supplier governance. Policies are reviewed annually and approved by our Board-level Security Lead (CISO/CTO).

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 use formal configuration and change-management processes aligned to ITIL and ISO 27001. All service components are tracked throughout their lifecycle using asset records, version-controlled repositories and configuration management tools. Changes follow a documented workflow that includes risk assessment, security review and approval before deployment. Security impact is evaluated by the operations and security teams, focusing on access controls, network exposure and data protection. High-risk changes undergo CAB review, testing and staged rollout. All changes are logged, auditable and continuously monitored to ensure compliance with policy and cloud-provider standards.
Vulnerability management type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
Vulnerability management approach: We operate a continuous vulnerability management process aligned to ISO 27001 and cloud-provider best practices. Potential threats are identified through automated scanning, configuration assessments, threat-intelligence feeds and alerts from AWS, Azure and Google Cloud. High-severity vulnerabilities are prioritised and patched as soon as provider updates are available, typically within defined SLA windows. We source threat information from vendor advisories, CVE databases, CERT notifications and security monitoring tools. All remediation actions are tracked, verified through follow-up scans and reviewed to ensure risks are fully addressed.
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 cloud environments, combining cloud-native security tools, log analytics, SIEM alerts and behavioural analysis to identify potential compromises. Indicators such as unusual access patterns, privilege escalation, configuration drift or anomalous network activity trigger automated alerts for review. When a potential compromise is detected, it is immediately triaged and escalated to the security team, who follow predefined incident-response playbooks. Containment and remediation actions are applied quickly, with high-severity incidents typically responded to within minutes. Post-incident reviews ensure lessons learned and preventative measures are implemented. If you want an even shorter version, I can provide it.
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: VE3 Cloud implements formal event reporting and follows escalation procedures if an information security incident occurs. Documented security incident response plans for the cloud solutions from VE3 ensure that the best possible levels of service quality and availability are achieved. Security incidents are monitored and tracked by security specialists in cooperation with defined communication channels relating to the customer until resolved.
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: Amazon Web Services, Microsoft Azure, Google Cloud Platform
How shared infrastructure is kept separate: Different organisations are kept apart through strong hypervisor isolation, software-defined networking separation and cloud-provider multi-tenant security controls. Each customer operates within their own subscription, project or account, ensuring logical separation of compute, storage and network resources. Virtual machines and containers run on isolated virtualisation layers enforced by the cloud provider’s hardened hypervisor, preventing cross-tenant access. Network isolation is achieved using VPCs/VNETs, security groups, segmentation policies and dedicated routing domains. Storage is separated through logically partitioned volumes and encryption keys unique to each customer. Role-based access controls and identity boundaries ensure users cannot access another organisation’s resources.

Energy efficiency

Energy-efficient datacentres: Yes
Description of energy efficient datacentres: Our service is hosted on hyperscale cloud platforms (AWS, Azure and Google Cloud) whose datacentres adhere to the EU Code of Conduct for Energy-Efficient Datacentres. These providers implement industry-leading sustainability practices including advanced cooling technologies, high-efficiency power distribution, PUE (Power Usage Effectiveness) optimisation, and renewable energy sourcing. Datacentres use automated energy monitoring, dynamic workload placement, thermal optimisation and right-sizing of resources to reduce consumption. Hardware lifecycle practices follow circular-economy principles, ensuring efficient equipment use and responsible disposal. Providers publish annual energy reports and sustainability commitments aligned with the EU Code of Conduct. VE3 inherits these controls to deliver environmentally efficient cloud infrastructure services to customers.

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