Reserver
Reserved Instances, managed properly.
What problem does it solve?
AWS Reserved Instances are tracked in spreadsheets and silently lapse when terms expire — reverting the fleet to expensive on-demand rates — while unused reservation capacity goes unnoticed.
Who is it for?
Teams running steady-state fleets on AWS, from startups with a handful of reservations to enterprises managing hundreds across multiple accounts.
Why are we building it?
Every AWS-heavy client eventually asks the same question: are we actually using our Reserved Instances, or are they sitting in a spreadsheet someone updated eight months ago? Almost always, some are already expired and quietly reverted to on-demand rates.
Reserver is what we're building to close that gap — connecting directly to AWS accounts, matching reservations to what's genuinely running, and turning "don't let this lapse" from a calendar reminder into an automated purchase.
How does it work?
- Match reservations to real usage
Reserver is designed to reconcile reservation records against what's actually running across EC2, RDS, and ElastiCache — not against a spreadsheet that's already drifted from reality.
- Coverage maps of reserved vs. on-demand
The plan is a visual map of what's covered by a reservation and what's paying on-demand rates unnecessarily, so the gap is visible instead of buried in a billing export.
- Break-even math on purchase recommendations
Every recommended purchase is meant to carry its own break-even point and projected annual saving, so the case for buying is a number, not a guess.
- Renewal autopilot
Expiring reservations are meant to be re-bought automatically before they lapse, rather than depending on someone noticing the expiry date in time.
What's the hard part?
Matching a reservation to the exact running instance it covers — across regions, instance families, and multiple AWS accounts under an Organization — is the genuinely hard reconciliation problem. AWS's own reservation-utilization reporting doesn't make this trivial, which is exactly why the spreadsheet-tracking failure mode is so common in the first place.
What does it do?
- Matches reservations to what's actually running — EC2, RDS, ElastiCache
- Coverage maps of reserved vs. on-demand capacity
- Purchase recommendations with break-even math and annual savings
- Renewal autopilot re-buys expiring reservations before they lapse
- Multi-account and AWS Organizations support
- Flat pricing — never takes a cut of your savings
What does this prove we can do for you?
Reconciling billing records against real infrastructure state and automating the fix is the same cost-observability and automation discipline we bring to a client's own cloud cost audit.
Where this shows up in client work
Questions, answered.
The questions we get asked most, answered plainly: no hedging, no marketing copy.
01 Is Reserver available yet?
Not yet — it's in build. Matching reservations to real running usage across accounts is the reconciliation problem we're solving first.
02 Does it only cover EC2?
The plan covers EC2, RDS, and ElastiCache reservations, with multi-account and AWS Organizations support.
03 How is pricing structured?
Flat pricing is the intent — Reserver is not designed to take a cut of whatever savings it finds.
Connects to your AWS accounts, matches Reserved Instances to running usage, and tells you exactly what to buy next — then makes the purchase a button, a schedule, or a rule.
This is the same discipline, real architecture decisions and an honest account of the hard part, that we bring to client engagements.