ssh.place: A Shared Pixel Canvas You Draw via SSH
08 Aug 2026
A canvas that only exists inside your terminal
A new Show HN project called ssh.place is making the rounds for a simple reason: it turns SSH — the protocol developers usually use to log into servers — into a collaborative art tool. There's no app, no website UI, and no account to create. You just SSH in, and you're drawing on a shared canvas with everyone else connected at that moment.
How it works
According to the report, ssh.place is built around a few deliberately minimal mechanics:
- Canvas size: 200×60 cells, shared by all connected users.
- Access: Any SSH key works — there's no signup or installation required.
- Controls: Keys 0–9 pick colors, and Tab cycles through all 16 available colors. The space bar places a solid block of the selected color.
- Cooldown: A 15-second cooldown applies per drawing element, and it's tied to the user's SSH key — not the connection — so reconnecting doesn't reset it.
- Text is blocked: The canvas rejects anything containing characters, restricting input to color drawing only.
- Where it lives: The canvas only changes over SSH — there's no separate web view mentioned.
It's essentially a terminal-native take on collaborative pixel-art projects, stripped down to color, placement, and a cooldown timer.
What's missing
The report notes several open questions that the announcement doesn't address: how long ssh.place has been live, who built it, what's powering it under the hood, and whether it has any real usage numbers (concurrent sessions, total pixels placed, etc.). There's also no stated policy on content moderation, no detail on whether the canvas resets periodically or persists indefinitely, and no explanation of how the system would hold up under heavy simultaneous SSH traffic.
Risks worth flagging
A few structural risks stand out:
- Moderation gap: With no stated moderation system, the canvas could be filled with unwanted or offensive content by anyone with an SSH client.
- Cooldown workaround: Because the 15-second cooldown is tied to the SSH key rather than the IP or account, a user could generate a new key to bypass it — suggesting the anti-spam mechanism may be easy to circumvent.
- Scalability unknowns: There's no mention of rate limiting beyond the per-user cooldown, which raises questions about how the service would perform under high traffic.
Why founders should care
Projects like ssh.place are unlikely to become standalone businesses, but they're a useful signal for builders thinking about friction, engagement, and distribution:
- It's plausible that removing every barrier to entry — no signup, no install, any SSH key works — meaningfully increases the odds that technical audiences will try a novel tool, even one with no clear utility beyond novelty.
- The interaction design (simple key-based color picking, a single cooldown rule) suggests that minimal feature sets can still produce an engaging shared experience, which may be a useful reminder for founders over-building MVPs.
- At the same time, the lack of disclosed moderation, persistence rules, or scaling plans likely indicates this is a hobbyist experiment rather than a production system — a reminder that clever distribution hooks (like an unusual access method) don't by themselves solve the harder problems of abuse prevention and scale that any real product eventually has to face.
For early-stage builders, ssh.place is less a case study in monetizable products and more a small, concrete example of how an unconventional interface — SSH instead of a browser — can create curiosity and word-of-mouth interest, even before questions of moderation, persistence, and scale are answered.