Ship a command-line for your web app in one hour, not months 🚀

Now a single developer can create command-lines as polished as stripe, heroku, and github with their favorite language or web framework in an afternoon.

Trusted by TRMNL

How Terminalwire made a command-line interface possible for an ambitious hardware startup

After a successful Kickstarter, TRMNL had to fulfill 1,325 orders for a WiFi-enabled e-Ink display—while also delivering a developer-friendly SDK for custom visualizations. Terminalwire cut development time from months to days, making the impossible possible.

With Terminalwire, a bootstrap company can have a CLI on day one.Read how Terminalwire helped TRMNL →

Frequently asked questions

Answers to common questions people have about Terminalwire

How is Terminalwire different than SSH?

SSH was created in 1995 to secure, encrypted interactive remote shell sessions. It includes features not needed by modern command-line apps for web applications, such as file transfer, port forwarding, and public-key authentication. Today’s command-line applications for web apps need to do things SSH can’t, like open a web browser on the client to authenticate via the web application.

Terminalwire was built specifically to solve problems that modern command-line web apps demand that SSH can’t. It’s a WebSocket-based protocol that streams standard I/O, and other channels, between a web server and client. This allows you to use your preferred command-line parser within your favorite web server framework to deliver a delightful CLI experience to your users.

How is it licensed?

Free Terminalwire licenses are available personal use and commercial Terminalwire licenses are available for organizations depending on revenue, gross assets, and features. Detailed information on pricing, features, and requirements may be found on the licensing page.

Can I use Terminalwire with other web frameworks?

Yes! Terminalwire is designed to be integrated with any web framework and server that supports WebSockets.

How is Terminalwire different from a REST API?

Terminalwire is a WebSocket-based protocol that streams standard I/O, and other channels, between a web server and client. This allows you to use your preferred command-line parser within your favorite web server framework to deliver a delightful CLI experience to your users.

How does authentication & authorization work?

Terminalwire integrates with your existing web app’s authentication and authorization mechanisms. You can use the same authentication and authorization methods you use for your web app.

Do Terminalwire connections traverse through third-party servers?

No, Terminalwire clients connect directly to Terminalwire servers. The encrypted connection does not traverse through any third-party servers keeping your data between your server and users.

The Terminalwire client does connect to Terminalwire.com to check if the URL for the server is connecting to is licensed. This is done through a separate HTTPS connection that only provides the URL of the Terminalwire server end-point. This license check is then cached for 24 hours to prevent frequent checks. If the license server is unreachable or experiencing service issues and a license check can’t be performed, the client will still connect to the server.

Is Terminalwire encrypted?

Yup. Terminalwire uses the same TLS encryption as your web server and browser, which is WebSockets Secure (WSS) in a production web environment.

Still not sure? Let's talk! 🤗

Whether your team is building a new command-line app or simplifying existing infrastructure, I'd love to see how we can work together.

Discuss Your Requirements