Category
Databases, ORMs, and the queries that get expensive.
Four providers meter four different things, and each one hides the pain somewhere else: a per-request I/O charge, a storage tier you cannot shrink, an HA checkbox that doubles the bill, a size you configured once and now pay for forever.
Postgres 14 stops getting fixes on 12 November, 19 arrives in September, and 18 is the version to land on. What actually changed in the storage layer, and how to tell in advance whether you will feel any of it.
Fivetran counts rows that changed and does not charge for the initial load. Estuary counts gigabytes and charges per connector instance in both directions. Airbyte stopped publishing its rate entirely. Five tools, five units, and the one that fits depends on how your biggest table churns.
Extended Support for RDS MySQL 8.0 started billing on 1 August 2026 at $0.10 per vCPU-hour, standbys included. RDS for MariaDB was never eligible, which makes 31 December a harder deadline than any invoice.
Formula correctness, messy-data cleaning, and what leaves your tenant. Which spreadsheet AI to reach for depends mostly on where your data already lives.
Mem0 bills add and retrieval requests, Zep bills credits, Letta bills active agents and seconds of tool execution, Cognee bills tokens ingested. All four are Apache-2.0, so the meter matters more than the feature list.
Picking a Postgres pooler is mostly picking a pooling mode and living with what it breaks. Five options, what each one is actually for, and the setting that stopped being a footgun.
The license fight that started the fork has quietly changed again. Here is where the three engines actually differ, and why a lot of Redis deployments are a cache, a queue, and a channel that Postgres already handles.
pgBackRest nearly lost its maintainer in April and is shipping again. The scare pointed at the two questions worth asking about any of these four tools: who keeps it alive, and who computes the incremental.
Four of these are not the same product, and the free tiers fail in four different ways. What each one actually charges for, and which shape of application each one fits.
The four warehouses have converged on features and not on billing units. Warehouse-seconds, bytes scanned, slot-hours, DBUs, and RPU-hours do not convert, and the minimum charge on a short query varies by a factor of sixty.
Three different products get sold under the same phrase, and the one that decides whether any of them works is a semantic model you probably have not written.
Prisma 7 dropped its Rust engine and Drizzle joined PlanetScale, which killed both of the easy reasons to pick a side. What is left is a question about how much SQL you want to write.
Nobody picks a vector store on unfiltered QPS, because nobody runs unfiltered queries. What separates these four is what happens when you add a tenant filter, and which version you are pinned to.