On 1 October 2026 Render announced lower prices for its Key Value service — its managed Redis-compatible store. The post is short and specific: "Starting October 1, 2026, all Key Value plans 1GB or higher will cost 20-45% less." Two plan sizes were added at the same time, 3GB and 50GB, "to fill the gaps between our existing plans", and existing paid services got the new pricing automatically.
That is a good change for Render customers, and the scope matters: the cut applies to plans of 1GB or higher. Plans below that are not mentioned, so they are not covered by the sentence. The percentage is Render's own figure, and the post carries no dollar amounts, so neither does this one.
The reason it is worth writing about from here is not the number. It is that the number exists at all.
A price cut on a line item you don't have
On Render, Key Value is a service you add and pay for separately from the web service that uses it. That is a perfectly reasonable way to build a platform: each component is its own product with its own plan ladder, and a price cut on one of them is news because it moves one line of your bill.
On DeployBase there is no such line. Our pricing page lists "Unlimited Databases" and "MySQL, PostgreSQL, Redis & MongoDB" on all four plans, from the Starter plan up; those are the page's own words, and what they describe in practice is that a Redis instance is a container you add to your account from the dashboard, and it runs inside the RAM and CPU you already pay for. There is no Redis plan to pick, no Redis invoice, and therefore no Redis price to cut. A 20-45% reduction on a separately-billed cache is, for a DeployBase customer, a reduction on nothing.
That is not a boast, and it is not a claim that one model is cheaper than the other. We did not read Render's pricing page for this piece and we are not going to compare totals we have not checked. It is a structural observation: the two bills are shaped differently, and a change on one axis of one of them does not translate to the other.
What "included" actually means, and what it costs you
"Included" is not "free of consequences". A Redis container on DeployBase draws from the same resource slice as your app: the Starter plan's 1 GB of RAM is shared between your application process, any long-running processes inside your app container, your scheduled cron jobs, and every database container you add. Give Redis a generous memory ceiling on a small plan and your app will feel it. The trade is explicit: you are not paying for Redis as a product, you are spending part of a fixed budget on it, and sizing that budget is your decision rather than a line on an invoice.
The separately-billed model has the opposite trade. Render's post is a reminder that it comes with a price ladder you can climb independently of your web service — a 50GB Key Value plan is now a thing you can buy without changing anything else — which is exactly what you want when the cache is the thing that needs to grow. A single fixed slice cannot offer that without moving the whole account to a bigger plan.
So the honest summary is: Render made an add-on cheaper; on DeployBase it was never an add-on. Which of those you want depends on whether your cache grows on its own schedule or in step with your app.
How to read a competitor's price cut when you host elsewhere
A few rules we try to hold ourselves to, written down because this announcement is a clean example of each.
- Find the line item first. Before asking "is this cheaper than what I pay", ask "which line of my bill is this comparable to". Sometimes the answer is none, and then the comparison is not a comparison.
- Keep the vendor's scope. "All Key Value plans 1GB or higher" is not "all Key Value plans". Announcements are precise about what they cover; summaries tend to round that off.
- Percentages without a base are not prices. 20-45% less than a figure you have not looked up tells you the direction, not the amount. The amount is on their pricing page, and that is where to read it.
- Separate the component from the hosting bill. Memory, storage and compute prices across the industry move for their own reasons; a managed cache getting cheaper at one vendor says something about that vendor's cost structure for that product, not about hosting in general.
If you run Redis on Render, the 1 October change is simply good news and needs no action. If you run it on DeployBase, nothing about your bill changed on 1 October — and the thing to check is not a price but a number in your dashboard: how much of your plan's memory the cache is actually using.