Self-service plans from your Terraform modules.
Point Wayfinder at a module. It drafts the plan, you fix the values that matter, and every team can order it from the catalogue.
Free forever plan, no commitment, in your own cloud account.
Built from the real interface. Open the catalogue in the live demo. No sign-in.
- Today
- 1 day or more78% of engineering teams wait this long for help from the platform team.Port, State of Internal Developer Portals, 2025
78% of engineering teams wait a day or more for SRE/DevOps assistance; Only 22% report getting issues resolved within one day; 16% experience maximum wait times of a week or more
Engineering teams surveyed by Port; sample size not published on the page - With Wayfinder
Wayfinder timings are from our reference deployment and demo flows, not from customer studies.
- Under 10 minA database, queue or cluster from your own Terraform module, without a ticket. Timed on our reference deployment.
Catalogue
Browse available resource definitions and packages
aws-eks-auto-clusterSuccessAWS EKS Auto Cluster with AWS-managed nodes
aws-s3-secureSuccessS3 bucket with unique names, read and read-write policies
aws-api-gateway-lambdaSuccessHTTP API Gateway with Lambda proxy integration
cluster-rbacSuccessDefault cluster roles for workload deployments
gcp-app-configSuccessGCP Cloud Storage bucket for application configuration
azure-config-storeSuccessAzure Storage Account for configuration as JSON blobs
apiVersion: v1
name: payment-api
components:
cluster:
type: CloudResource
plan: aws-eks-auto-cluster@1.0.9
storage:
type: CloudResource
plan: aws-s3-secure@1.0.1
api-gateway:
type: CloudResource
plan: aws-api-gateway-lambda@1.1.13
- StackInstance "payment-api" status changed: Pending → Success
- StackInstance "payment-api": All deployment actions taken
- Deployed via wf up, 4m 12s
Before and after
Before
- A ticket to platform for every database
- Terraform copied between repos and drifting
- Values nobody remembers the reason for
- Weeks from request to running resource
- No record of who provisioned what
With Wayfinder
- Teams pick a plan from the catalogue
- One module, one version, every consumer
- Encryption, networking and backups fixed by you
- Minutes from wf up to a running resource
- Every instance tied to a workspace and an owner
How it works
Point at a module
Give Wayfinder your Terraform or OpenTofu module. It reads the variables and drafts a plan.
Fix the values you own
Lock the values the platform team owns: engine, encryption, network, backups. Leave the rest to the team.
Publish a version
Teams reference it as aws-rds@1.2.0 in wayfinder.yaml. Bump the version and every consumer can follow.
In the product
Fixed by the platform team
Filled by the team
Module
What this shows
- The inputs you fixed are not editable by the team, and the plan says why.
- The inputs the team fills are the only questions they are asked.
- Usage shows every stack on this version, so a bump has a known blast radius.
Components
A versioned template for a cloud resource, drafted from your module.
The same idea for a Helm chart: a Kubernetes package with fixed values.
A wayfinder.yaml naming the plans an application needs.
One deployment of a stack into an environment, with its own state.
Everything teams can order, filtered by cloud, type and tag.
The plan editor reads the module and proposes inputs, descriptions and defaults.
Security and governance
Plans run with the workspace's workload identity, never a shared key.
A plan can only reach the cloud account its environment is bound to.
Changing a fixed value needs a new plan version and an approval.
Every instance records who ordered it, from which version, when.
Publish your first plan today.
Start free, point Wayfinder at one module, and order it from the catalogue.