Debian 11 Dies on 31 August, and It Is Hiding in Your Base Images
The people this deadline catches are not Debian admins. They run python:3.9-slim and have never once thought about what is underneath it. Nine days to find out.
Category
Where the code runs, and what it costs to keep it there.
The people this deadline catches are not Debian admins. They run python:3.9-slim and have never once thought about what is underneath it. Nine days to find out.
Algolia counts requests and records, Typesense counts RAM-hours, Meilisearch will count either, and Elastic switched to VCU-hours. Off the published rates, a $129.60 Typesense box equals Algolia at 269,000 searches a month.
From 1 October, EWSEnabled=True with an empty allow list blocks every EWS call in the tenant, and Null is the value that keeps EWS running. The end-of-August date is not a registration with Microsoft, and the kiosk block quietly moved to October.
Support ended 14 July 2026, the same day as SQL Server 2016. SQL Server sells you three more years by the core-hour. SharePoint sells you nothing, and Subscription Edition is not staying put: it is a new farm, a database attach, and a license that exists only while Software Assurance does.
Updates to Oracle JDK 21 released after September 2026 move to the paid license, and Oracle ships JDK updates quarterly. The next quarterly update is 20 October 2026. Same bytecode from Temurin or Corretto gets patched for three to five more years, free.
The endpoint returns 410 Gone with a body that calls it a temporary brownout. Trust the status code. Then work out what you actually lost, because the thing you are replacing cost zero and every replacement does not.
Tailscale charges per seat, ZeroTier per device, NetBird per active user against a machine allowance, Twingate per person who can request access. The cheapest one flips as your infrastructure grows, and nothing about the products changes.
Five providers, three volumes, list prices read off the vendors' own price files. The gap between the cheapest and the most expensive at 50 TB is 18x, and almost none of it comes from the per-GB number.
Launchpad marks 25.10 Obsolete, but the repositories are still on archive.ubuntu.com, frozen since July. So apt update succeeds, unattended-upgrades logs a clean run, and nothing on the machine tells you patches stopped.
The category split into three different jobs, and each tool bills for a different thing. Which one is cheapest depends entirely on the shape of your team and your traffic.
9.3 went out on 24 July 2026 and 9.4 follows on 16 December, so the stepping-stone plan is gone. Splunk sells 24 months from a minor's release date, which makes the version you pick a purchase of months. The walls are the CPU, the certificates, and the forwarders.
Security support for containerd 1.7 stops on 1 September 2026. Go to 2.3 rather than 2.0, convert your registry config before you touch the binary, and let the 1.7 deprecation warnings write your checklist.
One of these four has shipped nothing in fourteen months. Another closed multi-region monitoring as not planned. A third dropped its Cloudflare requirement and is now a docker compose file. The comparison tables have not caught up.
Support ended 14 July 2026 and Extended Security Updates run to 17 July 2029. The escalating 75/150/300 percent table everyone quotes is not what the Azure meter charges, and waiting to subscribe does not save you a dollar.
Amazon SES is the $0.10 per thousand everyone quotes. From 21 July 2026, new accounts start on a plan that charges $0.16, and the cheap number is something you opt into. Meanwhile the break-even against a managed provider is roughly ten times higher than the usual advice says.
Run the two rate cards against each other and Lambda costs 2.15 times Fargate for the same CPU and memory, so it stays cheaper until the function is busy nearly half the time. Lambda Managed Instances lands within 1% of Fargate, which is not where the announcement pointed.
One bills agent-seconds, one bills AI credits at roughly 6.5 per investigation, two bill seats, and one will not tell you. The word agent got stretched across five product shapes, and the meter is the fastest way to work out which one you are looking at.
AL2 stopped getting security updates on 30 June 2026. The upgrade is not a version bump, it is a different distribution, and these are the specific pieces that break.
How to read the lock block before you break it, when to clear a DynamoDB record by hand, and the migration to S3-native locking that has one combination which locks nothing and warns about nothing.
Per-GPU hourly rates off the vendor pages, and the thing the rate sheet gives away: the cheap-to-expensive order is not the same on Blackwell as it is on Hopper.
You are already on the enhanced Free tier, and the question is what happens at 500 resources. The alternatives repriced hard since March, and one of them now starts at $20,000 a year.
Nothing bricked in June, because UEFI checks whether a certificate is in the database, not whether it is still valid. What expiry actually took away is the ability to sign, and the Windows boot manager is the last one holding.
The kubelet stopped starting on cgroup v1 in 1.35, and one line of config still turns that off. The code is not gone, no removal release has been named, and the deadline that actually costs you money is somewhere else.
They have converged on the same loop, so the choice is about the shape of orchestration you want and whether the project is still where its vendor invests. One popular answer has already been superseded.
Datadog bills per host, Grafana and SigNoz bill per GB, Sentry bills per event. Running it yourself replaces all three with storage and your own time, and the license fine print decides whether you can.
The repository was archived on 23 March 2026 with a CVE published the same day as its final release. Seven landed in the ten weeks before that, all the same shape, and that shape is exactly what makes the migration hard.
Savings Plans, Reserved Instances, and Spot all advertise a percentage. The number that decides your bill is the list of things the discount never touches, and both AWS and Azure moved that line this year.
137 is 128 plus SIGKILL, and raising the memory limit is the right fix for exactly one of the four things that send it. Two commands tell you which one you have.
Kong's open source gateway stopped at 3.9 while Enterprise shipped 3.15, and Konnect charges ten times what Apigee does per million requests. Both facts reorder the shortlist.
Store a terabyte, serve five, and S3 bills $464 while R2 bills $15. The egress line is the whole comparison, and two of the cheap options have fine print that undoes it.
These protocols are not competing for the same job. Authorization, checkout, and settlement are three different layers, and knowing which one you are shopping for settles most of the argument.
Four different products wear the same label. Which one you need depends on whether you want URLs, passages, or clean text, and the bill is decided by how many pages you fetch, not how many searches you run.
Three replicas on EBS plus cross-AZ traffic is where a Kafka bill actually goes, and at AWS list rates that line is sixteen times what the same data costs on S3. Diskless is now everyone's answer, including Kafka's.
Voice finally works because the pipeline collapsed. What each platform actually charges per minute once the model passthrough is counted, and the three things that decide whether your agent feels broken.
Stripe now sells the merchant of record product it also owns a competitor to. Verified rates for six options, and the revenue level where paying the surcharge starts making sense.
Two of the three dates are fixed and public. The one that catches teams is the 120-day window that starts the day you migrate, and it only applies if you take Atlassian's own exit.
Cost Explorer says EC2 went up. Every tool in this category exists to answer the next question, and they answer it at four different layers, against numbers that are not always what you paid.
AWS bills your agents by the vCPU second. Microsoft and Google bill by the person. That single difference decides more about your bill than any model choice.
Inngest, Temporal and now Lambda all bill per step, and a five-step run costs six of whatever they count. Trigger.dev bills compute-seconds instead. Same workload, four rate cards, and one of them cannot be filled in from public prices.
What a small always-on app actually costs on each, and the specific line item on each platform that turns a $10 bill into a $200 one.
Custom silicon against GPU platforms, and the question that settles it: what is your user doing while the tokens stream? Speed is worth paying for in exactly two of the four common workloads.
At half an hour of work a day, all three container meters land within seven cents of each other. What separates them is whatever has to stay awake to receive the request: $5 for a Worker, cents for a stopped Fly machine, $16.43 a month for a load balancer before the container starts.
Five gateways took most of the production traffic this year. Routing, cost, and governance compared, plus the honest ops bill behind the cheap option.
Twelve engineers and forty CI identities run about $252 a month on one of these and about $5,800 on another. The unit printed on the invoice is most of the comparison. The rest is which directory the audit log lives in.
Cloudflare bills CPU time, Lambda bills wall-clock, and Vercel splits the difference by pausing CPU billing during I/O while memory keeps running. At 100M requests the cheapest and the most expensive swap places depending on whether your function waits or computes.
Docker Desktop's license threshold is the reason most teams start looking. Here is what the three usual replacements actually cost you in compatibility, security posture, and money.
Hosted runners got cheaper in January and the per-job rounding rule still quietly costs you more than any of it. And before you price a move to GitLab, CircleCI, or Buildkite: none of the four bill the same unit.
Kubernetes is extraordinary engineering and wildly overbuilt for most teams under fifteen engineers. Five things that are genuinely production-grade and stop one rung earlier.
Both bill by the second, both look cheap, and neither price is the whole bill. The agent-second rate covers the agent; the observability calls it makes to do its job are billed at their own rates, and the support credits that offset the first do not touch the second.
These three get compared as if they do the same job. They don't, and the architecture diagram explains every difference in price, latency, and who can read your traffic.
Picking a Gemma 4 size for the hardware you already own, getting it running under Ollama, and wiring native function calling into a small agent loop.
The BUSL has an expiry date printed in it, four years per version, and IBM is the licensor. The split that actually changes what you can build is which registry your source address resolves to, and 3,198 provider names sit on only one side of it.