Drive consistency and standardisation

Create isolation boundaries in order to provide assurance around the level of isolation our business applications need. Create stages such as non-production or production that networks, cloud accounts, policies and cloud resources can be scoped to. When Developers self-serve, Wayfinder's automation will isolate inline with your definitions.

Integrate team Cloud accounts into Wayfinder and make it part of your Gitops workflow. Map all accounts to the team workspaces ready for development teams to start self-serving Cloud infrastructure without any delays.

Create self-service Kubernetes plans and infrastructure types that teams will need for their workloads. Reduce the complexity away so it is easy for developers to select pre-defined, tested and secured infrastructure - allowing them to focus on environments and application deployment.

Create policies that are scoped to both teams and infrastructure. Allow teams the freedom to iterate on applications safely without the concerns of security issues being introduced. Combine this with workload isolation to add defence in depth.

Import tested and secured application-centric terraform modules. Allow teams to provide only what they need to into the module, such as database name, region or bucket name. By providing a self-service abstraction over Terraform, it allows your team to manage only one version of the module reducing project module sprawl.

Provide in-cluster services such as cost solutions, monitoring agents, security tools or integrations into various PKI systems. Use templates to create a set of dependent, versioned services that you can test and provide back to teams.