This name is reserved for the Daytona side of the T3 Code remote-execution setup. Nothing Daytona-specific is installed here yet.
Why: Daytona no longer ships a standalone self-hosted server. The only
"own compute" option today is Bring Your Own Compute — a Kubernetes cluster running
the daytona-region Helm chart (proxy, runner DaemonSet, snapshot manager,
SSH gateway) that registers itself with Daytona Cloud's control plane. It needs a
wildcard DNS name and TLS, a LoadBalancer for the SSH gateway, and several GB of RAM,
and it does not change the sandbox network policy — which is what blocks the
sandboxes from dialing the control plane on this host.
The control plane for T3 Code lives at
t3code.n0xeid.xyz
(it answers 401 without the bearer token).