Workspaces & Tooling

A short URL that always resolves to the right place,
even when the destination changes

Quick Link Resolver is the tenant-private URL shortener. Type "go/payments-grafana" in any browser and you land on the current payments dashboard. Move the dashboard to a new URL? Update the resolver entry once. Every link in every Slack message, runbook, and docs page keeps working. The companion to Quick Links for cross-tool URL stability.

Get Started Talk to Sales
app.novaaiops.com / quick-link-resolver
● LIVE
Tenant
private namespace
Always
live (no caching)
Auditable
every redirect logged
Versioned
every change
How It Works

Browser shortcut + DNS + redirect

Engineers add the resolver as a browser shortcut (or use a corporate DNS pointing "go/" at the resolver). The shortcut sends "go/" to the resolver, which looks up the key and 302-redirects to the current destination. Lookups are sub-50ms; the resolver is one of the lowest-latency surfaces on the platform.

  • Browser shortcut: one-time setup; "go" becomes a search keyword that prefixes the resolver URL
  • Optional DNS: corporate DNS can resolve "go" to the resolver for organization-wide pickup
  • 302 redirect: sub-50ms lookup; never cached on browser-side so destination changes propagate immediately
app.novaaiops.com / quick-link-resolver · how
Versioning

Every change leaves a history

Each resolver entry has a version history: who changed it, when, why, what destination it pointed to before. Roll back to a prior version with one click. Useful when someone updates a key thinking it is unused, only for the "wait, that was load-bearing" message to land 5 minutes later.

  • Versioned destinations: every edit creates a new version; prior versions accessible
  • Rollback in one click: restore a prior version when an edit broke something
  • Audit log includes editor: who edited a key surfaces in the audit log; useful for "why does go/x point there?" investigations
app.novaaiops.com / quick-link-resolver · history
Click Analytics

Which keys are used, which are forgotten

Per-key click counts surface dead and live keys. Dead keys (zero clicks in 90 days) are candidates for archive. Hot keys (top 20 by click count) are candidates for org-wide promotion if they live at team-private. The analytics also help with "is this key worth keeping current?" decisions.

  • Click count per key: last 30 days, last 90 days, all-time
  • Dead-key archive: zero-click-in-90d keys flagged for archive review
  • Hot-key promotion: top-20 team-private keys suggested for org-wide promotion
app.novaaiops.com / quick-link-resolver · analytics
Tenant-Scoped

Your namespace is yours

Resolver entries are tenant-private. "go/payments-grafana" in tenant A and "go/payments-grafana" in tenant B can resolve to entirely different destinations; neither tenant sees the other's. The auth header on every lookup binds the resolver to the calling tenant. No cross-tenant leakage by construction.

  • Per-tenant namespace: every key is scoped to its tenant; same key can exist in multiple tenants
  • Auth on every lookup: lookup carries the tenant context; cross-tenant leakage is structurally impossible
  • Migrate by export: tenants moving environments can export their resolver namespace as YAML and re-import
app.novaaiops.com / quick-link-resolver · tenant
Video walkthrough coming soon

Subscribe to Nova AI Ops on YouTube for demos, tutorials, and feature deep-dives.

Stable URLs across a moving target

Dashboards move. Tools change vendors. Resolver keeps the shorthand stable so links written today still work next year.

Get Started Request a Demo