Go packages on your domain.
Use a hostname you own in your dependencies, and point it at your git forge.
What go get sees
go get go.example.com/org/repoExamples use a repository named org/repo. Replace it with your own repository and required package metadata.
How setup works
Create an account, choose your hostname and forge, prove DNS control with a TXT record, and point the CNAME at go.packageurls.com. Wait for the certificate before trying your vanity URL.
Limits to know
Go reads go-import metadata to find the forge. First adopt the vanity module path in go.mod and imports; later forge moves can retain that path. Private modules still need the appropriate GOPRIVATE configuration and forge credentials.
Package URLs does not host a package registry or proxy git content. Your package manager authenticates with your forge. A hostname maps the first owner/repo path segments to the forge; nested GitLab groups are unsupported.