dash2 — sign in

Gated by Google + allowlist. 4 accounts allowed (pk-only).

Powered by packages/auth-allowlist (brain2pk Firebase project, 4 ALLOWED_EMAILS hard-fence). If you don't have access, this list is intentionally short — pk-only.

Signed in as ·

dash2.eduz.ai

Read-mode dashboard — devices, machines, fleets, tunnels. Write counterpart is cp2.eduz.ai.

…devices registered

…enabled

…with Tailscale

…static WAN IP

Devices

id	label	owner	role	OS · RAM	LAN	Tailscale	backbone	status
loading…

Connection strategy

loading…

What's in this dashboard

Source: ../../packages/machines-client/src/config/devices.json — registered device inventory.

Auth: Firebase Auth + allowlist (packages/auth-allowlist). Sign-in popup → Google → email ∈ ALLOWED_EMAILS → access.

Read vs write split: this surface displays. cp2 performs (onboard, lock, tunnel up/down).

v1 ideas (when there's a backend Worker):

Live reachability ping per device (Tailscale path / LAN path)
CF Tunnel health badges (uses tunnel_health.py from machines-client)
Onboard status per device (ufw / fail2ban / key-only sshd present?)
Last-seen timestamp from a heartbeat agent

Part of the eduz 2-series. Source data devices.json is duplicated into apps/dash2/ at deploy (CF Pages serves static, no cross-folder fetch).
Repo: github.com/zexp1/experiments2 · See 2.eduz.ai for full inventory.