New services from repo templates.
A golden path is a repo template the platform team maintains. Scaffold from it and CI, scanning and identity are wired before the first commit.
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.
- 2 minA new service from a template, with CI, scanning and identity already set up. Timed on our reference deployment.
You fill in
What lands
Before and after
Before
- A wiki page of setup steps, out of date
- CI copied from the last project
- Secrets pasted into the repo to get going
- Standards enforced by code review, if at all
- Every repo a little different
With Wayfinder
- One form: name, workspace, what it needs
- CI, scanning and CODEOWNERS from the template
- Workload identity created with the repo
- Standards live in the template, pinned by version
- Bump the template and pull requests roll out
How it works
Choose a path
Pick the template for the kind of service: web, API, worker, data job.
Choose what it needs
A database, a queue, a bucket. Each is a plan from the catalogue.
Get the repo
Wayfinder creates the repository, the workspace wiring and the first environment.
In the product
- PRBump aws-rds plan 1.4.0 to 1.5.0 across 12 servicesValidated against real usage in a replica of each. Evidence attached.12 of 12 passedPostgres 16owner: platform
- PRGolden path node-service 3.2 to 3.3, 9 reposCI template and scanner config updated in every repo pinned to it.9 PRs raisedTrivy 0.58
- DRDrift: uploads bucket versioning turned off in prodChanged outside Wayfinder on 21 Sep. Diff and owner attached, fix ready to apply.owner: checkout1 line diff
What this shows
- A template bump raises a pull request in every repo pinned to it.
- Each pull request carries what changed and why, with the evidence.
- Repos that drifted from the template show up with an owner and a diff.
Components
A versioned starting point for a service, composed from smaller templates.
CI, scanning, identity and manifests as separate templates, pinned together.
A template the platform team stands behind, offered in the catalogue.
The one-step creation of repo, workspace and environment.
Every repo records which template version it came from.
Bump a template, Wayfinder raises the pull requests.
Security and governance
The repo is created by Wayfinder under a scoped identity, not a personal token.
Scanning and branch protection come from the template and cannot be skipped.
Template changes are reviewed once, then applied everywhere by pull request.
Which template, which version, which owner: recorded per repo.
Create a service from a template.
Start free and create one template the whole team can start from.