How it works
From IAM role to reserved in an afternoon.
No agents, no sidecars, nothing deployed into your VPC. Reserver works entirely through AWS APIs, starting from a role you control and can revoke at any moment.
Step 01 — Connect
Grant a role that can look, not touch.
You create a cross-account IAM role from our template — Describe and List calls only. Reserver can read the shape of your fleet; it cannot start, stop, modify, or delete anything. Connect one account or a whole AWS Organization.
{
"Version": "2012-10-17",
"Statement": [{
"Effect": "Allow",
"Action": [
"ec2:DescribeRegions",
"ec2:DescribeInstances",
"ec2:DescribeReservedInstances",
"rds:DescribeDBInstances",
"rds:DescribeReservedDBInstances",
"elasticache:DescribeCacheClusters",
"elasticache:DescribeReservedCacheNodes",
"elasticache:ListTagsForResource",
"cloudwatch:GetMetricData"
],
"Resource": "*"
}]
}The entire read-only policy. Purchasing (Autopilot plan) uses a separate role scoped to the reservation purchase APIs — and nothing else. See the full security model →
Step 02 — Scan
Take inventory of the whole fleet.
Reserver walks your accounts and builds two lists. What's running: every RDS instance, ElastiCache cluster, and EC2 instance, with the dimensions that matter for matching — class, family, region, AZ, engine, platform, and how long it's been alive. And what you own: every reservation, its term, payment option, and expiry date. Scans re-run on a schedule, so the picture never goes stale.
- rds instances, clusters, Multi-AZ topology
- elasticache Redis & Memcached node fleets
- ec2 instances, platform & tenancy details
Step 03 — Match
Match every reservation. Find every gap.
Reservations are matched to running instances the way AWS billing actually applies them — service, class or family, region or AZ, engine, size flexibility included. What emerges is your true position: covered capacity, unreserved capacity burning the on-demand rate, reservations nothing is using, and terms about to expire.
- Covered — reservation matched to a live instance
- Gap — steady workload paying list price
- Idle — reservation owned, nothing using it
- Expiring — coverage about to lapse quietly
Step 04 — Act
Reserver forms an opinion. You set how far it runs.
Every gap becomes a concrete recommendation with the math shown: exact instance class, term, payment option, break-even date, and savings per year. On Watch, that arrives as a notification — email, Slack, or SMS — and buying is one click when you're ready. On Autopilot, you write the policy: renew expiring terms, buy on a schedule, reserve anything older than 90 days — with a human approval step wherever you want one.
- Notify — recommendation lands on your channel
- One click — you approve, Reserver purchases
- Rules — renewals, schedules, age thresholds
- Ledger — every purchase logged: who, what, why
Prefer to see it? Take the product tour →
Stop overpaying for a steady fleet.
Reserver is in early access. Join the list and we'll onboard you as capacity opens up — first recommendation within minutes of connecting.