Ship

One manifest, one command, and your coding agent.

wayfinder.yaml says what the app needs. wf up deploys it. Your coding agent can do both through Wayfinder's own MCP server, under your RBAC.

Start free Book a demo

Free forever plan, no commitment, in your own cloud account.

Built from the real interface. Open the demo tenant in the live demo. No sign-in.

Today
Weeks or monthsLead time to production for 68% of engineering teams.
With Wayfinder
Under 10 minwf up deploys a new service to your own cloud. Timed on our reference deployment.
$ wf mcp setup
  ok  Wayfinder MCP server registered with Claude Code
  ok  tools: list resources, validate manifest, run wf commands
  ok  acting as jon@acme, under your RBAC

$ wf init --ai
  detected  frontend (Node 20)   api (Go)   postgres
  ok  wayfinder.yaml written, 3 components, 0 secrets in the repo

$ wf up
  environment dev-busybeaver ready in 4m 12s

Before and after

Before

  • Environment config copied per environment
  • Cloud consoles and kubectl side by side
  • Secrets in .env files and CI variables
  • Coding agents that stop at the pull request
  • New joiners learning five tools

With Wayfinder

  • One manifest, variables and secrets by scope
  • wf up creates the environment and deploys
  • Secrets set once, referenced by name
  • wf mcp setup: your agent runs wf commands, as you
  • One tool, and the agent already knows it

How it works

wf init

Wayfinder reads the repo, finds the components and drafts wayfinder.yaml with the right plans.

wf up

Creates the environment if it does not exist, provisions the plans, deploys the app, remembers it for next time.

wf mcp setup

Registers Wayfinder's MCP server with Claude Code, Cursor or any MCP client. The agent lists resources, validates manifests and runs wf commands under your permissions.

In the product

acme / checkout-web / dev-busybeaver
AWSAzureGCPK8s
frontendcheckout.dev-busybeaver.acme.wayfinder.runDeployed via wf up, 4m 12s
apiGo, 2 replicas, workload identityDeployed via wf up, 4m 12s
postgresplan aws-rds@1.2.0, from your moduleProvisioned, 3m 40s
uploadsplan aws-s3@1.0.1, from your moduleProvisioned, 48s

What this shows

  1. Components from the manifest become nodes: app, api, database, bucket.
  2. Plans show which module version they came from.
  3. The whole stack came from one file and one command, and can be torn down with wf down.

Components

wayfinder.yaml

Components, their plans and their wiring. No per-environment copies.

Variables and secrets

Set by scope with wf set var and wf set secret. Referenced by name.

wf up and wf down

Create, deploy, iterate, remove. State remembered in .wfup.

Environments

Auto-named or named, cluster or cloud-only, short-lived or permanent.

MCP server

Wayfinder's own. Tools for coding agents, running as the developer.

Templating

Reference sibling outputs with ${{ .Components.db.host }}; dependencies are inferred.

Security and governance

Runs as the developer

The CLI and the MCP server act as the signed-in developer, never more.

Agent calls logged

A coding agent's tool calls are recorded like any other action.

Secrets by reference

Secrets never enter the repo or the agent's context; they are referenced by name.

Validated before it runs

wf validate catches a manifest that would exceed the workspace's permissions before it runs.

More of the platform

WorkflowsCloud resource plansRepo templateswayfinder.yaml and the CLIEnvironmentsAI agentsIntegrationsUpgrades and driftSecurity and governance

Run wf up on a repo today.

Start free, wire your coding agent, and ship from the manifest.

Start free Book a demo