u/Pale_Stranger_4598

Image 1 — Termy – more than SSH client (native btw)
Image 2 — Termy – more than SSH client (native btw)

Termy – more than SSH client (native btw)

Most SSH clients on Mac are either Electron wrappers or generic terminal apps with SSH bolted on. I wanted something that felt like it belonged on macOS, so I spent 6 months developing my product solo.

"Native" gets thrown around a lot, so to be specific about what I mean: the whole app is Swift/SwiftUI, including the terminal emulator (not a libvterm fork, not xterm.js in a WebView) and the Mosh client (own implementation in Swift with a complete framebuffer mirror). No Electron, no web shell, no hidden Chromium.

A few things I'm proud of under the hood:

- SSH stack on top of Citadel + a fork of swift-nio-ssh with a window-adjust patch and a custom RSA path for legacy key formats some servers still hand out

- Own SOCKS5 server written in Swift (RFC 1928 + 1929 auth) for dynamic forwards, so `ssh -D` works without shelling out to /usr/bin/ssh

- Active tunnels (local / remote / dynamic) get snapshotted and restored on reconnect, so dropping Wi-Fi at a cafe doesn't kill your forwards

- Smart Reconnect that survives a cold launch, not just a network blip

- ProxyJump multihop with a runtime session graph

- Multi-host broadcast with a diff view across panes

- FIDO2 / sk-* hardware keys via libfido2

- SFTP File provider

- Built-in S3 client (AWS + R2 + B2 + Wasabi + MinIO + custom endpoints) with a real object browser, multipart uploads, versioning/lifecycle/CORS/encryption settings, presigned URLs and ACL/tag editors. Same window as your SSH sessions

- Keys live in the macOS Keychain (iCloud sync off by design), can be generated inside the Secure Enclave with Touch ID required on every signature, or imported from existing OpenSSH files. Passphrase-protected ones decrypted in-app

Solo project, so honest feedback on what feels off is genuinely useful. Happy to answer technical questions in the comments.

ProductHunt: https://www.producthunt.com/products/termy

Termy is now available in EAP: termyapp.com
Code MACOSAPPS50 is 50% off any plan for the first 25 purchases.

u/Pale_Stranger_4598 — 3 days ago

i made my own devops cockpit as a solo dev

I kept doing the same thing on every box: ssh in, then htop, df, ss, docker ps.

Termy is a native Mac app. Connect over SSH and it snapshots the host: disks, processes, ports, services, containers. Nothing gets installed on the server.

A lot of posts here are "I got tired of my own workflow, so I shipped it." That's this.

https://termyapp.com

If you want a paid plan: SIDEPROJECTS50, 50% off, 20 uses.

u/Pale_Stranger_4598 — 3 days ago

native macOS app for managing servers, feedback on density and layout

hey everyone. I've been designing a native macOS app for working with remote servers (SSH, files, databases, containers and etc.), and the hardest part has been information density, there is a lot to show without it turning into a wall of controls or something like airplane cockpit.

A few decisions I'd love feedback on:

- Split panes instead of tabs, so you can watch several things at once. The tradeoff is each pane gets narrow, so I cap detail inspectors and let rows reflow.

- One dark theme built around a single warm accent, with frosted/translucent surfaces for depth. I tried to keep every list, header, and inspector using the same row idiom so nothing feels bolted on.

- Right-side inspectors for details instead of modals, to keep you in context.

My main worry is whether it reads as calm or just busy. Where would you cut? Anything that feels inconsistent or visually noisy?

Screenshots attached. Happy to explain any specific screen.

u/Pale_Stranger_4598 — 3 months ago

Showcase: Termy – Fully native SSH client for Mac.

Hosts Tab.

Most SSH clients on Mac are either Electron wrappers or generic terminal apps with SSH bolted on. I wanted something that felt like it belonged on macOS, so I've been building Termy as a solo project.

"Native" gets thrown around a lot, so to be specific about what I mean: the whole app is Swift/SwiftUI, including the terminal emulator (not a libvterm fork, not xterm.js in a WebView) and the Mosh client (own implementation in Swift with a complete framebuffer mirror). No Electron, no web shell, no hidden Chromium.

A few things I'm proud of under the hood:

- SSH stack on top of Citadel + a fork of swift-nio-ssh with a window-adjust patch and a custom RSA path for legacy key formats some servers still hand out

Terminal window

- Own SOCKS5 server written in Swift (RFC 1928 + 1929 auth) for dynamic forwards, so `ssh -D` works without shelling out to /usr/bin/ssh

- Active tunnels (local / remote / dynamic) get snapshotted and restored on reconnect, so dropping Wi-Fi at a cafe doesn't kill your forwards

Topology tab

- Smart Reconnect that survives a cold launch, not just a network blip

- ProxyJump multihop with a runtime session graph

- Multi-host broadcast with a diff view across panes

- FIDO2 / sk-* hardware keys via libfido2

- SFTP File provider

SFTP File provider

- Built-in S3 client (AWS + R2 + B2 + Wasabi + MinIO + custom endpoints) with a real object browser, multipart uploads, versioning/lifecycle/CORS/encryption settings, presigned URLs and ACL/tag editors. Same window as your SSH sessions

S3 Client

- Keys live in the macOS Keychain (iCloud sync off by design), can be generated inside the Secure Enclave with Touch ID required on every signature, or imported from existing OpenSSH files. Passphrase-protected ones decrypted in-app

Keys tab

Solo project, so honest feedback on what feels off is genuinely useful. Happy to answer technical questions in the comments.

reddit.com
u/Pale_Stranger_4598 — 3 months ago