Ship

Deploy to any cloud with one command.

wf up deploys to AWS, Azure, Google Cloud or Kubernetes with identity, policy and networking already set. Every environment is created from the same definition, so they do not drift.

Start free Book a demo

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

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

Today
1 to 6 monthsLead time from a commit to production for low-performing teams. Elite teams take under a day.
With Wayfinder
Under 10 minwf up deploys a new service to your own cloud. Timed on our reference deployment.
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

Before and after

Before

  • Weeks for a new environment
  • Staging that looks nothing like production
  • Long-lived cloud keys in CI
  • Preview environments nobody cleans up
  • Kubernetes clusters shared by email thread

With Wayfinder

  • Minutes from wf up to a running service
  • Dev, staging and production from the same manifest
  • Workload identity via OIDC, no static keys
  • A preview per branch, removed when it merges
  • Clusters imported, shared and scoped per workspace

How it works

Bind a cloud account

Trust Wayfinder's workload identity from your AWS, Azure or Google Cloud account. Nothing is stored either side.

Create an environment

Cluster-backed or cloud-only, named or auto-named, permanent or short-lived.

Deploy

wf up provisions the plans and deploys the components, in dependency order, and records the result.

In the product

acme / payments / Environments EnvironmentsAccess
  • D
    devAWS account acme-dev, eu-west-2. Rebuilt from the manifest on every merge.
    aws-eks-auto-cluster 1.0.9aws-rds 1.5.0aws-s3-secure 1.0.1
  • S
    stagingAWS account acme-staging, eu-west-2. Same manifest, staging values.
    aws-eks-auto-cluster 1.0.9aws-rds 1.5.0aws-s3-secure 1.0.1
  • P
    productionAWS account acme-prod, eu-west-2 and us-east-1. One plan behind staging, and the database parameter group was changed in the console on 21 Sep.
    aws-rds 1.4.0drift: 1 lineowner: checkout
  • PR
    pr-418Opened from the payment-api pull request. Removed when it merges, the record of what ran stays.
    short lived4h 12m oldowner: wayfinder

What this shows

  1. Every environment carries the plans it runs, at which version.
  2. Drift between environments shows up as a diff with an owner.
  3. Short-lived environments are removed on merge, and the record stays.

Components

Cloud account binding

OIDC trust from your account to Wayfinder. Roles live with you.

Environment

A place to run: a cluster namespace and a cloud scope, with its own variables.

Stack instance

One deployment of a manifest into an environment.

Kubernetes clusters

Import EKS, AKS or GKE, or let a plan create one. Share them per workspace.

Ephemeral environments

Created for a branch, torn down when it merges.

Networking and DNS

Private connections, public endpoints and records provisioned by plan.

Security and governance

One account per environment

Each environment reaches exactly one cloud account, under one identity.

Policy checks first

Policy checks run before anything reaches the cloud.

Approval for production

Production deployments can require an approval in the workflow.

Deployment record

Who deployed what, where, from which commit: recorded per instance.

More of the platform

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

Ship to your own cloud account today.

Start free, bind one account, and run wf up.

Start free Book a demo