go/ for every team

Your team's link namespace,
without the DIY Postgres instance

Glnk gives every team their own go/ short link system — hosted, multi-tenant, zero ops. Stop maintaining your private golinks fork. Spin up a namespace in seconds.

Get started — it's free
acme-corp.golnk.dev
$ glnk init acme-corp
Namespace acme-corp ready at acme-corp.golnk.dev
 
$ go add jira https://acme.atlassian.net/browse/ENG-1234
Created go/jira → atlassian.net
 
$ go add hr https://drive.google.com/drive/u/0/folders/abc123
Created go/hr → drive.google.com
 
$ go list
go/jira atlassian.net … go/hr drive.google.com … go/onboarding notion.so … go/deploy render.com …
 
Live at acme-corp.golnk.dev

Everything a team needs.
Nothing they don't.

Team namespaces

Each team gets their own isolated link space. No collisions, no conflicts. Admin controls who can create and edit links.

Variable links

go/gh/$1/$2 maps to github.com/$1/$2. Parameter substitution works exactly like you'd expect.

Click analytics

Every link tracks clicks, referrers, and timing. Know what's actually being used and what's dead weight in your tool stack.

Chrome Omnibox ready

Type go/jira in your browser address bar and land exactly where you need to be. No extension required for most browsers.

Private links

Share links only with your team. Unlisted links visible only to org members — nothing leaks to public search.

SSO & permissions

GitHub OAuth out of the box. Role-based access — editors create links, viewers browse. Enterprise SSO available on paid plans.

Three steps to your team's link system

01

Claim your namespace

Pick a slug, connect GitHub OAuth. Your team's links live at {slug}.golnk.dev. Takes 30 seconds.

02

Create your go/ links

Add links via dashboard or CLI. Set variable patterns, privacy, and tags. Edit or retire links instantly — redirects update everywhere.

03

Share and use

Type go/jira in your address bar. Share verbally in standup. Paste in Slack. Links work everywhere your team does.

[ go/ ]

Stop copy-pasting long URLs.
Start linking like a team.

Every engineering team eventually builds this. Yours doesn't have to maintain it.