A while back I came across someone’s write-up of a 1U firewall appliance they’d picked up from AliExpress for $290. Intel N100, four 2.5G Intel i226-V ports, a PCIe slot for SFP+ modules. Runs pfSense. One year on, they reported zero freezes, zero reboots, quiet as you like, cool enough in a home office with no air conditioning.

That last detail stuck with me. No AC and it just keeps going. That’s the kind of reliability review I actually trust, because nobody’s trying to sell you anything.

There’s a particular kind of frustration reserved for software that was genuinely useful, and then gradually wasn’t.

Netdata used to be exactly what I wanted. Install it, point a browser at port 19999, and immediately get a dense wall of real-time graphs showing exactly what your machine was doing. CPU, memory, disk IO, network throughput. All of it, updating every second, no configuration required. For a home server running a few containers and some self-hosted services, it was perfect.

So Plex has basically killed the Lifetime Pass. The price jumped to $250 USD before they stopped selling it altogether, and the online discourse has predictably split into two camps: people saying “just switch to Jellyfin, it’s easy,” and people who’ve actually tried to switch everyone in their family to Jellyfin.

Those are very different groups.

I’ve been following this closely because I’m in the second group. I run a small Plex setup that my wife and teenage daughter use, plus a couple of extended family members who I foolishly told about it years ago. So “just use Jellyfin” is a fine answer for me, sitting here at my desk with a terminal window open. It is a substantially less fine answer for my mother-in-law, who uses a mid-range Samsung TV and whose entire model of computing is “press the button that makes the thing happen.”

There’s a particular kind of dread that comes from watching a tool you actually trust start to show cracks. Not a dramatic collapse, just a quiet shifting of furniture. A page quietly updated. A couple of long-serving executives out the door. A new CEO whose LinkedIn profile prominently features “mergers and acquisitions” and experience with private equity firms.

That’s where Bitwarden is right now.

If you’re not across it: Bitwarden is a password manager with a genuinely good reputation. Open source, reasonably priced, a free tier that wasn’t insulting, and a self-hosted option that let the more technically minded run their own server. That last part spawned Vaultwarden, a community-built alternative server implementation that made self-hosting dramatically easier. The whole setup was, frankly, a model for how this stuff could work.

There’s something deeply satisfying about watching a piece of “dead” hardware get a second life. I’ve been following a thread online this week about someone who turned their broken Steam Deck — the LCD screen had given up the ghost — into a fully functional NAS running Debian 12, and honestly, it’s the kind of project that makes me grin like an idiot.

The setup is genuinely clever. Debian 12 minimal install (no GUI, because why would you need one?), a 2.5GbE USB NIC, 6TB of main storage plus a 4TB backup drive, and rsync doing incremental backups at around 280MB/s. That’s not shabby at all for repurposed gaming hardware sitting on someone’s desk. They’ve even wired up a Stream Deck for one-button safe shutdown, HDD temperature checks, and quick SSH access. The chef’s kiss detail though? A small secondary 8.8" HDMI display running Glances locally for real-time system monitoring — CPU, RAM, network, processes, all at a glance without needing to SSH in.

Been down a rabbit hole this week reading through a thread about self-hosting and CGNAT, and honestly, it’s one of those topics that sits right at the intersection of “deeply nerdy” and “genuinely important infrastructure that affects real people.” Bear with me if you’re not in the IT world — I’ll try to make this relatable.

For the uninitiated, CGNAT (Carrier-Grade NAT) is basically your ISP hiding your connection behind a shared IP address. Think of it like living in an apartment block where everyone shares the same street address — great for the landlord who doesn’t have to manage individual addresses, not so great if you want people to actually find your specific door. For those of us who like to self-host services at home — a personal media server, a game server, a home automation dashboard — CGNAT is an absolute pain in the neck.

Someone on the internet built a web server that runs on solar power and idles at 27MB of RAM. I’ve been thinking about this all week and I can’t stop smiling about it.

The setup is gloriously minimal: a Raspberry Pi Zero W running Alpine Linux in diskless mode — meaning the entire OS runs in RAM — with lighttpd serving static sites and a small Python app handling file sharing. The whole thing is powered by a couple of solar panels feeding into a cheap power station. It handles somewhere between 5 and 15 concurrent users without breaking a sweat, and it costs next to nothing to run. This is the kind of project that makes me remember why I got into tech in the first place.

There’s a particular kind of frustration that builds up slowly when you’re dealing with the modern web. You need to do something simple — resize a photo, strip some metadata, blur a face — and suddenly you’re being asked to sign up for a free trial, verify your email, and “unlock premium features” just to do what should take thirty seconds. It’s exhausting. And it’s gotten worse, not better.

So when I stumbled across a project this week — essentially Stirling-PDF but built for images — I found myself genuinely interested. The pitch is clean: one Docker container, browser-based, everything runs locally, your files never leave your machine. Thirty-plus tools covering the usual suspects like resize, crop, rotate, compress, and convert, but also some more interesting stuff like background removal, face and licence plate blurring, OCR, and object erasing. The developer is building it openly, asking for feedback, and has explicitly said they’re not interested in making it another “AI-wrapped gimmick or subscription trap.”

I came across a fascinating discussion online about someone who built a fully self-hosted web scraping infrastructure using 50 Raspberry Pi nodes, and honestly, it’s been rattling around in my head for days now. Not because it’s the most efficient solution—quite the opposite, actually—but because it represents something I find increasingly rare in our field: building something just to see if you can.

The setup is admittedly bonkers. Fifty Raspberry Pis, each running Chrome via Selenium, each with its own VPN connection, all coordinated to scrape job postings. The whole thing is local—no cloud services, just hardware sitting in someone’s home, collecting 3.9 million records over two years. There’s even an IoT power strip that automatically power-cycles nodes when they stop responding. It’s automated chaos, and I kind of love it.

There’s a conversation happening right now across tech communities that feels both refreshing and frustrating in equal measure. People are genuinely fed up with Discord’s data hoarding practices and are actively looking for alternatives. The thing is, we’ve been here before, haven’t we?

Someone recently posted asking about open-source TeamSpeak alternatives for self-hosting, and the responses painted a picture that’s all too familiar. The nostalgia hit hard when someone mentioned paying three dollars a month for a Ventrilo server back in 2006. Remember those days? When we actually paid for services and in return, we got exactly what we signed up for – no data harvesting, no feature creep, no sudden policy changes that make you feel violated.

I’ve been running Immich for a while now as my self-hosted photo management solution, and it’s been brilliant. For those who haven’t heard of it, Immich is essentially an open-source alternative to Google Photos that you can run on your own hardware. No subscription fees, no cloud storage limits, and most importantly, complete control over your data. It’s exactly the kind of project that makes the open-source ecosystem so valuable.

There’s something quietly revolutionary happening in the tech world right now, and it’s playing out in GitHub repositories and Docker containers rather than boardrooms and venture capital pitches. The self-hosted software movement is experiencing a genuine renaissance, and I’ve been spending far too much of my free time lately diving down rabbit holes of fascinating new projects.

The catalyst for this post was stumbling across a discussion thread asking about newer self-hosted projects worth watching. What struck me wasn’t just the number of responses, but the sheer variety and ambition of what people are building. We’re not talking about reinventing the wheel here – these are thoughtful solutions to real problems, often created by developers who got frustrated enough with existing options to build their own.

There’s something oddly humbling about discovering your “secure” setup isn’t quite as bulletproof as you thought. I came across a discussion recently where someone found their Minecraft server had been visited by an unknown player, despite being confident it was locked down behind Tailscale with proper firewall rules. The kicker? They’d left port 443 open at some point “by mistake.”

Look, I get it. We’ve all been there. You set something up, you think you’ve got all your ducks in a row, and then reality comes knocking with a gentle reminder that security is less about a single tool and more about layers of careful configuration. What struck me about this discussion wasn’t just the breach itself, but the fascinating ecosystem of Minecraft server crawlers and griefers that apparently exists out there in the digital wilderness.

I recently stumbled across a blog post from someone who’s been self-hosting for thirteen years, documenting their journey to what they consider their ideal setup: OpenSUSE MicroOS with Podman. It’s a fascinating read, but what really caught my attention wasn’t the technical stack itself – it was the discussion it sparked about complexity and what that even means in our world of DIY infrastructure.

One commenter absolutely nailed it: “There’s some major self-delusion involved in any self-hoster when they say their DIY stack is ’low complexity’. Let’s be honest, nobody else knows wth we did in there. We all build arcane rat’s nests and then go ‘isn’t that beautiful?’”

There’s a particular kind of frustration that comes with finding your carefully curated music collection locked behind ransomware encryption. It’s not the sort of thing you expect to happen to a Raspberry Pi running a music server in your home network. Yet here we are, and someone in the self-hosting community just lived through exactly that scenario with want_to_cry, a relatively unknown ransomware variant that targets vulnerable SAMBA configurations.

What struck me reading through the thread wasn’t just the incident itself, but the follow-up discussion—and more importantly, how the person who got hit took ownership of their mistakes and shared them publicly. That takes guts, especially when admitting you didn’t fully understand what DMZ mode actually does on your home router.

I came across an intriguing post the other day that really got me thinking. Someone was asking about adding ads back into their Plex or Jellyfin setup - but not for the reasons you’d expect. They wanted mandatory breaks to remind their kids (and themselves) to do chores or quick exercises during binge-watching sessions.

My first reaction was probably the same as yours: “Just pause it yourself!” But the more I thought about it, the more I realised this parent was onto something quite profound about how we consume media in 2024.

Someone on Reddit recently announced Wizarr 2025.10.0, and buried in their feature list was this absolutely perfect line: “Overengineering solutions is in the essence of selfhosting and homelabbing!” The comments that followed were gold - people practically queuing up to admit they felt personally attacked by this statement. One user mentioned implementing single sign-on through Authentik for just two users. Another wrote their own log processor because they were fed up with their existing setup not working perfectly.

I’ve been following a fascinating discussion about a new open-source project called Home Information, and it’s got me thinking about something that’s been bothering me for years: why do we keep handing over control of our personal data to companies that don’t really have our best interests at heart?

The project itself is pretty clever - it’s essentially a visual home management system where you can click on different parts of your house and access all the relevant information: manuals, service records, warranty details, you name it. But what really caught my attention wasn’t the functionality (though that’s genuinely useful), it’s the philosophy behind it. The creator has built something that runs entirely on your own hardware, stores your data locally, and doesn’t require you to sign up for yet another monthly subscription service.

I’ve been watching this fascinating discussion unfold online about someone’s journey to escape Google’s digital ecosystem, and it’s got me thinking about my own relationship with Big Tech. The original poster started what they thought would be a simple project - moving away from Google services - only to discover they’d bitten off far more than they could chew.

The whole thing started innocently enough with email. “I started small with email,” they wrote, which had me chuckling into my morning latte. There’s nothing small about ditching Gmail when you’ve been using it for years. The sheer number of services, accounts, and contacts tied to that one email address is staggering. But they pushed through, set up their own mail server with their own domain, and actually got it working. Fair dinkum effort there.

There’s something beautifully ironic about stumbling across a newsletter dedicated to self-hosted software updates. While the rest of the world seems obsessed with cramming everything into the cloud and paying monthly subscriptions for the privilege, there’s this thriving community of digital tinkerers who’ve decided to take matters into their own hands.

The Self-Host Weekly newsletter caught my attention this week, particularly because of the delicious contradiction in the comments section. Someone was apparently complaining about too many project updates in a newsletter literally designed to showcase… project updates. It’s like complaining that a coffee shop has too many coffee options – mate, that’s literally why we’re here.

I’ve been watching the discussion around SparkyFitness with genuine fascination this week. Here’s an open-source, self-hosted alternative to MyFitnessPal that just dropped its first Android app, and the response from the community has been nothing short of enthusiastic. But what really caught my attention wasn’t just the technical achievement – it’s what this represents in our increasingly surveillance-heavy digital landscape.

The project itself is impressive enough. SparkyFitness offers nutrition tracking through multiple food databases, exercise logging, water intake monitoring, and even has an AI nutrition coach in development. The developer has clearly put serious thought into creating something comprehensive rather than just another half-baked alternative. But here’s what gets me excited: people are genuinely thrilled about the prospect of running their own fitness tracking server.

I’ve been following the development of Spotizerr with interest lately, and the recent 3.0 update has got me thinking about something bigger than just another self-hosted tool. Here’s a project that lets you essentially build your own music streaming service by pulling tracks from Spotify and Deezer directly to your personal server - and frankly, it’s exactly the kind of innovation we need right now.

The timing feels particularly relevant when you consider how streaming services have been tightening their grip on content and pricing. Just last month, Spotify announced another price hike, and we’ve all seen how quickly our favourite albums can vanish from platforms due to licensing disputes. Meanwhile, tech giants are hoovering up our listening data to feed their advertising algorithms. It’s enough to make anyone consider alternatives.

The world of self-hosting has been quietly revolutionising how we manage our digital lives, from music streaming with Jellyfin to photo storage with PhotoPrism. Now, it seems gaming is getting its turn with projects like Drop, a FOSS alternative to Steam that lets you host your own game library.

When I first came across the announcement for Drop v0.3.0, my DevOps brain immediately perked up. Here’s a project that’s tackling something I’ve been frustrated with for years – the complete dependence on corporate gaming platforms and their ever-changing terms of service. The idea of self-hosting your own game distribution platform feels both ambitious and necessary.

I’ve been mulling over a question that popped up in one of the tech communities I follow recently, and it’s one of those deceptively simple queries that actually opens up a fascinating discussion about security practices. Someone asked why using a reverse proxy is considered safer than directly exposing service ports, and honestly, their follow-up question was spot on: “Doesn’t it just bump the problem up a level?”

The question really resonated with me because it touches on something I see all the time in my DevOps work – people implementing security practices without fully understanding the underlying principles. It’s like following a recipe without knowing why each ingredient matters. Sure, you might end up with something edible, but you won’t know how to adapt when things go sideways.

The recent release of OmniTools v0.4.0 caught my attention while browsing through various self-hosting communities. This Swiss Army knife of utilities represents exactly what we need more of in today’s digital landscape - tools that put privacy and user control first.

Working in IT for over two decades, I’ve witnessed the gradual erosion of digital privacy as more services moved to the cloud. Remember when we could just run software on our computers without worrying about where our data was going? These days, even the simplest task like converting a PDF to EPUB involves uploading our documents to some random server, probably getting tracked, and possibly having our data stored who-knows-where.

The other day, while setting up a new development environment for work, I stumbled across an interesting discussion about self-hosting email servers. It brought back memories of my own attempts at email independence over the years, and the subsequent frustrations that followed.

Running your own email server used to be a badge of honor in the tech community. Back in the late 90s and early 2000s, it was almost a rite of passage for system administrators and tech enthusiasts. The technical challenges were significant but manageable - configuring Sendmail or Postfix, setting up spam filters, and maintaining proper DNS records.

The tech world is buzzing with discussions about Plex’s recent changes to their remote streaming policies, and it’s sparked quite the debate in various online communities. This latest move has finally pushed me to do something I’ve been contemplating for a while - making the switch to Jellyfin for my home media server needs.

Going through the online discussions, it’s fascinating to see how this situation mirrors so many other cases where proprietary software gradually tightens its grip on users. The story always seems to follow the same pattern: start with a great product, build a loyal user base, then slowly introduce more restrictions and monetization.

The online discussion about someone ditching Google Photos caught my attention this morning. It resonated deeply with my own journey of reducing dependency on big tech services, though I must admit I’m still taking baby steps in that direction.

Reading through the thread, I was struck by how many people shared this person’s revelation about self-hosting. There’s this persistent myth that running your own server requires enterprise-level infrastructure or a computer science degree. The reality is far more accessible – you can repurpose old hardware and build something meaningful with it.

The developer tools landscape never ceases to amaze me with its constant evolution. Recently, I stumbled upon an interesting discussion about a new whiteboard IDE that combines Excalidraw’s canvas capabilities with Coder’s development environment management. The concept immediately caught my attention, particularly because it addresses a pain point I’ve experienced during remote collaboration sessions.

Working from my home office in Brunswick, I’ve often found myself juggling between different tools during technical discussions. There’s usually a whiteboard app open in one window, VS Code in another, and perhaps a terminal somewhere in the mix. The idea of combining these elements into a single, cohesive interface is genuinely exciting.

The tech world often pushes us toward the latest and greatest hardware, but there’s something deeply satisfying about seeing old devices given new purpose. Today, I stumbled upon a fascinating post about a repurposed laptop serving as a home server, and it sparked some thoughts about our relationship with technology and sustainability.

Picture this: a battle-scarred laptop, survivor of a neighbor’s domestic dispute, transformed into a fully functional home server. The specs would make most tech enthusiasts cringe - a humble Celeron processor, 4GB of RAM, and a mix of storage drives. Yet, this modest setup runs multiple services including Nextcloud and Immich, effectively replacing expensive cloud subscriptions.

Looking through various online discussions about self-hosted applications recently got me thinking about those lesser-known tools that become indispensable once you discover them. While everyone talks about the usual suspects like Plex, Home Assistant, and NextCloud, there’s a whole world of brilliant but underappreciated software out there.

One fascinating discovery was Wallos, a subscription manager that helps track all those recurring payments that seem to multiply when you’re not looking. Sure, you could use a spreadsheet, but having a dedicated tool that sends notifications before renewal dates is incredibly valuable in this subscription-heavy world.

The self-hosting community is experiencing a fascinating shift in sentiment regarding media servers, particularly around Plex and its open-source alternative, Jellyfin. This debate hits close to home for me, as I’ve spent countless hours setting up and maintaining media servers in my home office.

The core issue that keeps surfacing is the fundamental disconnect between what self-hosting should mean and what some popular solutions actually deliver. When we talk about self-hosting, we’re essentially discussing taking control of our digital services. Yet, ironically, some of the most popular self-hosted solutions still tether us to external dependencies.

Everything started with a simple thought: “I’ll just set up Plex on my NAS.” Famous last words. Looking back now, I can’t help but laugh at my naivety. That innocent decision has spiraled into what can only be described as a full-blown obsession with self-hosting and digital independence.

The catalyst was frustration with streaming services. Remember when Netflix was the only game in town? Now we’re expected to juggle half a dozen subscriptions just to watch our favourite shows. Even then, content appears and disappears at the whim of corporate licensing deals. It’s maddening.

The intersection of technology and music consumption has always been a fascinating space. Recently, I stumbled upon an interesting discussion about a tool that bridges Spotify’s vast library with self-hosted music servers. It’s sparked quite a debate in the tech community, highlighting the eternal struggle between convenience and ethical considerations.

Remember the days of Napster and Limewire? We’ve come a long way since then, but the fundamental questions remain the same. Today’s streaming services have solved many problems, but they’ve created new ones too. The massive catalog of songs at our fingertips comes with a cost - not just the monthly subscription, but also in terms of audio quality and artist compensation.

The recent buzz around self-hosted alternatives to Google services has got me thinking about my own digital autonomy journey. Don’t get me wrong - this isn’t about bashing Google. Their services are polished and convenient, but there’s something deeply satisfying about taking control of your digital life.

My home server, humming away in the study, has become quite the Swiss Army knife of services. The star of the show lately has been Immich, a remarkably capable alternative to Google Photos. What started as a curious experiment has turned into my primary photo management solution. The face recognition feature works surprisingly well, even on my modest hardware, and the ability to share libraries between family members is brilliant.

Remember when having a home server meant running a simple file share and maybe a Plex server? Those days seem almost quaint now. The self-hosting community has evolved dramatically, and this week’s developments really highlight how far we’ve come.

The latest buzz around Glance, a multi-purpose dashboard and feed aggregator, caught my attention during my morning batch brew. What fascinates me isn’t just the tool itself, but how we’re now effectively creating dashboards to manage our dashboards. It’s like inception for home lab enthusiasts, and I’m here for it.

Standing in my home office, staring at the humming server rack tucked away in the corner, I reflected on how much things have changed over the past year. The journey into self-hosting started innocently enough with a simple Raspberry Pi running Pi-hole to block ads across our home network. Now, that modest beginning has snowballed into what my wife lovingly calls “that computer thing you’re always tinkering with.”

The online self-hosting community has been buzzing lately about various setups and must-have applications. Reading through different configurations, it’s fascinating to see how people approach their digital independence differently. Some focus on media management, others on productivity tools, and quite a few on privacy-focused alternatives to popular cloud services.

Standing in my home office, sipping my flat white and staring at the small cluster of Raspberry Pis humming away on my desk, I’ve been thinking about the state of self-hosted software. The topic caught my attention during a fascinating discussion about what tools people wish they could self-host but can’t find decent alternatives for.

What struck me most wasn’t the list of missing tools, but rather how far we’ve come. The open-source ecosystem has matured significantly over the past decade. Remember when running your own server meant endless nights of troubleshooting and a PhD-level understanding of Linux? Those days are largely behind us.

The self-hosting community has been buzzing lately with discussions about Nextcloud, and it’s fascinating to see how polarised the opinions are. Reading through various forums and discussions, I’m struck by the stark contrast between those who swear by it and others who can barely contain their frustration.

Having run my own home server setup from my study in Brunswick for several years, I’ve experienced firsthand how self-hosted solutions can either be a dream or a nightmare. The Nextcloud situation reminds me of the early days of Linux on the desktop - what works flawlessly for one person might be completely unusable for another.