whatisgithub

What is waypoint?

hashicorp/waypoint — explained in plain English

Analysis updated 2026-06-26

4,728GoAudience · ops devopsComplexity · 4/5Setup · hard

In one sentence

A now-discontinued HashiCorp tool that let teams define how to build, deploy, and release an application in a single config file, targeting Docker, Kubernetes, AWS, Azure, and Google Cloud.

Mindmap

mindmap
  root((Waypoint))
    What it does
      Build apps
      Deploy apps
      Single config file
    Status
      Discontinued
      Replaced by HCP Waypoint
    Supported Targets
      Docker Kubernetes
      AWS Azure
      Google Cloud Run
    Tech Stack
      Go
    Audience
      DevOps teams
      Platform engineers
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Study the source code of a real-world Go deployment tool to understand how multi-cloud deploy abstractions are built.

USE CASE 2

Migrate an existing Waypoint Community Edition setup to HCP Waypoint before the unmaintained version drifts further.

USE CASE 3

Use the archived Waypoint config format as a reference when designing your own unified build-deploy pipeline.

What is it built with?

Go

How does it compare?

hashicorp/waypointgo-gomail/gomailtophubs/toplist
Stars4,7284,7304,726
LanguageGoGoGo
Setup difficultyhardeasyhard
Complexity4/52/54/5
Audienceops devopsdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1day+

No longer actively maintained, requires Go toolchain and Docker Compose to build from source. Use HCP Waypoint for production.

So what is it?

Waypoint was a tool from HashiCorp that let developers describe how their application should be built, deployed, and released, all in a single configuration file. Instead of writing different scripts for each hosting platform, a team could define the full lifecycle once and run it consistently across environments. The tool supported a range of build methods and hosting targets, including Docker, Kubernetes, AWS, Azure, and Google Cloud Run. Plugins made it possible to add support for other platforms. It ran on Linux, macOS, and Windows. Waypoint Community Edition is no longer actively maintained. HashiCorp has moved to a new direction called HCP Waypoint, which is a cloud-hosted version. The README points readers to a blog post and separate documentation site for information about that newer product. For anyone exploring the source code of the original project, it was written in Go. Building it locally required Go tooling and either a NixOS environment or running a provided setup command. Tests relied on Docker Compose to start supporting containers before the test suite ran.

Copy-paste prompts

Prompt 1
I have an existing Waypoint Community Edition deployment. What steps do I follow to migrate to HCP Waypoint?
Prompt 2
Show me what a Waypoint config file looked like for deploying a Docker container to AWS ECS, I want to understand the format before migrating.
Prompt 3
How do I build and run the open-source Waypoint server locally from source using Go and Docker Compose?
Prompt 4
What alternatives to HashiCorp Waypoint Community Edition should I consider for a unified build-deploy-release pipeline today?

Frequently asked questions

What is waypoint?

A now-discontinued HashiCorp tool that let teams define how to build, deploy, and release an application in a single config file, targeting Docker, Kubernetes, AWS, Azure, and Google Cloud.

What language is waypoint written in?

Mainly Go. The stack also includes Go.

How hard is waypoint to set up?

Setup difficulty is rated hard, with roughly 1day+ to a first successful run.

Who is waypoint for?

Mainly ops devops.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.