Enter your current RDS configuration below. We'll model the savings PGFlare optimisation typically delivers — broken down by instance right-sizing, storage reclaim, and I/O reduction.
🔒 Estimates based on AWS eu-west-2 list pricing. No data sent to any server.PGFlare provides deepest analysis on PostgreSQL 16.9. Earlier versions are fully supported.
Doubles instance cost; adds ~$0.10/hr standby
Minimum 20 GB. Enter your current allocated storage.
Minimum 1,000 IOPS; minimum ratio 1:1 IOPS per GB.
How would you describe your current RDS performance situation?
Estimated annual savings after PGFlare optimisation
| Component | Current | After | Saving/mo |
|---|---|---|---|
| Instance | £0 | £0 | £0 |
| Storage | £0 | £0 | £0 |
| I/O (IOPS) | £0 | £0 | £0 |
| Total | £0 | £0 | £0 |
If active remediation is applied (Remediation+ session at £897), you can typically capture an additional 15–25% on top of diagnostic savings.
Pricing data: AWS RDS On-Demand pricing for EU (London) eu-west-2 region, PostgreSQL engine, converted from USD at £1 = $1.27. Prices are approximate and may differ from your reserved or spot pricing. Always verify against your AWS Cost Explorer.
Instance savings: Based on typical CPU reduction of 40–70% after query optimisation. Low health = 20–30% right-sizing; Medium = 35–50%; High = 50–65%. Most workloads can move down 1–2 instance sizes within the same family after eliminating sequential scans, missing indexes, and N+1 query patterns.
Storage savings: VACUUM + bloat reclaim typically frees 10–30% of allocated storage across medium-to-high inefficiency workloads. Low inefficiency assumes minimal bloat (5%).
IOPS savings: Index optimisation and query rewriting reduce random I/O by 30–60% in typical workloads. Only applicable when provisioned IOPS storage (io1/io2) is selected.
PGFlare investment: Diagnostic session £497 (1 day). Remediation+ session £897 (2 days). Emergency response £350/hr. ROI calculated as (annual saving − session cost) ÷ session cost × 100.