Integrations

What Wayfinder connects to. Today, and next.

Wayfinder sits between your developers and your clouds. What we connect to today, and what's landing on the next release.

Start free → Talk to us

Free forever · No commitment · Upgrade anytime

Available today

What ships in the current release.

The integrations that make the core platform run - clouds, clusters, IaC, AI providers, identity and secrets.

Clouds

Bring your own AWS, Azure or GCP account. Wayfinder runs in your cloud, not in ours.

  • AWS
  • Azure
  • GCP

Kubernetes

Managed clusters across the big three, or import an existing cluster and share it across workspaces.

  • EKS
  • AKS
  • GKE
  • Import existing

Infrastructure as code

Plans wrap Terraform or OpenTofu modules. Choose either as the provider behind a CloudResourcePlan.

  • Terraform
  • OpenTofu

Helm

KubeResourcePlans deliver workloads via Helm charts. Use the upstream community charts or your own private repos.

  • Helm 4
  • OCI repos
  • HTTP repos

AI providers

Pick the LLM that fits your tenant. Bring your own API key, change provider any time.

  • Anthropic Claude
  • Google Gemini

IDE agents (MCP)

Wayfinder ships its own MCP server. wf setup mcp wires it into whichever coding agent you use, under your RBAC.

  • Claude Code
  • Cursor
  • VS Code
  • Windsurf
  • Antigravity

Identity

SSO via your IdP. Workload identity federation to AWS, Azure and GCP - no static cloud keys at runtime.

  • SSO / OIDC
  • AWS IAM (OIDC)
  • Azure managed identity
  • GCP workload identity

Secret storage

Envelope encryption with your own keys. Wayfinder never holds cleartext.

  • AWS KMS
  • Azure Key Vault
  • Local encryption

DNS

Manage DNS zones in the same cloud providers your workloads run in.

  • AWS Route 53
  • Azure DNS
  • Google Cloud DNS
Next release

Connect Wayfinder to anything else.

The next release opens Wayfinder up: outbound to any HTTP or MCP server, inbound webhooks from any system, a first-class GitHub integration, and reusable HTTP actions you can invoke from Workflows.

Next release

HTTP integration actions

Reusable, declarative actions you author once and invoke from workflows or lifecycle hooks. Slack post-message, ServiceNow raise-incident, Infracost cost-estimate, or any HTTP endpoint - each with typed inputs (e.g. a CloudResourcePlan variable).

Next release

Webhooks (inbound)

Push data into Wayfinder, trigger actions from outside. Stand up an environment when a Jira ticket moves; refresh a plan when a vulnerability scan lands. Payloads land as ResourceData and can fire workflow triggers.

Next release

External MCP servers

Register any MCP server: AWS Knowledge MCP, GitHub's MCP, your own internal services. Wayfinder routes them through the agent executor with auth handled, and Bring-Your-Own-Agent can bind directly to them.

Next release

GitHub

First-class source control wiring: repo discovery, Stack Definition pull, raise pull requests from a workflow, react to GitHub events. Short-lived GitHub App tokens for the agents that need them.

Want to influence what we wire up next? Tell us what you'd integrate - the design is still flexible.

Wayfinder runs where your work runs.

Start on the free tier - see what's wired up today, plan for what's coming next.

Start free → Book a demo

Free forever · No commitment · Upgrade anytime