These Raspberry Pi price hikes are no joke
As of today, the price of the 16GB version of the Raspberry Pi 5 is going up by $100, a price bump that's almost as much as the original $120 price tag. Driven by the ongoing RAM shortage, Raspberry Pi is raising prices on over a dozen of its bare-bones computers, after previous increases in […]
Stevie Bonifield
is a news writer covering all things consumer tech. Stevie started out at Laptop Mag writing news and reviews on hardware, gaming, and AI.
As of today, the price of the 16GB version of the Raspberry Pi 5 is going up by $100, a price bump that’s almost as much as the original $120 price tag. Driven by the ongoing RAM shortage, Raspberry Pi is raising prices on over a dozen of its bare-bones computers, after previous increases in December and February. The increases range from $11.25 to $150.
In a blog post announcing the price increases, Raspberry Pi CEO Eben Upton reiterated that they won’t be permanent, stating, “The circumstances in which we find ourselves are challenging, but in the future they will abate. When they do, we will reverse our price increases, and until they do, we will continue to work hard to limit their impact in every way we can.”
To potentially soften the blow of the price hikes, Raspberry Pi also announced a new version of the Raspberry Pi 4 with 3GB of RAM available starting today, priced at $83.75. Raspberry Pi models with 4GB or more of memory have been impacted the most by memory price surges. Upton also notes that it’s not an April Fools’ stunt, adding, “Notwithstanding today’s date, our new computer is as real as the rest of our products.”
Follow topics and authors from this story to see more like this in your personalized homepage feed and to receive email updates.
- Stevie Bonifield
Sign in to highlight and annotate this article
Conversation starters
Daily AI Digest
Get the top 5 AI stories delivered to your inbox every morning.
More about
version
The hottest EVs from the 2026 New York Auto Show (plus one brawny concept)
With gas prices rising across the country, consumers are turning to electric vehicles as a way to save money on their commute. And while there weren’t a ton of all-new EVs on display at the 2026 New York International Auto Show, we did see some notable debuts from automakers including Subaru, Kia, Hyundai and more. So here’s a look at some of the most interesting upcoming EV models on display today, including a handful of previously announced vehicles that we haven’t had a chance to see in person before. Subaru Getaway Sadly, Toyota didn't bring the Highlander EV to the NY Auto Show, so I couldn't make a direct comparison to Subaru's new three-row EV SUV. Sam Rutherford for Engadget Built on the same platform as Toyota’s Highlander EV , the Getaway isn’t just Subaru’s first three-row EV SU
Building a Real-Time AI Dungeon Master with Claude API, Socket.io, and Next.js 16
Live Demo The AI in gaming market sits at $4.54 billion in 2025 and is projected to hit $81.19 billion by 2035 ( SNS Insider , 2025). That number isn't surprising when you think about what generative AI actually unlocks for games infinite narrative branching, dynamic NPCs, and a Dungeon Master who never gets tired at midnight. I built DnD AI, a multiplayer AI Dungeon Master running on Next.js 16, Claude API (claude-sonnet-4-6), Socket.io, and DALL-E 3. This post is a technical walkthrough of the six hardest problems I ran into, and how I solved them. No fluff just the architecture decisions that actually mattered. TL;DR: Next.js App Router can't maintain persistent WebSockets, so a custom server.ts boots Socket.io and Next.js in one process Claude streaming output pipes through Socket.io t
I Built a Zero-Dependency Supply-Chain Security Scanner for Node.js — 18 Checks, One Command
The npm install trust problem When you run npm install , you're trusting hundreds of strangers to not run malicious code on your machine. And that trust has been broken — repeatedly. Packages like event-stream , ua-parser-js , and coa were hijacked to steal credentials, install backdoors, and exfiltrate data through postinstall scripts. By the time npm install finishes, the damage is already done. The traditional answer? npm audit . But that only catches known CVEs . It completely misses: Typosquatted packages hiding in your lockfile Dropper packages that curl | sh in postinstall Tampered package.json files swapped after install C2 domains hardcoded in dependencies Stolen npm tokens used to publish without CI/CD provenance I needed something better. So I built it. Meet sec-check — one comm
Knowledge Map
Connected Articles — Knowledge Graph
This article is connected to other articles through shared AI topics and tags.
Discussion
Sign in to join the discussion
No comments yet — be the first to share your thoughts!