01
Park cloud waste
Turn it off when nobody needs it
Schedule non-production resources to stop at night and restart before work begins. Find idle and oversized infrastructure, then stop paying for capacity your team does not use.
Built by 2 ex-AWS engineers · booking demos
Sit back.
Relax.
We’ll mind the cloud.
CloudValet does two things, and does them well. We stop unused or oversized cloud resources from wasting money, and explain your team’s IAM permissions in plain English.
Pre-launch access. No payment details required.
Park idle cloudRight-size wasteExplain IAMWatch every changeAlert the right person
Your dev team does not work 24/7.
Neither should their cloud.
Nights, weekends and holidays are roughly two thirds of the week. Non-production infrastructure bills for all of it even when its not used.
See how parking worksThe arithmetic / One ordinary week
168 hours go in.
Only 45 get used.
Take a team working nine hours a day, Monday to Friday. Their non-production cloud can keep billing through every other hour unless a schedule tells it to stop.
Day
00:0006:0012:0018:0024:00
MON
TUE
WED
THU
FRI
SAT
SUN
Team working Available to park
Needed
45 h
Monday to Friday, 09:00 to 18:00
Quiet
123 h
Nights, weekends and the gaps between
Potential runtime reduction
73%
Before rightsizing adds anything else
Illustrative $10,000 month
$7,321
is the portion attached to those 123 quiet hours.
Keep running · $2,679Opportunity · $7,321
Illustrative arithmetic, not a promised saving. It assumes the same hourly runtime cost across the week. Storage, commitments, data transfer and resources that must stay online are not included.
Designed by 2 ex-AWS engineers, backed by our global team
We got sick of watching cloud money being used to buy mega yachts.
David · ex-AWSDuke · ex-AWS, ex-Microsoft, ex-Expedia
We met working on a giant AWS account. Both of us had spent years inside big tech watching bills from the provider side and the paying side. We had seen the same pattern everywhere: non-production environments running 24x7, load-test fleets left on for weeks, and IAM policies so nested that three engineers could read the same document and disagree on what it allowed.
We used ParkMyCloud. It did one thing well: turn non-production resources off when nobody was using them. Then Turbonomic bought it in 2019, IBM bought Turbonomic in 2021, and the simple scheduler we relied on got folded into a much bigger platform. The lightweight version never came back.
So we started building CloudValet: an independent tool in the same spirit. One tool, two jobs: park idle cloud resources, and explain who can access what. No sprawling suite. No enterprise theater.
CloudValet is not affiliated with, endorsed by, or sponsored by ParkMyCloud, Turbonomic or IBM. Those names are trademarks of their respective owners.
Engineers who shipped at real scale
We read pricing docs so you don’t have to
Start-stop schedules are our love language
Least privilege, not least effort
“Your engineers clock off at six. Your dev environment keeps the meter running 24x7...”
DUKE & DAVID ON GOOD WAYS TO KEEP JEFF BUYING NEW YACHTS
01 / Two jobs. Done well.
Park the waste.
Explain the access.
No sprawling suite and no wall of jargon. Just lower cloud waste and IAM your team can actually understand.
02
Make permissions clear
Know who can do what, and why
Read IAM permissions in plain English. See unused and over-permissioned accounts, understand policy changes, and get alerted when access drifts.
02 / How it works
Connect it once.
Let the valet tend.
You approve what stops and when. We keep watch over waste and permission changes, then tell you what matters without the jargon.
STEP 01
Connect
Link cloud accounts with scoped, read-only access first.
STEP 02
Understand
See what is wasting money and what every IAM permission really allows.
STEP 03
Relax
Approve parking schedules and receive clear alerts when access changes.
03 / One control surface
Different clouds.
One operating language.
Review resources, recommendations, and policy state with the same clear workflow across providers.
Unified resource inventory
Cross-account ownership
Consistent policy controls
Shared reporting for finance and engineering
Connects to
What we manage on each providerAWS estate
124 resources · 4 accounts
| Resource | Type | Signal | Action / value |
|---|---|---|---|
| dev-api-cluster | EC2 | Scheduled | 18:00 |
| analytics-sandbox | RDS | Review size | −42% |
| build-runner-03 | EC2 | Idle | 7 days |
Core job 02 / IAM clarity
Permissions,
without puzzles.
CloudValet audits your IAM setup continuously and translates complex policies into clear answers: who has access, what they can do, and what changed. The only thing we cant answer is why...
Clear enough to act on.
Get alerted to policy changes, unused access, and accounts with more permission than they need.
01
Who can do what
See effective access across people, roles, teams, and cloud accounts.
02
Plain-English policies
Translate dense IAM statements into direct descriptions your whole team can read.
03
Too much access
Flag unused permissions and accounts with broader access than their work requires.
04
Changes that matter
Alert the right people when permissions are added, removed, or unexpectedly widened.
04 / Built for the people on call
One platform.
Four boxes for clearer morning meetings.
Give every team the view and control they need, without creating four versions of the truth.
FinOps & finance
Turn cloud waste into an action list with ownership, forecastable schedules, and reporting everyone can read.
Platform teams
Apply the same operating rules across accounts while leaving teams room to move quickly.
Engineering leaders
See where idle environments, oversized services, and access risk are accumulating before the bill arrives.
Managed providers
Manage separate customer estates through consistent policies, delegated access, and shared proof of action.
Questions
The things people ask us first.
Anything missing? Ask us directly and one of us replies.
Ask a question- 01
- What does CloudValet actually do?
- Two things. It parks non-production cloud resources on a schedule so they stop billing when nobody is using them, and it reads your IAM permissions so you can see who can do what, in plain English.
- 02
- Which clouds do you support?
- AWS first, with Azure and Google Cloud following. If you run several accounts, subscriptions or projects, they roll up into one view.
- 03
- Will parking break my environments?
- Parking applies only to the resources you choose, on schedules you set, and any resource can be started on demand with one click. Production is excluded unless you deliberately include it.
- 04
- How much access do you need?
- You start read only. We inventory resources, costs and permissions without changing anything. Start and stop rights are a separate, narrower role you add when you are ready to let CloudValet act.
- 05
- How much can we expect to save?
- It depends on how much of your estate is non-production, so we will not put a number on your bill before we have seen it. Turning off a development environment outside working hours removes roughly two thirds of its running hours.
- 06
- Do you need our billing data?
- Read access to cost and usage reporting makes the savings numbers accurate. Without it CloudValet still parks resources, it just estimates prices from public rate cards.
05 / Design partner access
Sit back.
We’ll show you.
Book a focused walkthrough with the ex-FAANG engineers building CloudValet. We’ll show you resource parking and plain-English IAM monitoring for your cloud estate.
Resource parking walkthrough
IAM clarity walkthrough
No payment or commitment