Tailscale
private mesh / accessConnect machines across different networks without publishing administrative services to the public internet.
INFRASTRUCTURE
A self-hosted laboratory for deployment, networking, containers, backup and recovery. The public view shows roles without exposing sensitive topology.
NODES
Public routes and origin boundaries.
Architectural roleAplicações, serviços web, observabilidade e cargas em contêineres.
Operacional — verificado ao vivo em 06/08/2026Ambiente local de apoio, monitoramento e continuidade.
Inventariado — acesso ao vivo não confirmado nesta execução · name under reviewJogos, aplicações e capacidade complementar do laboratório.
Operacional — verificado ao vivo em 06/08/2026STACK
Not a generic cloud-stack list.
Connect machines across different networks without publishing administrative services to the public internet.
Publish only services that need public routes while keeping origins behind the edge.
Keep services isolated, movable and recoverable through reproducible definitions.
Keep versioned snapshots, verify integrity and treat restore as the acceptance criterion.
Use explicit control where needed and simpler TLS/reverse proxying for smaller services.
Turn “it should be online” into observable checks and history.
Separate game-server lifecycle from the general web stack.
Keep a low-level path for diagnosis, maintenance and recovery.