Join us for DevOps Live at ExCeL London  |  6-7 March 2024

Drive consistency and standardisation

Move away from brittle point solutions to testable, repeatable and standardised way of working

Platform teams need consistency

Scale using product ways of working, not by scaling your resources

Product approach over complex tools

Platform teams are stitching together various point solutions with custom scripts, CI/CD pipelines and complex technologies due to a lack of platform solutions that provide a framework for them to work against.

Reduce operational overheads at scale

Creating infrastructure is easy, but managing and maintaining it in a self-service way is complex. Platform teams need a shift-left model to be able to safely rollout changes and enable teams to upgrade easily.

Team scaling to demand

As more requirements hit the team, so does the need to hire. Being able to hire the level of talent needed is difficult and time consuming. Scaling the assured self-service components reduce the need to scale the team.

Provide the integrations your teams need

Enable dynamic self-service capabilities

Get enabling teams in 6 steps!

Step 1

Isolate infrastructure between environments

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.

Step 2

Attach Cloud accounts to Team Workspaces

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.

Step 3

Create self-service infrastructure plans

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.

Step 4

Define policies and controls around teams

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.

Step 5

Import Terraform modules for self-service

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.

Step 6

Provide customised in-cluster services and deployment templates

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.

Integrate with existing IDPs

If you are already using an Internal Developer Portal such as Backstage, Port or Cortex - then you can integrate these existing ways of working into Wayfinder. Wayfinder has an API and a declarative YAML structure that will allow for you to integrate and use versioned API contracts to manage your Developers infrastructure needs.

Backstage
Cortex
Port

Familiarise yourself with more features...

Get familiar with other Wayfinder features