Give employees names such as go/handbook, zo/onboarding or team/benefits. Let Zogy host the directory, or run the same names on your own infrastructure.
Start a private directory with named teammates, explicit roles and personal read-only browser devices. The included workspace supports 20 members and 1,000 aliases.
Hosted access uses Grasany sign-in and current membership. Native internal hostnames need company browser policy or an IT-controlled gateway.
RUN ON YOUR INFRASTRUCTURE
Take the same names with you
Install the Node.js package behind company HTTPS and DNS. Configure your hostnames and company OIDC. Portable export/import moves aliases between hosted and self-hosted directories.
Requires Node.js 24+, a private durable data folder, one writer process and company HTTPS/network controls.
The same alias. Two separate companies.
Local simulation · No network request
Choose a company and resolve handbook.
Switch companies without changing go/handbook: each has its own destination. On real intranets, company gateway/browser configuration selects the company directory.
The work around the shortcut, included.
Control changes
Company-scoped aliases and explicit roles
Revision checks before edits and imports
Pause stale shortcuts without deleting names
Audited changes and private exports
Move without starting over
A portable hosted/self-hosted format
Previewed company-to-company imports
Read-only browser sync with expiring cache
Versioned downloads and recovery guidance
Start in your existing workspace
The included hosted directory supports 20 workspace members and 1,000 aliases. Company Links is separate from public zo.gy names: a short-code pass or subdomain does not create a company licence.
Commercial company plans
Commercial plans and managed support are not available for purchase yet. Start with the included hosted directory or the self-hosted source package within its documented limits.
Questions for your IT team
Can several companies use go/handbook?
Yes. Each has its own namespace. Hosted URLs and device tokens bind to the company identifier; self-hosted directories run in separate company infrastructure. A shared public router never guesses the company from an unscoped Host: go request.
What if we have no infrastructure?
Use the hosted HTTPS directory and browser extension. No company server is needed for those. Native bare hostnames require an IT gateway or browser policy; DNS alone cannot route paths or distinguish private companies on a shared host.
Can we move it in-house later?
Export the portable directory, review and import it into your installation, test the routes, then switch DNS/browser settings. Exporting does not erase or automatically disable the old service.
Will /alias work everywhere?
A bare /alias is relative to the current website. Use a configured hostname, company HTTPS address or the extension’s go + Tab command.
Does the extension work off-network?
It uses an authenticated session cache, refreshed every five minutes and expiring after at most fifteen. It does not bypass VPN or destination permissions. Extension-store distribution is not claimed.
Can admins install updates from the console?
The console checks the public release and shows its checksum, download and recovery guidance. Installation is manual. Publisher signing and a signed automatic updater remain separate work.