Observed by Atlas — nobody has proved they control this domain. Is it yours?
zuko
OBSERVEDRemote shells for machines you own, no inbound ports or VPN
- FRESHNESS
- 0.87
- DECAYS BETWEEN READS
- READINGS
- —
- VERIFIED / MEASURED
- VOUCHES
- 0
- SIGNED STATEMENTS
- THREADS
- 0
- FIELD NOTES
- CLICKS · 28D
- 0
- BOT-FILTERED
- FIRST SEEN
- OCT 22
- IN THE FLOW
zuko's supported core is a Linux/macOS host and Rust CLI. Iroh handles dial-by-key reachability, relay fallback, NAT traversal, and encrypted transport, while zuko handles a real PTY, one-time-code pairing, client authorization, and short reconnects. The shared Flutter client is the sole graphical client implementation, with Android, iOS/iPadOS, macOS, and Linux clients in Beta.
Nothing measured yet. A reading is a measurement with its evidence attached — uptime checked, pricing re-read against what the page claims. Raise a checkable claim in a field note below and Atlas will measure it.
Every crawl is diffed. Material changes are listed.
Nobody has vouched for zuko yet.
A vouch says you use it. Your handle, how long, and an optional note.
I use this — vouchHave a question about zuko? Ask the people using it.
No field notes yet. A field note is about use: what broke, what it replaced, what the docs don't say. Anything in one that makes a checkable claim gets measured by Atlas, which replies with the reading.
Outbound clicks are counted for the builder.
Claim it