SnoozeOps automatically sleeps and wakes non‑production VMs and databases on a schedule — cutting 35–65% of idle cloud spend without a single long‑lived credential stored in the database.

$ snoozeops status --org=acme

02:00 checkout-service RUNNING → SNOOZING

02:00 payments-staging-db RUNNING → SNOOZING

06:45 ci-preview-a1b2 LEASED (2h) — skip, deploy in progress

08:00 checkout-service SNOOZING → WAKING

08:00 payments-staging-db SNOOZING → WAKING

est. saved this week — $4,218.00

█

35–65%

avg. non‑prod spend cut

0

static credentials stored

<10 min

to connect via Terraform

24/7

lease‑aware automation

how it works

01

Run the open Terraform module to stand up a Workload Identity Pool and a least‑privilege role. Paste the Principal back in — no access keys change hands.

$ terraform apply

02

Background workers sync every non‑prod VM, Cloud SQL/RDS instance, and App Engine/Beanstalk env across AWS and GCP within minutes.

142 resources found

03

Bundle dependent resources into a Service Group, then attach a Schedule with ordered Wake‑Up Groups — databases first, app servers last.

checkout‑service · 3 groups

04

Celery triggers idempotent stop/start calls on your cron. Active CI/CD leases hold a resource awake until a deploy finishes — nothing sleeps mid‑pipeline.

POST /service-groups/{slug}/sleep

the product

Estimated monthly savings, total managed resources, and active schedules at a glance — plus a live feed of the last ten wake/sleep events, so nobody has to ask "did the job actually run?"

One curl call from your deploy pipeline wakes or sleeps an entire dependency stack — RDS, EC2, cache, all at once.

Sequential startup ordering with health‑check delays between tiers, so the app servers never boot before the database is ready.

Keep a resource alive for 1h, 4h, or a custom window — or force sleep/wake instantly, with graceful pre‑stop hooks for stateful apps.

Every automated or manual state change, filterable and exportable to CSV for your next compliance review.

security & trust

SnoozeOps authenticates through Workload Identity Federation — a short‑lived, cryptographically‑verified trust relationship between your cloud account and ours. No IAM access keys, no secrets rotation, nothing to leak.

module "snoozeops_wif" { source = "snoozeops/wif/gcp" version = "~> 1.0" project_id = "acme-nonprod" allowed_actions = ["compute.instances.stop", "compute.instances.start"] } # no keys. no service account json. no secrets.

pricing

$19.90/monthly

For a single team getting non‑prod costs under control.

$99.90/monthly

For teams running Service Groups across multiple environments.