One team saved $42,983 in 141 days

Your dev servers run 24/7.
Your team uses them 8h a day.

Idlefy flips the default: servers stay off. Your team starts one for exactly as long as they need — from Slack, Telegram, or Web — and it shuts itself down when the timer runs out. No algorithm guessing. Up to 67% off your cloud bill.

+$100 in credits after upgrading to Pro

No credit card required · Free plan available

Quick pick 17 servers · $0.46/hr
Servers 17
Price per hour $0.46
$ $ $ work wasted
Without Idlefy
With Idlefy
0:00 — 8:00 — 24:00
Now
$5,692
With Idlefy
$1,897
Est. savings
$3,795
Save up to 67% — Start Free

How does Idlefy work?

Not an idle detector. A different default.

Idlefy is a cloud cost platform built on one rule: development servers stay stopped unless someone actually needs them. Instead of hunting for idle machines after the money is spent, it flips the default — a VM is off until an engineer takes a lease on it. You pick a machine in Slack, Telegram, or the web dashboard, choose how long you need it, and it starts in about a minute. When the lease expires, the server shuts itself down.

Need more time? Extend from the same chat. Idlefy warns you before the timer runs out — and if you're still mid-task at expiry, on Pro the Safety System grants one 30-minute grace period before the force-stop. The timer is always set by a person — Idlefy never decides on its own that a server looks idle. Persistent disks survive every stop, and Idlefy only controls servers you explicitly tag — on AWS that boundary is enforced by the IAM policy itself.

Full walkthrough: how Idlefy works

One day of vm-gpu-01 UTC
vm-gpu-01 4h Start ▸ from Slack, Telegram, or Web
00:0006:0012:0018:0024:00
09:00lease started— @anna, 4h via Slack
12:40warning sent— 20 min left, extend?
13:00auto-stop— lease expired, disks kept
13:01billing: 4h compute billed, 20h stopped
  1. 1

    Tag the VMs you hand over

    Dev boxes, staging, GPU rigs. Untagged machines stay read-only — never started, never stopped. On AWS the IAM policy itself enforces it.

  2. 2

    They sleep by default

    A managed VM's resting state is stopped. Nobody pays for an idle Friday night again.

  3. 3

    Lease when you need it

    A tap in Slack, a message in Telegram — or one click on the web — starts the machine for the hours you choose. Extend anytime.

  4. 4

    It shuts itself down

    At expiry the VM stops on its own — still working? On Pro the Safety System grants one 30-minute grace first. Persistent disks stay.

Dev Boxes: a dev machine that stays off until you need it

Idlefy creates it in your own AWS account. Lease it and it starts; when the lease ends, it stops itself.

No machine yet? Idlefy builds one for you. Pick a size, an operating system and your SSH keys. Idlefy sets up the subnet and the security group, creates the machine stopped, and puts it on the same lease timer as every other server it manages.

Ready-made sizes for solo work, team work and GPU, or any machine type your organization allows. Ubuntu, Debian or Amazon Linux — with the NVIDIA driver already installed for GPU boxes. A short project? Set a lifetime and the box deletes itself when it is done.

dev-box · anna-api your AWS account
Ubuntu 24.04 2 vCPU / 8 GiB 50 GiB SSH: my IP only
08:58created— stopped until you lease it
09:00lease 4h— starting
09:01running— SSH command ready
13:00stopped— lease over, disk kept
$ ssh ubuntu@203.0.113.24

Four steps, no AWS console

Where and how big, the details, who can reach it, review. By default SSH is open only from your own IP address.

Your account, your bill

The machine lives in your AWS account and AWS bills you directly. While it is stopped, you pay only for its disk.

A bigger machine for a day

Change the type of a stopped box in seconds and see the hourly difference first. The disk stays as it is.

No access inside

Idlefy never logs in to the machine. Only your public SSH keys go onto it, and Idlefy manages only the resources it created.

AWS only for now. On Pro, create and lease a dev box from Claude Code or Cursor through the Idlefy MCP server.

See the burn in minutes

A free idle audit shows what 24/7 servers really cost you — before you change anything.

1. Connect, read-safe

One cloud connection. Idlefy sees all instances but can control only the ones you tag — on AWS that's verifiable in the IAM policy, not a promise.

2. Scan 30 days

A month of usage history, analyzed read-only from data your cloud already stores. Nothing to install — and the audit never touches a running machine.

3. See the burn

Every idle hour, priced. Per instance, per hour of the week. Then put the worst offenders on the lease schedule.

The audit finds the waste. Shutdown stays on the lease timer your team sets — never on a guess.

For the people who start servers — and the people who pay for them

For engineers

  • Start a VM straight from Slack or Telegram — no tickets, no consoles.
  • Extend or release from the same app when plans change.
  • Your workflow stays yours: SSH, IDE, CI — the machine is simply on when you need it.
  • You decide what Idlefy can touch. The tag is the boundary, and you set the tag.

For engineering leaders

  • A bill that tracks usage, not calendar time — leased hours are the only running hours.
  • The free Idle Audit prices every wasted hour before you commit to anything.
  • Full audit trail: who started what, when, and for how long.
  • Budgets and roles per team, so savings survive the next quarter too.
Teams typically waste $2,000–5,000/mo on idle servers. Idlefy starts at $50/mo — up to a 95× return.
Billed 24/7, used 8h
"I'll turn it off later"
"Is anyone using staging-3?"
A bill nobody can explain

Real results — 17 servers, 141 days of data

$42,983 saved
82% cost reduction
1,048 rentals
Recommended by E-chat.tech

Native Integrations for Slack, Telegram & macOS

Seamless integration with your existing tools

Telegram Bot

Full VM management from your favorite messenger

🤖 Idlefy Bot

Your VM data-server lease expires in 20 min

Slack App

App Home dashboard with one-click actions

ID
Idlefy APP

Active rentals: 3

This month saved: $240

macOS Widget

Native desktop widget for instant VM access

Development-API
t3.large • us-east-1
Running
Lease ends in:
03:12:45

How Idlefy protects your cloud account

Least-privilege access

We don't ask for admin rights. Only the narrow, tag-scoped permissions the product actually needs.

Keyless cloud federation

OIDC (Web Identity Federation) on AWS, Workload Identity Federation on GCP — keyless on both, automatic token rotation, no access keys to manage.

Sign in with your own identity provider

On Pro, connect Okta, Auth0, or another compatible OIDC provider and keep joiners and leavers where they already live. Domains are proven by DNS before they grant anything, and SSO can be made mandatory. How it works.

IAM Policy Example Safe
{
  "Sid": "IdlefyVMManagement",
  "Effect": "Allow",
  "Action": [
    "ec2:StartInstances",
    "ec2:StopInstances",
    "ec2:RebootInstances"
  ],
  "Resource": "*",
  "Condition": {
    "StringEquals": {
      "ec2:ResourceTag/idlefy": "enabled"
    }
  }
}

Simple, Transparent Pricing

Start saving immediately. Upgrade only when you grow.

Pay a fixed fee Save up to 67% Cancel anytime

Free

$0 /mo

For Sandbox & Personal Use.

  • 1 VM
  • Up to 5 users
  • Max 24h sessions
  • Web interface only
Most Popular

Basic

$50 /mo

For Growing Dev Teams.

  • 5 VMs, 5 Workflows (expandable)
  • ChatOps — Slack & Telegram
  • Custom durations up to 48h
  • RBAC & team roles
AI-powered

Pro

$100 /mo

For Scale & Security.

  • Everything in Basic, plus:
  • Safety System & Idle Detection
  • SSO — Okta, Auth0, and OIDC
  • Budgets with blocking, per team and per person
  • Sessions up to 72h
+$100 bonus credits after upgrade
Choose Pro Compare features

Do the math yourself

Free calculators and real instance prices — no signup, no email gate.

Latest from the blog

Notes on cloud cost, FinOps, and dev infra.