Dormeto
ENFR
Menu

AWS · Application Load Balancer

Your idle web apps nap.
The first visitor wakes them.

Dormeto stops the workloads behind your Application Load Balancer when nobody uses them. It starts them again when a real visitor arrives. Awake, traffic goes straight to your application: Dormeto is out of the request path.

Get started How it works

Installs in your AWS account with Terraform. Never CloudFormation.

What it naps

EC2, Auto Scaling, ECS, EKS, RDS: asleep when idle.

  • Application Load BalancerALBits rules switch to the waker
  • Amazon EC2EC2instances stop
  • Amazon EC2 Auto ScalingAuto Scalinggroups scale to zero
  • Amazon ECSECSservices scale to zero
  • AWS FargateFargatetasks scale to zero
  • Amazon EKSEKSDeployments to zero
  • Amazon RDSRDSstops after its app
  • Amazon AuroraAurorastarts before its app
  • AWS LambdaLambdathe waker answers
  • TerraformTerraforminstalls the manager

How it works

Watch a fleet sleep through the night.

A router in each account and region watches your load balancer. It naps what nobody uses and wakes it on the first real request.

Request routing, awake and asleep Awake, the load balancer forwards requests to the application. Asleep, it forwards them to the Dormeto waker, which starts the application and redirects the visitor once it is ready. Visitor Load balancer Your app Waker
Awake: straight to the app Asleep: through the waker Simulation, not to scale. Click a sleeping app to wake it.
  1. 01

    Detect idle

    The router watches the request count of each workload on your load balancer. After an idle window (15 minutes by default), the workload is due for a nap.

  2. 02

    Nap

    The load balancer's rules switch to a small Lambda function, the waker, and the backends stop. A request during the switch cancels the nap, so nobody is caught half-way.

  3. 03

    Wake just in time

    The first real request starts the backends. The visitor is held while they start, then redirected as soon as the application answers. Or they see a page that reloads by itself. The rules then switch back to your app.

The manager

From discovery to the first nap.

The manager finds what could nap across your organization and onboards it in a click. It operates the routers for you, by AWS API calls through roles you control.

The overview: workloads awake, asleep, napping or failed, wakes and ignored requests over 7 days, and the routers with their health Discovery: the last run, the Organization access panel, and the candidates by status with their idle share A workload onboarded from the manager: asleep, its backend stopped, its two rules covered, and the drift the router repaired Routers: version, health, last idle check, workloads, an upgrade offered, pause and uninstall Operations: connections, router upgrades and an offboarding, each with its steps and status

Only real visitors wake it

Bots, crawlers, monitors and scanners get a waiting page, never a wake.

Noise control →

Runs in your account

The manager and the routers run in your AWS accounts, through least-privilege roles you create. Nothing is sent to Dormeto.

Security →

Terraform, never CloudFormation

The manager is a versioned Terraform module. It installs the routers itself, by API calls.

Get started →

Our test environment

Measured, not promised.

Figures from our test environment in eu-west-1 and eu-west-3. How each was measured.

to discover a synthetic organization
67 s1,002 accounts and 17,033 account-regions
to wake a workload
30–50 san EC2 instance, an Auto Scaling group or a Fargate service
requests through Dormeto
0once a workload is awake: traffic goes straight to it
workloads behind one router
1,500measured under ELB throttling, with bursts of wakes
asleepwaking upawake

FAQ

Questions

Short answers to what teams ask first.

Another question?Write to us, a person answers.contact@dormeto.com →
01Does Dormeto sit in front of my traffic?

Only while a workload is asleep or waking. Awake, the load balancer rule forwards every request to your application. The waker is not invoked at all.

02What do visitors see during a wake?

Their request is held for up to a minute. It is redirected to the same URL as soon as the application answers. If the wake takes longer, they get a waiting page that reloads by itself. API clients get a JSON answer with a retry delay.

03What still costs money while a workload naps?

Compute stops. The load balancer, storage (EBS volumes, database storage, warm pool volumes) and a few Lambda invocations keep running. What Dormeto itself costs to run is on the Scale page.

04How is it installed?

The manager is a Terraform module you apply in one account, from a versioned release. The other accounts get two roles, from a Terraform module, an AWS CLI script or a StackSet of yours. The manager then installs the routers itself, by API calls. No CloudFormation needed: Get started.

05Does anything leave my AWS account?

No. The manager, its data and the routers run in your accounts, and Dormeto receives nothing: Security.

06Which clouds are supported?

AWS, with Application Load Balancers. Other clouds are not supported today.

Let idle apps rest.

Install the manager in your AWS account with Terraform, or ask us anything.

Not sure it pays? Estimate your savings first, from your laptop, before installing anything.

Get started Talk to us