Runless Documentation

Welcome to the Runless SaaS user manual. This guide explains how to onboard AWS connections, configure runtime automation, and manage team access in a multitenant control plane.

What is Runless?

Runless is a vendor-hosted runtime automation platform for non-production environments. It started with ECS and is expanding to other billable AWS resource types (RDS, EC2, Auto Scaling Groups, EKS, and more) using the same schedule-and-restore pattern. It helps you:

  • Reduce AWS costs by scheduling stop/start windows for idle resources
  • Centralize control across multiple linked AWS connections in one tenant workspace
  • Operate safely with role-based cross-account access and verification checks
  • Track savings through tenant-level dashboards and runtime history

Getting Started

Choose a topic to begin:

Core Concepts

  • Tenant: Your Runless workspace containing users, AWS connections, and schedules
  • AWS Connection: A linked AWS account verified through a cross-account role, with its own Quick Start stack version and per-resource-type permissions
  • Commercial Status: Subscription state used to gate full runtime operations
  • Resource Type: A category of billable AWS resource Runless can manage (for example ECS service, RDS instance). Each resource type is opt-in and requires its own IAM grant on the Quick Start stack
  • Resource Rule: A schedule (and, for resource types that need it, a restore configuration) that drives cost-saving automation for one managed resource. ECS today expresses this as a desired task count; other resource types will define their own restore configuration

Prerequisites

  • Customer AWS account with ECS clusters/services to optimize
  • Access to the Quick Start stack outputs in the customer account
  • Runless account (owner or member role)

Support

For questions or issues:

Version Information

This documentation targets the latest Runless SaaS release.