Terminalwire

Build command-line interfaces for web apps

Ship terminal applications 10× faster using your favorite web framework

Get Started

A dramatically easier way to build terminal apps 🧘


Terminalwire streams command-line applications over WebSockets from your web server to a thin client installed on peoples’ terminals.

That means developers don’t have to worry about building web APIs and instead can focus on building delightful command-line user experiences.

Achieve 10× more for ⅒ the effort 💪


Solo developers and teams create and maintain command-line apps without the burden of building APIs, managing versioning, packaging binaries, or handling incompatible outdated clients.

New features are deployed instantly to the server, just like a web app. No client-side updates necessary. No breaking changes. Deployments can happen frequently, even on Fridays.

Works with your favorite web framework & language

Drop Terminalwire into existing web apps and ship a command-line interface in minutes

Developers are no longer limited to “what runs best on the client”–they are free to use their favorite command-line library in their language of choice.

Ready to dive in? Crack open the manual for your favorite web framework and have a terminal running in minutes.

Don't see your framework? Want support for your app sooner? Reach out, discuss your requirements, and we'll get you up and running.

Frequently asked questions

Answers to common questions people have about Terminalwire

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 can I get early access to Terminalwire?

I’m working with select customers in private beta to ensure that Terminalwire meets their needs and integrating it into my own production web applications. I expect to release Terminalwire to the public in the coming months. If you’d like to integrate Terminalwire into your stack today, email brad@terminalwire.com and let’s talk about your requirements.

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 terminal 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.

Authentication & Authorization

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.

How is Terminalwire different from a REST API?

Terminalwire is a WebSocket-based protocol that streams terminal 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.

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.

How will it be licensed?

Terminalwire will be available under a dual license. One license will be freely available for personal use. Commercial licenses will also be available for organizations.

Sound good? 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