Core job 01 / Cloud parking

Your team clocks off.
Your bill shouldn't
work nights.

Non-production cloud runs roughly 168 hours a week and gets used for about 45 of them. CloudValet parks the rest: stop after hours, start before work, prove the saving.

168 h

Hours a week your dev environment can run

45 h

Hours a week your team is actually working

73 %

Of the week non-production sits unused

Illustrative arithmetic for a standard working week, not a measured customer result.

Inform. Optimize.
Operate. Repeat.

Cost work fails when it's a one-off cleanup. CloudValet turns it into a loop that runs every single night, with an owner and a number attached to each stage.

01

Inform

See the whole meter

We read every connected account and build a live inventory: what is running, who owns it, what it costs an hour, and how much of it is non-production.

  • Tagged and untagged resources
  • Cost per resource, per team
  • Idle hours already paid for
02

Optimize

Decide what should sleep

Utilisation over time tells us which resources are idle, which are oversized, and which are safe to park. Every recommendation carries a projected monthly saving.

  • Idle detection over 7 to 30 days
  • Rightsizing with projected savings
  • Parking schedules per team calendar
03

Operate

Make it a habit, not a project

Schedules run every night, exceptions are one click, and savings roll up into a report finance trusts. Waste stops coming back next quarter.

  • Nightly stop, morning start
  • Snooze and override with an audit trail
  • Monthly savings report by team

Stopping a resource is easy. Doing it safely, every night, is the product.

Schedules that match real life

Working hours, timezones, public holidays, sprint demos, and on-call windows. Park at 18:30, wake at 08:30, skip the days your team actually needs the environment.

A safe stop, in the right order

Resources stop in dependency order: app tier before database, workers before queues, so nothing wakes up broken.

Restart before anyone notices

Warm-up starts ahead of the first standup, with health checks before we mark the environment ready.

Rightsizing as well as parking

Some resources should shrink rather than stop. We recommend the smaller size, the saving, and the window to change it.

Override without a ticket

Anyone on the team can snooze parking for a resource for an hour or a night. Every override is logged with who and why.

Told, not surprised

Notifications land in Slack, Teams, or a webhook before a stop and after a failed action.

What the valet
does after dark.

You approve the plan once. After that it runs itself, and you read the outcome in the morning.

  1. 17:45Pre-stop notice posted to the team channel
  2. 18:00Dev app tier stopped, workers drained
  3. 18:04Sandbox databases stopped in dependency order
  4. 18:10Oversized staging cache flagged for rightsizing
  5. 07:55Environments warmed and health-checked
  6. 08:15Overnight saving posted to the daily digest

Pay for what
you park.

Free while you look at your own waste. Pro when you want the schedules running themselves. Enterprise when approvals and audit trails matter.

Free

$0

forever, up to 25 resources

Connect one cloud account read-only, see the waste, and read your IAM in plain English.

  • Idle and oversized resource discovery
  • Plain-English IAM policy summaries
  • Manual start / stop of parked resources
  • One connected cloud account
  • Weekly waste digest by email
Start free
Pro

$0.25

per managed resource / month

Automated parking schedules, rightsizing plans, and IAM change alerts for the whole team.

  • Unlimited parking schedules with calendar and holiday rules
  • Auto start before work, auto stop after hours
  • Rightsizing recommendations with projected savings
  • IAM change, unused-access and over-permission alerts
  • Slack, Teams and webhook notifications
  • Savings and access reporting for finance
  • Unlimited accounts across AWS, Azure and Google Cloud
Book a demo
Enterprise

Custom

annual, volume-based

For large estates, managed providers, and teams with audit and approval requirements.

  • SSO and role-based access with delegated teams
  • Approval workflows for parking and access changes
  • Least-privilege recommendations with audit history
  • Multi-tenant views for managed service providers
  • API access and custom policy guardrails
  • Named engineer and onboarding support
Talk to us

Pre-launch pricing. Nothing is charged today. Design partners help us set the final numbers, and checkout opens at launch.

Want to see what tonight would save you?

Book a demo