Shell Commands in the Cloud

Run command-line tools and scripts from anywhere using SSH or HTTP.

Request Access

Your tools everywhere you go

Many command-line utilities can now be put in the cloud, configured just as you need, and run from anywhere using SSH with no installation.

Share scripts and automation

Empower your team with scripts and custom tooling that doesn't need to be set up. Just give access and others can run the command.

Integrate with your workflow

Running commands via HTTP and WebSocket open up new ways to integrate shell scripting and utilities into your internal systems.

Cmd.io is a specialized compute platform

It was made for running short lived, sometimes interactive programs made for the command-line. Programs are run in their own stateless, isolated execution environment in the cloud.

Programs are run as commands using SSH, HTTP, or WebSocket. They can be given environment variables, arguments, and STDIN. Then they stream back the output of STDOUT and STDERR. It's effectively a cloud API for POSIX tasks.

However, Cmd.io is not designed to run long-lived programs, programs that accept network connections, or programs that require interactive access to the user filesystem.

Enable teams without installs or credential sharing

Assemble and share commands that use open source utilities and scripted shell to perform tasks like deploying your web app. They can be run without installing a bunch of tools, making sure the local environment is set up correctly, or running in a local Docker or VM.

Credentials can be stored in the command environment, avoiding more complicated or insecure management of secrets. In many cases, credentials won't even be accessible by users of the command.

Use with git push to build developer workflows

SSH allows Cmd.io commands to be used as Git remotes to push to:

ssh://progrium@cmd.io/deploy-cmd/repository/path

Repository path patterns can be used to route different remotes to different commands. Maybe you have a deploy remote, but also a test remote that can orchestrate more complex testing of your source before pushing it to the main repository.

Build shell-based automation into apps and internal tools

With the HTTP API, you can "shell out" in your applications like using any other cloud API. Using the WebSocket API you can run shell scripts and commands and stream the output right in the browser.

Now tools that had to be run from the command-line can be turned into API endpoints. Did someone say lightweight CI platform?

Keep tools in the cloud, and off your machine

Not only can you put convenient utilities like jq on Cmd.io, but you can put ...larger... tools like latex up. Using latex locally can mean taking up to a 1GB of disk space and is often a mess to compile.

Cmd.io commands are built once, from packages or source, and are ready to use whenever you need them. Their environment configuration stays the same no matter what machine you run them from.

Most importantly, Cmd.io is a building block.

Cmd.io was intentionally built to do one thing and do it well.
It was designed to be composable with other systems.
Here are a few ideas to get you thinking creatively...

Cron
CI
Webhooks
WebSocket
Slack
IFTTT