Does this affect production environments?
No. Runless is designed for non-production environments like development, staging and QA. We recommend keeping production environments in a separate account and always on.
How secure is Runless?
Security is our top priority. Runless assumes a dedicated cross-account role with least-privilege permissions and external ID protection. All actions are logged and traceable. Your long-lived AWS credentials never leave your account.
Can I override schedules manually?
Absolutely! Every ECS service or EC2 instance can be manually turned on or off at any time, regardless of the schedule, individually or in bulk for a cluster/region. This is perfect for emergency access, late-night deployments or unexpected work sessions.
What AWS permissions are required?
Runless requires access through the onboarding role to list and describe supported resources (ECS services and EC2 instances today), update their running state, and configure EventBridge forwarding for their runtime events. Access is split into per-service grants, so you can enable only the resource types you use. The Quick Start stack provisions the role policy and trust relationship.
How long does setup take?
Most teams are up and running in under 20 minutes. Launching Quick Start usually takes 10-15 minutes, and account linking plus verification in the Runless portal takes a few additional minutes.
How is commercial access validated?
After your AWS account is linked and role verification succeeds, Runless reconciles the account with licensing status. If access is pending or inactive, the account remains visible but restricted until commercial access is active.
How do team members get access?
Runless uses tenant-level team management. Owners can invite members, assign roles, and remove users directly from the dashboard without managing a separate Cognito user pool.
Is there a free trial?
Yes - through the Early Access Program. Our AWS Marketplace listing is currently in review, and until it goes live a limited number of design partner teams use Runless completely free. In exchange we ask for real usage on a dev or staging environment and occasional feedback. Apply at contact@cloudsoft.com.pl.
How do you calculate savings?
Savings are calculated from each resource's AWS pricing (CPU/memory for ECS services, instance type for EC2) and running time. The dashboard shows actual costs saved by tracking when resources are stopped versus when they would have been running.