FAQ
Questions we keep getting. If yours isn't here, drop us a line.
SlashGo is team navigation: go/docs, go/okrs, go/oncall. It is built around memorable internal paths, org membership, browser resolution, and team adoption.
Yes — via one of three paths: (1) The Chrome extension intercepts http(s)://go/<slug> and rewrites to slashgo.io. Needs `go` to point somewhere in DNS — usually /etc/hosts or an MDM policy. (2) If that fails, Chrome falls back to a Google search. The extension catches that search URL and redirects. Works without any DNS setup. (3) Omnibox keyword — type `go <slug>` in the address bar. No extension needed.
No. The omnibox keyword path works without it. Everything else works better with it.
The 21st person joins normally. Owners and admins see a banner asking them to upgrade to Pro for $5/mo. We never fail an invite to force an upgrade.
No. Full daily / weekly / monthly click analytics on every tier, including Free.
At rest, yes. AES-256. Plaintext is only decrypted at redirect time.
Not yet — Chrome only. Firefox and Edge are on the roadmap and reuse the same rules.json.
Yes. slashgo exposes a signed read-only MCP endpoint via cmdline. Agents can resolve go/ slugs without a user login.
Email us. Team is self-serve, and billing questions go through the account page.