Features

You must provide all the configurations of a given type when creating a Connection

📄️ Create Users

You can add other people to your Runops organization or let them register themselves.

📄️ Manage Users

Update a users' status and groups from the portal and CLI.

📄️ Request Access

Users from an organization can request access to Runops from Slack, Portal, and CLI. In all cases, an operator has to approve the new user before they receive access. Runops sends a Slack message with the user information for approval to the operators.

📄️ Access Control

Groups

📄️ Webhooks

Configure and receive events for actions users are taking.

📄️ Runops Proxy

Runops proxy allows forwarding remote TCP services locally.

📄️ GDPR

Runops helps you adhere to GDPR. The automatic redacting of any Personally Identifiable Information (PII) data from human data access drastically reduces the risks of a leak while keeping your existing workflows in place.

📄️ Untitled

📄️ Architecture

The Runops agent is a small, reliable, and cross-platform task runner, making it easy to run tasks on your infrastructure. Its primary responsibilities are polling Runops for work, running tasks, and reporting the task's status code and output log.

📄️ AWS Secrets Manager

Single-command setup:

📄️ Collaborative Automation

A powerful workflow for Templates is having a central Git repository with scripts certified by stakeholders of a Connection.

📄️ Command-line

You can use Runops to manage access to any service that has a CLI client. Such services include Kubernetes, AWS, GCP, app consoles like Rails Console, Elixir IEx, and others.

📄️ Directory Service Integration

Sync users from your Directory Services into Runops.

📄️ Enhanced Agent Security

The agent is a system that has higher privileges in a private infrastructure, the created tasks are processed and executed through an authentication that maps an api key of an organization, however there's no way to guarantee that task is being executed by an authenticated and authorized user session. This requirement may be important to organizations in which requires this sort of enforcement.

📄️ Execution Reviews

We define review workflows on Connections, and reviews happen in Slack or the web application. Connections have 3 review modes:

📄️ Github Integration

Ignoring files

📄️ Hashicorp Vault

Manage your secrets in Hashicorp Vault.

📄️ Kill Tasks

If the command is taking to long, it's possible to kill an existent task in a running state. However, it is not guaranteed that it will succeed.

📄️ Link Automations to Connections

Extra configurations

📄️ Manage Credentials

You can execute these steps from the command-line and the web application//use.runops.io

📄️ Multiple Self-Hosted Agents

This is done via TAGS.

📄️ PCI DSS

Runops doesn't access card data. Runops-managed components are out of the PCI scope. The only component that may access card data is the Runops agent that runs inside your infrastructure. It's an open-source application that you can apply the same controls you have for your internal PCI-scoped applications.

📄️ Web Portal

📄️ Re-Use Secrets

It's possible to map custom keys from your secret manager:

📄️ Rich Automation Inputs

We have a way to create validations for each parameter and this will provide security for your template at the form level.

📄️ Runtime Information

Runops exposes metadata information in which could be retrieved in the runtime of the task as environment variables:

📄️ Export Session Recordings to S3

You can configure your own S3 bucket to store the redacted logs after task execution.

📄️ Secrets Management

The Runops agent pulls credentials from the Secrets Manager of your choice, all within your infrastructure. Secrets never leave your infrastructure.

📄️ Security

The primary design constraint for Runops is to make sure your sensitive data never leaves your infrastructure. Credentials stay in your Secrets Management tool. Access results are redacted before they get sent to users.

📄️ Self-hosting

Self-hosted agents enable you to deploy Runops agents inside your infrastructure. There are two main reasons why you may want to use them:

📄️ Session Recording

Auditing Proxy Connections

📄️ Run Automations from Slack

To run automations from Slack, run /runops templates anywhere in your Slack workspace:

📄️ slack-workflows

📄️ SOC2

Runops has all the SOC2 Type 1 and Type 2 systems requirements. We are working on the policies and should be ready for the audit soon.

📄️ Templates Access Control

You can assign certain templates to specific users and other templates to different users.

📄️ Automation (Templates)

Define and share common Tasks with your team.