# pro.webssh.net: the GitHub home of WebSSH, an SSH client for Apple platforms > This repository is not the application source in any meaningful sense, it is the front door of a commercial SSH client for macOS, iOS and iPadOS, a place to report bugs and to sponsor the work. The code that is here is the JavaScript of the interface layer, not the product you install. **isontheline/pro.webssh.net** — iOS / iPadOS / macOS SSH Client - Repository: https://github.com/isontheline/pro.webssh.net - Website: https://apps.apple.com/us/app/id497714887 - Stars: 666 · Forks: 85 - Language: JavaScript - License: MIT - Published: 2026-10-21 · Updated: 2026-10-21 · Language: en - Canonical page: https://hysenlabs.com/projects/isontheline-pro-webssh-net ## A repository whose stated job is bug reports The README is unusually explicit about what this repository is for. It says the repository should be used to report any issue with the use of the WebSSH application, and it points at the issue tracker on GitHub for that purpose. That is the key to reading the project. The application itself is a commercial product distributed through the App Store, listed under id 497714887, and the repository is where the community and the developer meet around it. The documentation lives on its own site at webssh.net, and the README also offers a route to become an external beta tester for anyone who is not afraid to try a pre-release build. The product is described as an SSH, SFTP and port forwarding client for macOS, iOS and iPadOS, with the tagline SysAdmin Toolbox. The audience is people who administer systems from an Apple device, which is a narrower and more specific group than the general SSH client population, and the multi-device framing matters because the same app covers a phone, a tablet and a desktop. The topic list backs the description up with the technical vocabulary: ios, ipados, macos, ssh, sftp, terminal, webssh, and the xterm and xtermjs tags that tell you what the interface layer is built on. ## What is in src, snippets and statebar The repository layout explains the relationship between the code and the product. The top-level entries are a `src` directory, a `snippets` directory, a `statebar` directory, a `documentation` directory, an `.appstoreconnect` directory, a `star-tracker.yml` file, and the usual `.github` and `.gitignore`. The primary language of the repository is JavaScript, and the topics list includes xterm and xtermjs, which is the terminal emulator that a browser or native web view based client would embed to render a shell session. The `statebar` directory name points at the status bar of the application, and `snippets` at reusable pieces of code or documentation snippets rather than a complete application tree. The `.appstoreconnect` directory holds the App Store Connect material, and the screenshots in the README are read from it: `webssh-macos.jpg`, `webssh-ipados.jpg` and `webssh-ios.jpg`, one per platform, each described as a WebSSH SSH, SFTP and port forwarding client screenshot. What is not in the tree is as telling as what is. There is no server component, no native networking code and no product build system, so an engineer looking for the implementation of an SSH client will not find one here. The visible JavaScript is the interface layer of a shipped application, not a library you can depend on. ## The documentation site is where the real answers are The README points readers to the documentation at webssh.net, and it does so in the list of things the repository is for, alongside reporting issues. That placement is the important part. The repository is a thin surface, and the substance of how the application works is expected to live in the documentation site. The same pattern shows in the beta tester route. The README offers a link to a page on becoming an external tester, which is the standard way a single-developer product recruits people to exercise pre-release builds. For a project without an internal QA organisation, external testers on real devices are how bugs in the field get found, and the fact that the route is public and documented is a sign the project wants that loop to be wide. The same pattern shows in how bugs are handled. The README says to report any issue with the use of the application, which points at the GitHub issue tracker. The one repository-native piece of tooling is `star-tracker.yml`, which drives the Star History chart embedded in the README. That is a small detail, and it is the only piece of automation described in the README itself. ## A one-time purchase, funded by sponsors The funding model is stated plainly. WebSSH PRO is a one-time purchase, and the README asks that if you like the app and want to support the project further, you consider sponsoring it through the project's GitHub sponsors page, with the reason given as helping to keep it alive and improve it. That framing explains the structure of the repository. A one-time purchase with no subscription has no recurring revenue to fund maintenance, so sponsorship stands in for it, and the public repository is where that community is visible. The README repeats the ask in the Sponsors section, saying every contribution, even a small one, is greatly appreciated and will help keep the project alive and improve it. For a buyer, the practical reading is that this is a single-maintainer product with a funding model you can participate in, and the MIT licence on the repository is a licence on whatever code the repository does contain, not a promise about the application as a whole. The application is sold through the App Store, and the licence of a commercial app in the store is a separate question from the licence of the files in this repository. ## MIT licensed, no releases, and a branch pushed yesterday The licence is MIT, with the LICENSE file at the root of the repository. The repository is not archived and the last push was on 2026-10-20, so the public surface of the project is being kept current even though the product itself ships on its own schedule through the App Store. There are no GitHub releases, and that is consistent with the repository not being the product. Release notes for an App Store application live in the store listing and in the documentation site, not in tags on a repository of screenshots and interface code. The default branch is master, and the visible work is what you would expect for a project that tracks a shipped app: screenshot refreshes for the store listing, documentation updates, and the small interface-level code changes that go with them. The star tracker configuration and the App Store Connect assets are maintained in the same tree. One thing an evaluator should be clear about: the branch being current tells you the project is alive, but it does not tell you that the SSH, SFTP and port forwarding implementation is available under any licence. It is not, and the repository does not claim otherwise. ## Conclusion This repository is worth using as the contact point for WebSSH Pro if you already own the app, because that is exactly what it is for, and the issue tracker there is the route the project asks users to take. It is the wrong place to look for the implementation of an SSH client you intend to build on, since the repository is a public front for a closed commercial product with only interface-level JavaScript visible. Verify first that the app you are buying is the one this repository tracks, check the documentation site for the current platform and feature set, and read the MIT licence file to see exactly which parts the licence covers. ## FAQ ### What is the pro.webssh.net repository for? The README says the repository should be used to report any issue with the use of the WebSSH application. Documentation is at webssh.net, and the app itself is sold through the App Store under id 497714887. ### Which platforms does WebSSH support? The README describes WebSSH as an SSH, SFTP and port forwarding client for macOS, iOS and iPadOS, and the repository contains a separate screenshot for each of the three platforms under the .appstoreconnect screenshots directory. ### How do I become a beta tester for WebSSH? The README links a page on becoming an external tester on the documentation site at webssh.net, described as an option for anyone who is not afraid to try a pre-release build. ### How is WebSSH PRO paid for and how is it supported? WebSSH PRO is a one-time purchase, and the README asks users to consider sponsoring the project through GitHub sponsors, with the stated reason being to help keep it alive and improve it. ### What licence applies to the code in the pro.webssh.net repository? MIT, with the LICENSE file at the repository root. The repository is not archived, its last push was on 2026-10-20, and it has no GitHub releases because the repository is not where the product itself is versioned. ## Sources - [isontheline/pro.webssh.net on GitHub](https://github.com/isontheline/pro.webssh.net) - [Issues](https://github.com/isontheline/pro.webssh.net/issues) - [License: MIT](https://github.com/isontheline/pro.webssh.net/blob/master/LICENSE) - [Project website](https://apps.apple.com/us/app/id497714887) - [README](https://github.com/isontheline/pro.webssh.net/blob/master/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/isontheline-pro-webssh-net