A consistent multi-cloud landing zone for Google Cloud Platform, Azure and Amazon Web Services.
Built using modularised, versionable infrastructure as code templates with Terraform using the underlying CSP APIs.
A shared services layer including networking, account management, security, IAM, logging, alerting and billing.
Enables administrators to define which activators can be deployed into development, proof of concept and production based on several criteria, including technology maturity, regulatory environment and data restrictions.
Enables development teams to quickly provision infrastructure by deploying pre-approved activators.
Track and control production changes with versionable infrastructure as code (IaC) that is stored in repos.
Provision infrastructure in minutes, with the IaC being part of the application build process (high DevOps maturity).
Activators are a combination of a reference application architecture and devops pipelines provisioned using IaC templates.
Activators can be created by administrators with policy-based controls defining where they can be deployed and by whom.
Activator provisioning includes linking to the shared services VPC to benefit from consistent deployment and controls.
Activators include provisioning of the latest monitoring and observation tooling.
Pipelines can be defined for each activator using either Jenkins running on K8S or cloud native tooling.
Pipelines can be defined using several release strategies – Canary, Blue/Green, Rolling Blue/Green and Release Train.
Pipelines include ITIL practices including release notes, change control, auditing, pre and post release testing and automated rollbacks.
Pipelines support both CI/CD and also continuous deployment (release-at-will).
Not just a bunch of scripts, but deep software datacentre engineering
