Skip to main content

Quick links

The fleet's operational surface, one table. Every URL is tailnet-only: reach it from a tailnet device, authenticate with the fleet SSO where the app asks.

ComponentURLWhat it is
Forgejohttps://forgejo.i.shikanime.studioGit forge
Grafanahttps://grafana.i.shikanime.studioDashboards
Logshttps://logs.i.shikanime.studioVictoriaLogs query
Metricshttps://metrics.i.shikanime.studioVictoriaMetrics
Fluxhttps://flux.i.shikanime.studioGitOps reconcile state
Honchohttps://honcho.i.shikanime.studioAgent memory server
Inferencehttps://inference.i.shikanime.studioLLM gateway, mTLS and API key
Automatahttps://automata.i.shikanime.studioAgent hub VM
Vaultwardenhttps://vaultwarden.i.shikanime.studioInteractive secrets
Autheliahttps://authelia.i.shikanime.studioFleet SSO
LLDAPhttps://lldap.i.shikanime.studioDirectory admin
Blockyhttps://dns.i.shikanime.studioDNS sinkhole
Longhornhttps://longhorn.i.shikanime.studioStorage

Media and collaboration apps follow the same pattern — jellyfin, immich, synapse, copyparty, the *arr stack all live under *.i.shikanime.studio. Pages that go deeper: Catalog for the full service list, Observability for the metrics pipeline, Gateways for how these names resolve.