Stop paying for a full copy to serve your hot reads
A read replica copies your whole database. PgCache stores only the data your queries read and keeps it fresh with logical replication. Your app changes one connection string.
Read replicas weren’t built for read offloading
Scaling reads shouldn’t mean paying to copy your entire database.
You pay to replicate cold data
Most traffic hits ~20% of your data, but an RDS or self-managed replica keeps a full copy of all of it, including rows nobody reads.
Read replicas are all-or-nothing
RDS replicas and Aurora readers serve the whole database, so you can’t scale only the hot tables. Each one you add is another full instance.
Aurora IO billing punishes read scaling
On Aurora Standard, reads that miss memory are billed IO, and new readers start cold. IO-Optimized drops the IO fee, but instances cost ~30% more.
Bolting on a cache means rewriting your app
A Redis layer adds invalidation logic, a new system to run, and stale-data bugs: work the database team didn’t want to own.
Estimate your savings
See what you stop paying when you offload reads to PgCache instead of running a full replica.
Swap a $500/mo replica for m6g.large at $156/mo all-in, about $344/mo saved.
PgCache copies only the hot working set, not your whole database.
Check your workloadPrefer to buy through AWS? AWS Marketplace listing
All-in estimate: PgCache hourly rate + EC2 on-demand (us-east-1, Linux), ~730 hrs/mo. Excludes EBS storage. Rough estimate for discussion; actual savings depend on your workload.
See what your own workload would save
Step 1
Check your workload
Paste a pg_stat_statements export or a Postgres log. In about a minute you see which of your queries PgCache would serve from cache.
No export handy? See a sample report
Runs in your browser. Nothing is uploaded.
Step 2
Get a free workload review
30 minutes with the founders, by video or email. Bring your Fit report or your Postgres problem.
- What PgCache would serve and save on your workload
- If it fits, a pilot with hands-on help
Prefer email? [email protected]
Already curious? Request a pilot
Free. Pick any open time on our calendar.
Run it yourself: Source on GitHub · Try it in one command
Not ready yet? Get updates by email.