Docs

Use cases

Reach a machine by ~name. Be a member of its mesh. Inbound stays closed to everyone else. The machine does not need a public port.

Buddy backup

Keep a copy on a friend, or on another machine you run. They add you. You azi mesh accept. scp or rsync to the installed name. SCP.

rsync -a ~/photos/ zod.azimov.network:~/backup/photos/

The files land on their disk.

Plex and Jellyfin

Run the server at home. Have it listen on the overlay address. A service bound to localhost stays on that machine. Ports.

An installed peer answers on the kernel interface as zod and zod.azimov.network. Open that host and the port from a player on a joined machine. A pending peer does not answer. Jellyfin’s usual port is 8096. Plex’s is 32400.

Devops

A shell on a build box or a VPS with SSH closed to the internet.

azi ssh ~box

Stock ssh and git use zod.azimov.network once the peer is installed. SSH. Direct when both machines can reach each other. A galaxy relays the rest.

Other services

A git remote, a dashboard, an admin UI: TCP to the overlay address and port. Same membership as ports. Today a member can reach that address. Choosing ping, a shell, a port, or exit per name is on the roadmap.

Exit

Send public traffic through a friend whose exit bit is on. LAN and the overlay stay on your ordinary route. Exit.