The cloud is convenient, until it isn't.
You upload your photos, you sync your contacts, you click through the cookie banners, then prices go up, or you read about the family that lost their entire Google account over a medical photo sent to their doctor.
At some point, the question shifts from, why would I run this myself, to why aren't I?
My guest this week is Alex Kretzmar.
He's the head of DevRel at Tailscale, the longtime host of the Self-Hosted Podcast, and co-founder of LinuxServer.io.
We cover what self-hosting really means in 2026, the apps worth running yourself, like Image and Home Assistant, why Docker Compose ties it all together, and how Tailscale lets you reach any of it from anywhere without opening a single port.
If you've been thinking about pulling your digital life back behind your own walls, this is your roadmap.
This is Talk Python To Me, episode 546, recorded April 27th, 2026.
Talk Python To Me, yeah, we ready to roll, upgrading the code, no fear of getting old, async in the air, new frameworks in sight, geeky rap on deck, Quarth Crew, it's time to unite, we started in pyramid, cruising old school lanes,
had that stable base, yeah, sir.
Welcome to Talk Python To Me, the number one Python podcast for developers and data scientists.
This is your host, Michael Kennedy.
I'm a PSF fellow who's been coding for over 25 years.
Let's connect on social media.
You'll find me and Talk Python on Mastodon, Bluesky, and X.
The social links are all in your show notes.
You can find over 10 years of past episodes at talkpython.fm, and if you want to be part of the show, you can join our recording live streams.
That's right, we live stream the raw, uncut version of each episode on YouTube.
Just visit talkpython.fm/youtube to see the schedule of upcoming events.
Be sure to subscribe there and press the bell so you'll get notified anytime we're recording.
Temporal is hosting their yearly conference, Temporal Replay.
Join your peers at Replay, the conference on orchestrating durable workflows and agents.
May 5 to 7 in San Francisco.
Visit talkpython.fm/temporal dash replay and use the code TALKPYTHON75, all one word, all caps, to save up to $449 on your ticket.
Alex, welcome to Talk Python To Me.
Well, thanks for having me.
This is Comfy Surroundings. Hello.
I'm really excited to be talking about self-hosting, something I have talked around on the podcast a little bit, and I had the Home Assistant guys on for a while long ago when Home Assistant was this little boutique thing that people might find interesting.
Now it's kind of blown up, but I'm really looking forward to talking about digital sovereignty, running your own apps, not being dependent on huge tech companies for every little thing, and just the joy of finding something in open source
or just out there and going, hey, what if I just run that myself?
And so I thought of Alex, thought of you, and I said, hey, we got to talk about this.
Great, yeah.
Well, thanks for having me.
Yeah, you bet.
So before we dive into all those things, give people a bit of a background about yourself.
Yeah, well, I'm Alex.
I, as you perhaps can tell from the accent, originally hail from the UK.
I live in North Carolina these days, though, for my sins.
And I work for Tailscale.
I head up their DevRel department and primarily make YouTube videos for them.
You know, it's an interesting company to work for because it's all product-led growth.
So my job is to really get people enthused and excited about the product and all the interesting ways in which they can access their stuff remotely.
And then, I don't know, people bring it to work and that's how the company makes money.
So I get paid essentially to make YouTube videos about hacking on self-hosted applications.
And I still don't quite know how that happened.
I think you guys over at Tailscale are doing a great job.
We're going to go into it later when we get into sort of the security and accessing stuff of all the self-hosting things.
But I started using Tailscale a couple of years ago and yeah, it's fabulous.
So very nicely done.
So some other stuff I've done, I used to do a podcast called Self-Hosted, wrapped that up last year.
But I do a new one now called Bitflip with a few of my buddies.
And again, from the self-hosting universe, you can find out more about that at bitflip.show.
I hope some self-promotion's okay.
But please, yes.
No, that sounds great.
Because I was a little disappointed to hear that you shut down Self-Hosted, the podcast, because I was just getting into it.
And then, so you're back.
Yeah, we did it.
How does it differ?
Well, not much really.
So the weird thing was about Self-Hosted, and I don't know if you felt this with a show with Python in the name, but I kind of felt a little bit limited by the title because I tend to approach things from a very pragmatic angle.
We were just talking before we pressed record about how important Linux and open source and all this kind of stuff is.
And yet I'm using a MacBook to record, not Linux, because it's just bulletproof reliable for media applications.
And there are all these little compromises we make all throughout our digital lives.
And so Self-Hosted as a movement, particularly in the subreddit actually, is very opinionated.
And unless you're doing absolutely everything, lock, stock, 100% yourself, there are some people who say, well, you're holding it wrong.
You're not doing it properly.
My approach has always been, it's okay to have DigitalOcean run a VPS for me, but I've still got root to that VPS and I am hosting my own website.
I'm self-hosting my own websites.
But to some people that definition doesn't sit right.
And so- You got to be running on a Raspberry Pi in your basement.
If that's not the way it is, it's not true.
Right.
And we all know that there are just limitations to doing things, like maybe you're moving house and so your website would be offline for two weeks whilst you move house.
That's probably not okay.
Or there's a storm in your area or a water pipe bursts or like any number of fates can befall things in your house.
And I'm not saying these things can't happen to a data center, but there are just mitigations in place between, you know, even just things like ISP pairing and like the data center is probably in the middle of an internet exchange building, whereas my house definitely is not.
So I kind of wrapped up the self-hosted podcast just a little bit because I felt like, I don't think I feel this way anymore, but sort of 18 months ago when we wrapped it up, that self-hosting had, we kind of said all we needed to say and that as a movement,
it was just kind of bubbling away in the background and those that had found it were going to find it and it was just sort of ticking over.
But I don't know, self-hosting is all the line trendy these days.
I think I heard Linus on the WAN show on Friday literally saying that building a NAS is trendy.
And I'm like, what?
Is it?
Okay, cool.
Well, I'm here for it.
Yeah, I'm here for it as well.
And I'm glad to hear you're still carrying on with the podcast under a different banner.
Well, the reality is that a lot of this stuff, like I said, like I do for Tailscale and for Bitflip now is this is stuff I'm doing anyway.
Like my personal YouTube channel as well at KTZ Systems.
Like I just, I'm just always like, just out of shot over here.
There is a desk covered with like five of those little Lenovo mini PCs that I'm putting into a little Proxmox Ceph cluster because I woke up last week and my home assistant was down because my little Minis Forum MS01 had lit itself on fire in the middle of the night.
And I found, ah, where's a single point of failure?
I can fix that with some clustering and high availability and so the rabbit hole continues.
Yes, I love that you have a high availability on your home network.
I'm working on it, which is another story.
But so it turns out these little Lenovo PCs, you can pick them up for about $150 or so.
Even today, even in the hardware apocalypse that we're going through.
These, you know the ones I mean, like the little one liter PCs, right?
Usually bolted onto the back of a monitor in an office or something.
And you can pick those up for about $150 and they will run every self-hosted app you could possibly throw at them.
In reality, certainly just for individual use, they are absolutely all the average person needs as a home server.
And so one of the things I like to do with them is put what's called Proxmox on it, which is a hypervisor that lets you run virtual machines, something called LXCs, Linux containers, as well as Docker.
We love us some Docker, I understand.
Basically, if it doesn't run in Docker, I don't run it.
I'm just going to trigger some people in the audience, I'm sure.
You know what?
I'm with you.
When I go and look at one of these things that is potentially self-hosted, I'm like, well, where's the Docker Compose file?
Otherwise, I'm not sure we're going to be continuing down this path.
I mean, you Python people know all about standardized packaging formats and stuff like that.
Like the prevalence of pip and then these days, uv, of course.
Like, you know, these things matter.
They're like, how users round off those rough edges of how it gets from my keyboard in my lab to your computer and wherever you are.
Docker kind of closed that last 10%.
I mean, a lot of the primitives of Docker existed well before, like C groups and namespaces in the Linux kernel.
All that stuff existed for years before Docker came along.
All they did really was provide a standardized packaging format, which is really just a tarball, and a standard way of building those tarballs with a Docker file, like a recipe.
That was all they did, and provided a little bit of plumbing and networking.
Like, we just ignore all the technical details they did.
But essentially, they just closed that last 10% of usability, and suddenly, me, as a computer science student, could run any application in the world without having to dive into Systemd and init scripts and database migrations
and blah, blah, blah, blah.
It was just...
Yeah, complex networking, attached volumes.
Like, there's a lot of stuff going on there, yeah.
Yeah.
Docker is life in this house.
A long time ago now, I co-founded a website called Linuxserver.io.
I don't know if anybody in the audience has heard that, but it's the largest, I believe, sort of open-source containerization movement project on the internet, and that was born out of the fact that sort of 10, gosh, yeah, maybe 12 years ago
that Docker was pre-1.0, so it was very sort of nascent at that point, and it was...
There was just...
There were no standards.
Like, the readmes were all over the place, or if there even was one.
There were no sort of standardized base images.
People hadn't cottoned on to, like, supply chains, and, you know, today it's a hot topic, but sort of back then, it was, oh, if it runs, I'm happy, you know?
So Linux Server was sort of my attempt, our attempt, I should say, at fixing some of those issues, and, you know, we packaged up media server apps back in the day, like Plex, and some of the other slightly less salubrious
applications you might find on the internet, as well as a bunch of other self-hosting stuff, which we should probably get into talking about some of the apps.
Yeah, absolutely.
Well, to kind of put a bookend on your introduction, I do just want to quickly ask you about your racing and VIR and stuff like that.
You know, and I was looking to contact you, I was going through your About page, and I saw a car racing around a racetrack, and I thought, well, can't not talk about that.
I've had folks from Formula One and from NASCAR on the show before, and I'm a big fan of these kinds of things.
Yeah, I do too.
So, that's one of your hobbies?
That's pretty awesome.
Yeah, I've followed Formula One since, well, I remember sitting on my dad's knee as a kid watching Damon Hill, Nigel Mansell, go around Silverstone, so it's been a while.
There's obviously a new crop of F1 fans, which is amazing, thanks to the Drive to Survive stuff, but I've followed it for years.
I just enjoy watching, I just enjoy watching the sport.
It's like a nerd soap opera in a way.
Not a fan, honestly, of these new regs, though, with the sort of the super clipping and all this kind of stuff.
It'd be interesting to see what happens when we get to, where's the next one?
Miami, I think.
Yeah, I believe it is Miami and then Canada.
So, for people who don't know out there, Formula One is called Formula One because there's one formula on how to build the cars, but then all the teams generally, almost from scratch, build their cars.
And every couple, every four or five years, they're like, okay, we're completely doing it differently.
And so, this year, they've completely done it differently and there's a lot of controversy.
I don't know, it's interesting, but.
Yeah, they've gone for like this 50-50 split between the combustion engine and the battery power, but the batteries can't harvest enough energy every lap.
So, I don't know what genius thought of that, but, so they get halfway around the lap and they lose half of their horsepower, which can mean you've got closing speeds between cars of sort of, I don't know, 50 to 100 miles per hour.
And we saw in Japan in the last race, quite a bad accident as a consequence.
Right there in Spoon, it wasn't pretty.
I know all of the electric stuff and like the hybrid things and IndyCar and even way, way more so in Formula One is for environmental friendliness.
And hey, I drive an electric car, I love electric cars and I'm all about caring about the environment and stuff, but the 20 cars driving around the track is nothing compared to the 300,000 people that took airplanes to get there.
And then when they ship the cars on planes halfway around the world, like the fuel spent when they're racing, it has nothing to do with, you know, it doesn't even register on the number of the environmental impact of that.
So I don't know, I kind of long for the Damon Hill days with like, Oh, me too.
Fast engines, you know.
On our honeymoon, actually, my wife and I, we ended up in Milan on race weekend, totally by accident, genuinely by accident.
We were booking this like interrail trip around Europe and my itinerary landed us in Milan on race weekend.
I didn't actually know at the time and all hotels for that weekend spiked.
They're like two or three exiting costs and I'm like, what's going on?
So I just typed Milan events, September, whatever.
Anyway, turns out, so we went to Monza and I'll never forget we were stood at, it was the Iscari chicane so it's on the opposite side from the start, finish straight and the noise, I think there were V8s, I don't think there were V10s, I think there were V8s then but just the noise of them sitting on the grid
waiting to go, it was like a bunch of angry wasps and you could hear it and it's half a mile away.
Amazing, amazing.
We lost something when they went to the V6 turbo hybrid stuff.
100%.
All right, last bit, I mean a lot of people are fans of F1 and racing, not many of them end up on a race track.
Oh yeah, that's a whole different kind of fresh.
Yeah, so I've been into, I've owned seven Volkswagen Golfs over the years, culminating in the Golf R a few years ago and I just had to take it on a track.
Like in England I went on this run what, we call it a run what you brung track evening and I went to Brands Hatch and I literally turned up without even a helmet, without doing any prep or whatever and they just let me untrack.
Just, I couldn't believe it.
And then I had the best evening of my life and then we emigrated and came here and I was like, I've got to scratch that itch.
So I went to the internet and found out to go to VIR you have to do all sorts of training and get like instructors and it all sounded a bit much.
But anyway, VIR is a serious racetrack.
Like you can end up I think on the back straight in my little golf I was doing 140 on the back straight and there are moments coming up through the uphill essays at VIR where you're just like, if this goes wrong she's going to hurt.
And in the end I ended up scaring myself a bit silly but I had real fun but there was just a couple of moments where I was like, you know, I've got a kid at home.
I should probably, this is a young man's game or an old man's game when you've got nothing left to lose, I guess.
Yeah, that's true.
There's a, it's a bimodal sort of experience.
Yeah.
But I learned a lot like I learned how to change brake pads, brake fluid.
I fitted a new intercooler to my car.
I upgraded the turbo.
I did tuning.
Like technical stuff.
I like learning how things work.
Same with software, same with cars.
It's basically just one is slightly more visceral and arguably the stakes are a bit higher if you screw up installing a turbo it can be very expensive.
It's worse than, oh, I got to reinstall that.
Yeah.
Good fun though.
No, I'm sure it's amazing.
That sounds very, very cool.
So what a great experience.
Let's talk the main, main topic.
Like, I guess we've been using the word without really defining it.
Like what is self-hosting for people who are just like, you know, they, they haven't done these sorts of things.
I think as I, as I alluded to earlier, there's a broad spectrum of definitions to what self-hosting means to different people, depending on how tightly you hold certain beliefs around definitions.
But for me, it means the business model that exists is feeding the open source developer or small team that built it.
Like it's, it's not, are you familiar with Corey Doctorow and his idea of n-certification?
Yeah.
The idea that a company will give some, we, we've been accused of this at Tailscale and I don't think it's actually going to happen.
the CEO at Tailscale, I have great faith in Avery's leadership, honestly.
I know I sound like a corporate shill saying that, but I genuinely believe it.
So, the idea of n-certification is that a company takes a bunch of money from venture capital or some other source and gives the product away.
We saw it with Uber, for example.
Like they give the product away at a loss leading price point to gain market share.
We've seen it in multiple industries over the years.
Walmart is a great example.
They'll put mom and pop short stores out of business in the local town and then slowly raise the prices.
Right, right.
Once everyone's gone, it's, it's, they have no choice but to go there.
Exactly.
And so the idea of n-certification in software is, is very prevalent.
We've, we're seeing it with streaming services right now where they're just gradually turning the screw, lifting the prices, pulling out shows without your control.
All of these things have, are really boiled around one central point.
I mentioned the business model.
That's one thing, but really it's control.
And do you have control over the services that are running your life?
If you have Google in your life, you probably don't.
If you have Apple in your life, you probably don't.
You feel like you do, but there are countless examples.
For example, there was one a couple of years ago where, I think this was in the New York Times.
We definitely covered this on Self-Hosted a while ago where a mother took pictures of their kids, a medical issue of their kids, private areas, and sent it to their doctors through telehealth.
They also sent the picture to their husband through a messaging app, which then meant that that picture got backed up to, I think it was Google Photos.
It might have been Amazon.
Please don't quote me on this.
I'm just speaking from two-year-ago memory.
And they got flagged as a CSAM issue, like a child pornography issue.
And they had most of their digital life cancelled.
They were locked out of their accounts.
They were basically banned from that company.
Might have been Google.
Let's go with Google.
And just the idea of being locked out of my Gmail.
I mean, just stop and think about how much of your life is in your Gmail inbox.
How long have you had yours?
15 years.
I think there's over a quarter million emails in my Gmail account.
It's ridiculous.
I mean, it is ridiculous.
And extrapolate that from email to photos.
Extrapolate that to music, to videos, to, I don't know, taxis and invoices, all this stuff.
There are just so many different facets of our lives that we've given up to third parties that are either being used to train the next round of industrial revolution, oligarchy revolution, like AI models, or they're being used to feed an advertiser's
bottom line and create a profile about you and who you are and what you do and who you associate with.
Because make no mistake, when your photo gets uploaded to Google Photos, they are making a map of all the faces in that photo.
Whether you know the person in the background or not, Google will know them because they probably have Google Photos too.
And they can scan that Alex was stood next to Fred Smith on June the 21st, 1983.
And like, they can create such incredibly detailed profiles about people.
And if that doesn't bother you, self-hosting is probably not for you.
But I don't know about, I don't know about you, but it makes me deeply uncomfortable that I'm giving up these freedoms and this privacy without really appreciating that I'm doing so.
Like a lot of the transaction is very, what's the word I'm looking for?
Like it's just not a fair, it's not a fair exchange of value for value.
It's asymmetric.
Yeah.
Asymmetric.
Very asymmetric.
Yeah, absolutely.
Totally.
And I want to just, while we're sort of setting the stage, I just want to put an idea out there that this kind of stuff is super valuable and a good thing to keep in mind, not just for individuals, which 100% that it is, but also for developers running their software.
Do you necessarily need to take all of your data and put it into an AWS managed service or an Azure managed service or send all of your users information through, say, Google Analytics to Google to then turn around
a mine or to other places?
You don't have, I feel like people think they have to.
You don't have to.
It almost feels inevitable, doesn't it, these days?
That, oh, well, everyone else is doing it.
I may as well.
Yeah.
We'll get the cookie banner.
We'll put it up.
People are used to, everywhere they go, they click the cookie banner.
True.
But there are entirely serviceable alternatives to almost every single proprietary service that you have.
Google Analytics, let's start with that one.
There's an open source app called Plausible.
It does almost everything that Google Analytics does.
It just, the analytics stay within your world and they're not, they're not kind of fed into the Google machine.
And whether that's a, like, on feature parity, there's an argument to be made there about, like, well, Google's more invasive so they have more data.
I don't see that as a plus point, personally.
This portion of Talk Python is brought to you by Temporal and the Temporal Replay Conference.
Previously, I've told you about Temporal's open source framework and I've had Mason Egger on the podcast.
If you've built background jobs or multi-step workflows, you know how messy things get with retries, timeouts, partial failures, and keeping state consistent.
This is where Temporal's got your back with their open source framework.
And if that kind of workload is what you're building, you should definitely consider attending the Temporal Replay Conference.
It's hosted May 5-7 in Moscone Center in San Francisco.
Join your peers at Replay.
Temporal's conference on orchestrating durable workflows and agents.
You'll learn real-world patterns for reliability, failure handling, and scale from developers building themselves, including speakers from OpenAI, Replit, and Abridge.
Check out Replay 2026 at talkpython.fm/temporal dash replay and use the code talkpython75 all one word to save up to $449 on your ticket.
That's talkpython.fm/temporal dash replay and code talkpython75 all one word.
The link is in your podcast player's show notes.
Thanks to Temporal for supporting the show.
I don't either.
And I think this is an interesting segue to finding some of the interesting apps here.
So I went to pull up plausible.io and I think you're right.
I think plausible is really great.
The one that I'm using is umami.is which is sort of a peer to plausible.
I believe, I think you can pay for both of them.
I'm not 100% sure about umami right now.
Yeah.
I don't know your ad book must be doing some hard lifting over there because plausible works just fine for me.
You're using umami, are you?
Yeah, I'm using umami and I looked at plausible as well and umami seemed a little more oriented towards self-hosting whereas plausible self-hosting seemed like oh, you could do it but we're kind of this like thing that we run in the cloud and you can pay for but you technically could
and I felt like umami was like self-hosting first with, I don't even, like I said, I'm pretty sure there is a you now can pay for it as well.
But I wanted to bring up this you, the site can't be reached because I think another interesting thing is like hosting DNS.
So like pyholes, I have nextdns.io which is why I can't go to plausible right now unless I log in and tell it plausible is okay.
Same thing for umami by the way.
I think, what about, let's talk, let's, you're at Tailscale, let's talk networking.
We'll get back to the use of Tailscale when we kind of wrap things up but like, do you use Pyhole or do you use any of these sort of managed things outside just your browser?
Well, the modern internet basically requires using an ad blocker.
I mean, when you, I'm fortunate to work from home so I'm almost always with inside these four walls where I have an AdGuard Home instance running and my DHCP server when, whenever a device requests an IP address from the router,
it will hand out the DNS server in my local network as the AdGuard Home instance.
And AdGuard Home's job is to run a list of websites that it thinks are serving ads and it will block those at the DNS level.
So simply what will happen is you will go to try and load a website and it can't load certain components of the webpage and those components happen to be adverts in this case.
It's not 100% coverage but I'd say it's sort of in the 80 to 90% range which is still a heck of a lot better than having no ad blocking whatsoever.
And the idea here is that a lot of these, well, first of all, adverts use a lot of bandwidth.
They also are probably shoving down a ton of JavaScript into your browser so the performance of loading a webpage is worse.
It's using more bandwidth, it's using more processing power and on mobile, of course, that matters.
When I leave the house, I'm not under the umbrella of my AdGuard home instance anymore because it's running on, I don't know, a Raspberry Pi in my basement.
And so I've got a couple of options.
One is I can use a hosted DNS service like you do called NextDNS which basically does the same thing as a Pi hole except you pay for it.
I don't think it's a huge amount of money if I recall.
It's a couple of bucks.
It's either $1 or $1.99 a month.
It's really small, yeah.
It seems fair.
And the idea behind NextDNS, like I say, is that it does the same thing as a Pi hole or an AdGuard home.
It's just a hosted service that you pay for a managed service.
Or you can use something like Tailscale and tunnel back through your firewall remotely and set your AdGuard home as your Tailnet DNS server and then use your AdGuard home or your Pi hole from your basement that you're already running already configured
with all of your ad lists and blah, blah, blah.
You can configure that to be your DNS server.
And my wife loves these sort of like mobile games like the Candy Crushes of the world.
And they are just chocked full of ads.
And we only really talk about it when we're like traveling because she's, oh God, I wish we were at home because then I wouldn't get adverts.
Yeah, we'll just turn on Tailscale and lo and behold, no ads.
You're back to good.
I think one final little note about like running your, either your AdGuard at home or your Next DNS if you register at your router level that's really interesting is you block ads in mobile apps as well like you're mentioning or on my TV all the tracking
the TV does is short-circuited because everything on the network is subjected to it.
And I'm, you know, as long as these ad networks are serving up malicious ads, I don't feel bad about blocking them.
That's another angle of course, yeah.
Yeah, I mean, if we go to Talk Python, you know, the website, there's, ads are still there.
Why?
Because I'm not using some shady network to deliver it.
I'm just sharing content and someone who happens to talk about what we're doing, you know, and so I think that that's a, I think that's certainly something worth considering, right?
I feel like this DNS stuff is part of self-hosting at least the personal level a bit.
It's the, it's one of the fundamentals, yeah.
Networking is one of those things that you have to have it if you want to do anything in your house, like even, and I use my mother, who I love dearly, as the example of the non-technical person in my life.
Even if my mum, like she orders a router from her ISP or something like that to get Wi-Fi in her house, well, she's doing networking, she doesn't realise it.
She's getting a Wi-Fi SSID broadcast, she's getting an IP address from the router every time she connects.
The DHCP server provides a DNS server, which is probably your ISP's DNS server by default, and they are recording all of your DNS queries and selling them to the highest bidder also, I might add.
And so there are just so many layers to this onion, and DNS is the, just what, we have a five-year-old in the house, we just watched Shrek this weekend, hence the onion reference.
There are just so many layers to this onion that you just, you can keep peeling it forever, and this is one of the things that I genuinely love most about Linux, open source, self-hosting, that whole universe is that this conversation, I could literally sit here for eight hours and talk to you about different,
you know, different things, like DNS is one thing, document management is another, media streaming is another, like each of these things, they're all, they're entire industries in their own right in the real world, but in self-hosting, you can play CIS admin, you can play, you know,
the person who's running these mega corps offline, fully just in your basement, you know, and there's no, there's no business model to feed, it's literally just open source software, the true spirit of it, running in your house under your control.
Yeah, we're definitely in danger of going for eight hours, so, I hope not, but we could, right, we definitely could, and by way of, I think that's a perfect transition to talk about this place called Awesome Self-Hosted here, which is a Git repository and a website,
you know, I do, Alex, I think this is going to be a bit of a fad, it's not really catching on, there's only 288,000 GitHub stars in this.
And if you look at it, you're familiar with the Awesome Lists, of course, there are dozens of these things, but Awesome Self-Hosted, I mean, it's updated daily, like, I look at the recent Git commits and it was last updated yesterday, and there are,
how many categories?
There must be.
I don't know, but let me scroll, like, there's a couple of pages of just categories of things like e-commerce, DNS, for example, analytics.
Right.
You want to replace Jira?
It's in here.
You want to replace, I don't know, a wiki?
It's in here.
You know, it's honestly kind of overwhelming.
And so this speaks a little bit to one of my overall philosophies when it comes to self-hosting of find a problem in your life and solve it, like a real problem.
Don't just contrive one just for the sake of it.
Photos is always the universal example I go to because everybody takes photos.
And so you want to look at something like image, I-M-M-I-C-H.
And that is a self-hosted Google Photos clone, and it lives entirely on your hardware that you control.
It has machine learning, so it can learn your face.
It can do, you know, object detection.
It can do basically anything that Google Photos can do, except it lives on your hardware using your files and your compute until the end of time.
And that's an end of it.
Like, that's as deep as the rabbit hole goes.
I love it.
But it also makes me nervous.
Good, it should.
Because the thing with self-hosting is you get to place this admin, but it also means you own the data, which means when there's an outage or a hardware failure, you're on the hook for that too.
Yeah, I'm not super concerned about an outage for my self-hosting thing, but I am certainly concerned about an outage of a self-hosted something for my production apps.
And when I said it makes me nervous, yeah, yeah, but the things that make me nervous are twofold.
The first thing that made me nervous would be just backup, backup and restore, or kind of losing access to it.
Like something that I think it takes a while, at least for me, it took a while to learn the lessons through some paper cuts, was, oh, there's a new version of this thing that I'm self-hosting.
How cool.
Let's see what it is.
Docker compose pull, Docker compose up, and then it won't start because there's some incompatible migration or something that I didn't run and I got to go read the docs and it says, oh, did you upgrade from version 1.6 to 1.8?
You can't do that.
You got to go to 1.7 and then 1.8.
I'm like, now I'm an admin.
But more concerned, like I had all this data, what if I can't get it to work on 1.8, but it's like a half database transition and then neither will run and now what do I do?
Well, the best answer to that are some of the primitives around things like ZFS and snapshots.
So there is this concept with, so ZFS, by the way, if you're not familiar, is the Zettabyte file system and it was born out of Sun Microsystems in the early 2000s, I believe.
It's now unfortunately owned by Oracle, but there is a project called OpenZFS which is dedicated to bringing it to the masses, to normal people.
There are still some weirdnesses around the licensing with ZFS, so it's not included by default in every single Linux distro, but it is included in things like Proxmox and Ubuntu and you can install it on Arch and NixOS and even Unraid, I think,
has ZFS these days.
And so the idea here is you're using what's called a copy-on-write file system.
Now some of these terms, I will admit, sound a little nerdy and they kind of are, but the idea behind copy-on-write is you take a snapshot at a moment in time and instead of the file system recording everything, you know,
transactionally forever, it will only record the delta from the previous snapshot.
And so what that means is that you can fork, you can basically fork file systems on disk and then you can mount the snapshot from three days ago as an actual file system and then restore the files that way.
So let's say your upgrade scenario, you could restore the database from just before you did the upgrade because as a good sysadmin, you are doing the hygiene of taking a snapshot before you do the risky thing, right?
You can automate all this stuff with scripts, right?
And I think there's a pragmatic angle here of how much time do you spend automating versus administering versus just going outside and touching grass.
But in the age of AI, there's really not, like it's, I installed Arch Linux last night downstairs on my gaming rig.
I was done, I decided I'm done with Windows for gaming.
And I thought, right, how far can Codex get me?
You know, the OpenAI version of Claude Code.
And I installed Arch myself and then I said, right, I want this desktop to look like this.
I want this kind of vibe.
I want like an Ubuntu kind of orange vibe.
I want Wayland compositor for my display and I want it to all log in seamlessly and blah, blah, blah, blah, blah.
I want these fonts.
I want my fan curves to be this.
And I just let it cook and maybe half an hour later I came back and my system was just configured.
Wow.
And it's amazing.
And you can do the same thing with a lot of like, like backup script.
You can literally say to Codex, these are my requirements.
I want you to take a snapshot before you do any kind of Docker compose operation.
And it will do it, whether it's via an alias or whatever.
I don't, the mechanics don't matter.
But the point is a lot of this stuff you can protect yourself from yourself now with so much less cognitive load than you used to have.
You can then configure it to backup offsite to all sorts of different places.
There's a, there's a wonderful service called ZFS.rent, which if you're not familiar is a way of, you basically send them a hard drive and they will put it into a server somewhere and you pay, I think it's $10 a month for that hard drive slot.
And then you can replicate all of your photos encrypted over the internet to ZFS.rent.
And it's, it's 10 bucks a month.
And then you've got that peace of mind.
That's wild.
I had no idea about this.
This is a really interesting way.
It's a great service.
I have several friends that use it.
Okay.
Yeah, that's really cool because backup is certainly one of them.
And that, that's not just export the data.
That's like making sure the app runs so that you can actually get to the data that's in the, you know, Postgres DB that's running in the little Docker composed network that it created when you ran it and so on, right?
There's plenty of other options with backups too.
Like Backblaze is a decent one, although they were in the news fairly recently for some, I don't know, they stopped backing up OneDrive folders and just did it silently.
And I don't know, you know how Reddit likes to go, go, go in on people.
So I don't know, Backblaze, they've been there for a long time.
They're a pretty reliable option.
You could also, if you want to do it fully self-hosted, Hetzner, you know, VPS provider, they have what's called a storage box, which you can usually bid on, which I think they cost somewhere typically between 30 to 50 euros a month.
So it's not the cheapest option, but if you want that level, that amount of storage offsite, it gets expensive.
That's just the reality of it.
When the business model is just storage and not farming your data and mining you for advertising stuff, it turns out storage is expensive.
Yeah, that's what you got to pay for it if you're not the product.
Yeah, but these things have enough storage that between you and a few mates, you could probably split it up into different ZFS datasets and replicate that way and, you know, split the bill a little bit as it were.
Are there self-hosting things that really stand out for you that you're a big fan of?
Like apps?
The real problem aspect is one for me, I think, that's critical to it, to the success.
You know, I talked about photos as being one example.
Home automation is another.
As you said, you'd have the home assistant guys on this podcast before.
We actually had Paulus on self-hosted a while ago and, you know, those guys, what they're doing with the Open Home Foundation is amazing.
Again, they're eschewing the status quo of five different apps for five different ecosystems and making everything talk to everything else and it's amazing.
And, you know, for me in this studio, for example, I've got one, two, three different ecosystems just for my studio lights and it's all brought under Home Assistant in one place.
And so for me, that solves a real problem.
So when Home Assistant is down, okay, it's not the biggest deal.
I have to walk around and turn three sets of lights off.
Okay, fine.
But when you start to add all of the different ecosystems in your house together, like your thermostats, you know, I have a mini split up there that I control through an ESP32 with like a serial connection.
I then have an Ecobee thermostat downstairs and so that's two ecosystems just for the climate in the house and then my garage doors are another ecosystem and so it continues.
And so solving real problems and bringing them back behind the firewall really is the idea for me.
Just, I don't know, it helps me sleep better at night but it's also in many cases just more convenient and less hassle.
The unification really that Home Assistant brings is really one of the biggest because everybody's got their janky little app that they think is so special, you know what I mean?
Yeah.
And I don't blame manufacturers necessarily for going that route because the way the internet was designed is it's, you know, I have something on this desk, right?
How would the manufacturer talk to it to control it through a smartphone app?
The only guarantee you've got is that a cloud server exists.
You can't control whether the user is necessarily on the same Wi-Fi and in fact, we've seen over the last 20 years as technology's evolved that I remember unboxing products 20 years ago that just the usability was just horrid.
You know, there are so many assumptions the manufacturers have to make about the environment it's going to land in, the Wi-Fi situation, the smartphone it's going to run on, blah, blah, blah.
And the only way you can really guarantee compatibility is to take control of that link and host the cloud component yourself and then have your users talk to your cloud and then have the cloud talk to the device.
Even though I can reach out and touch the light that's up here, it has to go to the cloud first to talk to it just because it guarantees that user experience.
I know.
My lights that I have for my streaming setup, they don't even have on, you can't physically turn them on.
The only way you can turn them on is over the network.
It's weird.
Yeah.
Welcome to 2026.
Exactly.
How did we accept that that is normal?
When did that become normal?
I don't know.
Now that I think about it, it should at least have an on button.
Oh, well.
Right.
I know.
So let's talk for a little while.
Now we've sort of set the stage, talked about some awesome apps and motivation and so on, but let's talk a bit about actually how to do it because I'm sure there's, I don't know, let me throw out, I'll just speculate.
I bet there's 30 to 40% of the people are like, oh yeah, I'll just SSH into my setup as well and then I know what to do from there.
And there's like maybe 20% of the people are like, I know what, I know I should SSH in there and the others are like, what is SSH?
Yeah.
So there's a lot of hesitation, I think, because you are kind of becoming a DevOps person.
Like you're running probably in Docker, maybe on Linux.
It's not on your main machine, most likely.
And then this whole backup sort of story that we talked about and restore.
Like talk to people about some of the tech.
It's inherently still a technical occupation and there isn't still really a great way around some of that.
Now we're on a Python show.
We understand that abstractions exist, right?
Python, of course, itself is an abstraction above something else.
There are lots of companies that will tell you and will try and sell you abstractions on top of this self-hosting layer that I'm talking about.
Well, Docker is an abstraction.
Linux is technically an abstraction, although let's just not talk machine code.
Let's just deal in, let's just treat Linux as the base.
Yeah.
Assume you have an OS.
Okay.
Yeah.
I think that's fair.
I agree.
You know, there are, I have a couple of, I don't know if you can see it in camera, probably not.
I've got a couple of Zima Board 2s on test, which they sent me for review for YouTube.
And they have a, they have something called Zima OS.
Z-I-M-A-OS.
And, you know, it's pretty good.
Like it's a, it's a one click.
You can, it's got a little app store in it, like you have on your phone and you can install a lot of these apps in one click onto Zima OS.
You can connect to USB hard drive and within maybe 20 minutes, half an hour, you've got a fairly functional setup.
Now, is it the most buttoned up, most secure bulletproof thing in the world?
No, almost certainly not.
But it gets you started.
And I think that is the real key is the best way to learn this stuff is to not think about it too much.
It's just to do it in a fairly low stakes way.
Don't try and switch from Spotify, for example, and convert your wife and your kids and everyone in your life to your self-hosted music streaming service overnight.
Softly, softly, slowly, slowly, catchy monkey.
You know, it's one of those things that you're probably going to need these things running in parallel for a little while until you feel comfortable enough that when you wake up at 7am and the streaming service that you've built in your basement doesn't work and the kid can't
watch their episode of cartoons before school or whatever, do you want to have to log in at 7am via SSH to your server and fix it?
No, I never do.
It turns out that's not something I want to do, but it's something I've had to do a few times because I've made mistakes either in not rotating logs properly or a disk filled up or there was a hardware failure or the list goes on and it's just, you know, you're trading some convenience
for ownership and the transaction is different and some of the cost there is in you and your time, but I will always advocate for people to learn these skills because I think in the modern world
they are such basic fundamental skills.
I wouldn't put them quite in the same bracket as learning how to do plumbing or electrical work or something like that, but this stuff, you know, everybody takes photos everybody listens to music and why should we continue to enrich the pockets
of Megacorps when we have the tools and the capabilities to do this stuff ourselves if we're just willing to put a few weekends aside and learn it?
It's a great point.
I guess start small.
These little...
Start small, yeah.
These home or these self-hosting OSes, I guess they sort of call it, it tries to bring kind of an app store experience to the self-hosting.
Another one that I would say is Coolify.
I don't know if you're familiar with Coolify.
Coolify's great.
Yeah, I'm sure.
Yeah, cool.
I did some stuff with Coolify for a while.
It's a little similar.
And you don't even need anything in your house with Coolify.
They will do hosted versions of these self-hosted apps if that even makes sense.
But essentially, you're still running the service, you're paying to run the service on their infrastructure.
And so all of the stuff we talked about around digital sovereignty and privacy and business models all remains true except for the fact the compute doesn't live behind your firewall.
It lives somewhere else.
Yeah, and you can even do things with Coolify such as get a server at Hetzner or DigitalOcean, create an account at Coolify, and then basically install their Daemon thing on your app.
And then through there, a little management.
You're managing multiple servers running.
I wanted to love Coolify and I think the idea is great.
I found that I ended up juggling so much more UI settings where I'm like, you know, if I just had a Docker Compose file, I could just define and replace or something.
Yeah.
Such is the life of an abstraction, right?
You trade certain complexities for certain decisions that the main, I mean, look at Apple, right?
We're always looking at macOS going, oh, I wish it, why are they doing it that way?
Well, you outsource that decision and the same is true with Coolify.
And any other abstraction that you choose as part of this stack, like even Docker, for example, is an abstraction, as I said, and you are making a certain set of, you're outsourcing a certain set of decisions to Docker in how things work.
It's just a reality of the world.
Yeah, that's a really good point.
That's, you know, you choose your abstraction.
So I bring it up because I do feel like people who are hesitant to do this kind of stuff, this is a really good option to get you started and get you comfortable and like, ah, what if I, maybe I could just run it myself after you're comfortable, you know, you work your way down until you, you know,
gain some of these skills.
What about Linux?
You know, one of the things that I think is both a hesitation for doing this at all, but also a hesitation to use Docker.
It's like, well, I could just do it on Linux.
At first you're like, well, I can't do Linux or Linux is intimidating to me.
Eventually you get that skill.
You're like, well, I could just put it on my machine.
Why do I need to actually use all this Docker complexity?
It is the repeatability for me, at least.
So what Docker brings to the table is a unified interface to running headless applications.
I can define using a Docker compose file, which is just a short YAML file in maybe 15 lines.
I can say, right, this is the name this container is going to get.
These are the exact directories this application is allowed to access on my system.
My photos app, for example, doesn't need access to my music library.
And so you reduce the blast radius of anything going wrong.
These are the ports it's allowed to access.
These are the kernel capabilities it's allowed to have if you want to get that deep.
You can turn off from a security perspective, you know, the photos app, for example, probably doesn't need a huge amount of kernel permissions to operate effectively.
Turn off the stuff it doesn't need.
And then that way, if there is a supply chain attack or a vulnerability exposed, the application itself becomes so much less of an attack vector because it literally physically has no access to certain bits of the kernel.
You know, when you keep going down the list of what Docker Compose can provide for you, within 15 lines you can define an entire application's deployment and then store it in GitHub completely securely, safely.
Obviously don't put secrets in GitHub, people.
Please do not do that.
But there are plenty of ways to sort of store secrets locally.
I think there's something called OpenBow, which is a local fork of HashiCorp Vault as a secret management.
You can use Bitwarden CLI, you can use 1Password.
There's many ways to store secrets.
Again, for me, it's like, why do we need things like Docker to exist?
It's because it's a universal language.
I can ship you a Docker Compose YAML or any developer assistant can ship a Compose file alongside their applications and I don't need to know anything about you or your application.
I just run Docker Compose pull up and suddenly all of it's like in the Kubernetes where it's like an operator, in the Windows where it's like an installer.
You're capturing all of the knowledge that you have about how to run your application successfully into this artifact which I then just pull down and deploy and run and it removes all of that complexity.
Beyond Docker, you mentioned a lot of the Docker Compose stuff.
You're right.
I'm going to define the networking, what things can talk to what.
I'm going to define the storage.
I'm going to define the visibility over the firewall sort of levels of things and it's great.
I just looked on my server.
I have three different versions of Postgres running from different apps that are like, oh no, we use Postgres 16.
Oh, we use 18 or whatever it is.
It's like, how are you going to manage that if you install more than just a handful of things?
They all want these different servers and what a hassle, right?
But because it's all contained within their own little network that they see, it's fine to run through because they all use the same port but they're not conflicting.
Yeah, that version of Postgres has no idea.
You could spin up 20 different Postgres 16s on the same server because all a container is really just process isolation in memory.
You want to think of it like that as a mental explanation?
All you're doing is taking your RAM and slicing it up into tiny little boxes and then placing that process inside that box.
It can't, that process then can't see anything outside of that box unless you give it specific and explicit permissions to do so.
And that's why containers have taken over the world if you ask me.
I agree.
I always thought that they were another level of complexity until I realized all the stuff you put in the Docker file is basically what you would have had to ad hoc type into your Linux machine anyway.
So you've got to know it anyway.
Yeah, you do.
Yeah.
I mean, the Docker file is basically just a bash script just with bells on.
Yeah, yeah.
You just put run or env or something in front of all the commands.
Let's come back to your comment on codex and AI because for as intimidating as these things are now, they're way less intimidating if you just have cloud code or codex and you say, hey, explain this line to me or I need this to happen.
Here's the file.
Why is it not happening or how do I make it happen?
That is an absolutely achievable thing.
even stuff like last week, my server was running slowly.
I didn't know why.
The CPU wasn't busy.
The RAM wasn't full.
I looked at things like disk pressure.
I looked at all the things I as a 15 year experience sysadmin knew where to look.
Didn't see anything.
And so then I had codex go and look at it via SSH.
I was running it on my laptop and I said, right, you have permission via SSH.
Go look at this server.
Tell me what's wrong.
And it turned out there was some spiking on certain NAND chips on the SSD when it was trying to write to certain sectors of the disk.
It was causing massive IO weight.
And I didn't catch that because it didn't make those writes during but codex ran overnight.
And whilst I was sleeping it was still doing the checks and still finding finding out what was going on.
And it turned out that the SSD, my boot SSD was on the verge of failing.
It just hadn't marked itself as failing in smart yet.
And it presented me this report, gave me all the diagnostics, it ran and yada yada.
I would never have caught that.
No.
Not until it failed.
And then I'd have caught it.
But now I have time to go out and research the correct SSD to replace it and not pay rush shipping and all of this stuff because the robots went out and basically did my job for me.
I mean, it's like, on the one hand, AI is one of these things of like, we're ushering in the very thing that's going to replace us as humanity.
But I don't see it that way.
Like, burying your head in the sand and saying, you know, vibe coded, slop this, that and the other.
Like, it's not, it's not really a mature take on it, in my opinion.
Yes, there's a lot of, there's a lot of slop out there.
Yes, there's a lot of, like, but we shouldn't be replacing art with AI.
Like, art fundamentally is a human endeavor and the reason it is valuable is because of the human effort that went into it.
You'll never replace that with a robot.
And, not even including the fact that everything that an AI does by its very nature is derivative of something that's actually being done before.
So, you're never getting anything truly new and truly revolutionary.
When it comes to, like, boring, menial tasks, like figuring out why my server's slow, have at it.
I don't want to, I don't really want to be debugging that all night.
Yeah.
The recent thing I did with DevOps, Docker, and AI was I wanted to do a new self-hosting app and I want to serve it out of the same server as some other ones, but I don't want them to interact with each other.
I don't even want them on the same network, but the NGINX front end has to be able to get to both of them.
So, I'm like, all right, log code, how do I create a second network that still the one container can see both of the networks, but this one can't see, you know what I mean?
Like, I'm like, how do I actually make that happen without breaking anything?
It just knows.
Yeah, it's like, this is what you do.
This is the commands you run to, like, create the external network and then here's the settings and all the compose files.
You restart them in this order so stuff doesn't break.
I'm like, wow, okay.
If you know just enough to be dangerous on a topic and you can guide it through the hallucinations that it does, it makes you incredibly powerful and so, for that reason, at least for the foreseeable future, I don't think it's going to replace, you know,
everybody.
There are for sure certain tasks and certain things that humans will be less required for and I think, you know, we're on the cusp of either the greatest change in humanity's labor since the Industrial Revolution or,
and the economics will bear this out one way or the other, you know, forces at play here much bigger than either of us, or it will just turn out to be inordinately too expensive to do that for a very long time and then the progress and investment will stop
and either a lot of very smart people are betting an awful lot of money and they're all wrong or there is actually something to this and we will see, I guess.
Yeah, I think it's being misused for a lot of stuff but I also think that there's areas where it's incredibly helpful and this computer stuff in general, programming, DevOps, amazing.
So we're getting short on time, Alex.
I feel like we've only scratched the surface like for real but let's talk about Tailscale.
I want to talk, I want to take one step back before we jump into Tailscale and just put out a warning.
This is something that really blew my mind when I saw it.
So when we're running our self-hosted apps, obviously we want to have security, limited access potentially.
You might be running them at home and so how do you access them?
There might be a bunch of funky networking things that people do but just as a quick PSA, I want to point out that, from here, other window, if you're using something like uncomplicated firewall in your Docker Compose file, you say,
listen on 00, just default, like this port maps to that port, that's effectively 0000, that port, like listen on all the things and you're using something like uncomplicated firewall or one of these other things that manipulates the IP tables.
Docker says, you know, Docker and UFW use firewall rules in ways that make them incompatible.
That is like, things like UFW don't block access to your Docker stuff so something else, something stronger like a cloud firewall or things like that, right?
Like on my servers, I have a at the cloud hosting level don't let anything access stuff but 80 and 443 or whatever and, you know, limited access to SSH.
But if I didn't have that and I just used UFW, that would be not ideal.
so let's talk about firewalls for a minute.
I think there's a couple of things at play.
One is you're hosting a public facing service like a website, right?
That clearly has to be on the public internet.
There's no way around that.
The whole purpose of a website or an API probably is to be hit remotely and provide a response.
But when we're talking about self-hosted infrastructure, the only customer is you, maybe your family, maybe a few friends.
And so the idea behind Tailscale is to bring that connectivity back to be a more personal level.
You know, our free tier, for example, at Tailscale has a six user limit.
It has unlimited devices.
And so the idea there is that you and your family all live in the same tail net.
You make sure that Tailscale is installed on your server in your basement or wherever it happens to be.
And it's installed on your phone.
It creates a wire guard tunnel underneath, encrypted, end-to-end.
And Tailscale makes a direct connection between those two devices with no middleman.
And so the way that Tailscale remains free is because we ask people, we give it away for free for a lot of it, but then we ask those people to champion us at work.
And we just crossed 30,000 paying customers just last week, I believe.
And so each of those paying customers, well, not all of them, but a large number came through that funnel of, well, this is awesome.
Why are we not using this at work?
Yeah.
So let me just sort of give the elevator pitch for people, I think, how cool this is.
One way to self-host is I've got this running on a spare computer of whatever sort, Mac Mini, small, NUC, whatever, on your home network.
You want access to it while it's traveling.
The not great way is just, well, let's just put that on the internet.
I'm going to open up a port on my router.
I mean, just think back to the LastPass thing, right?
How did LastPass get this huge takeover a few years ago?
The one of the devs was running a Plex server on the open internet and didn't patch it.
That got taken over.
They got lateral movement inside the network, gotten the access keys to LastPass, and down it goes, right?
So that's a bad example of self-hosting.
Better would be use something like Tailscale, never open any ports at all, but when you're on the Tailscale network, you see into the networks where it's running.
You see into your home network even when you're away, or you see into your server infrastructure even though zero ports are open.
And that to me is just kind of magical.
Yeah, if you want to learn more about it, I won't get into the specifics here, but there is a blog post called How Tailscale Works at tailscale.com.
I'll send Michael a link to put in the show notes.
And essentially, the magic there is we abused like stateful firewalls and how they work a little bit to do something called Nat traversal.
So the idea is that there weren't enough IPv4 addresses for every device in the world to get its own address and sit on the public internet.
And so we created this abstraction called Network Address Translation.
Each device sits behind a firewall and gets a local IP address.
You've probably seen the 192.168.whatever numbers.
That's a local IP address versus what you get like what'smyip.com or whatever.
And that'll give you a totally different IP address than what your laptop has with inside the Wi-Fi.
And so you've got to have something that's doing that translation between those two things and that's called NAT.
Then Tailscale punches through that NAT and makes a direct connection from your phone at the coffee shop over 5G through your residential firewall with no ports open to your server running under the stairs.
It's super seamless.
Yeah, it's super seamless.
So I use it for things like I have a local LLM running on my Mac.
Oh, yeah.
And then if I'm at the coffee shop, then I just make sure I'm on the Tailscale network and I can still run apps that talk to my OpenAI API over my self-hosted LLM as if it was running on my laptop, but it's not, right?
Yeah.
Remember what we said at the beginning of the show?
Like the rabbit hole goes deep and if you can think of a proprietary service, there's almost certainly a self-hosted alternative to it.
AI is another one that you can self-host.
So if you have a Mac Mini, we all heard about OpenClaw a few weeks ago, right?
You can put it on your gaming rig.
If you have an NVIDIA GPU in your gaming rig, you can use that for local AI.
I mean, the rabbit hole is, if you're a curious person, I apologize in advance if you've not looked into self-hosting because it will consume you for a little bit.
It's just how it goes.
It is definitely how it goes and it's very satisfying as you start to make progress in it.
Alex, I think that's it for our time.
Final thoughts for people who want to get started.
How would they get started?
Oh, how would they get, oh gosh, that's a broad question.
Hmm.
Well, if you want to learn more about building a server in and of itself, I run a website at perfectmediaserver.com where you can learn how to build basically a Linux server with some storage in it to replace Netflix or something.
I mean, I don't know.
Awesome self-hosting is a good place to get started.
There are dozens of YouTube guides.
Just type self-hosting in and just watch a couple of hours worth of YouTube and you'll get a pretty good idea.
And then from there, like I say, it's all about figuring out what problems you're trying to solve and then what shape that problem takes versus what your budget is, what your personal risk tolerances are and all that kind of stuff too.
There's a lot that goes into it, but if you want to reach out to me, alex.ktz.me, you can come find me.
I'm on Discord all over the place and I'll say hi.
I'd love to chat.
Yeah, awesome.
I'll certainly link to your connections on the website, on the show notes and I do want to give a shout out to Tailscale.
I think people should certainly consider it as part of the connectivity of all this stuff because it makes it so much simpler and so much safer.
Not a sponsored episode.
Hashtag not sponsored.
Yeah.
I'm just a corporate shill for free today.
For me, I found out about it a couple years ago and I'm like, this solves all the problems and I was just such a fan and so I just want to make, you know, I think it's really a way that things get quite simplified for it.
It was the same for me and I enjoyed it so much and I've been trying to solve this remote access problem as a self-hoster for, I didn't know it, but for 20 years I opened firewall ports to do remote desktop from school to my house when I was a teenager.
You know, like, I've been trying to solve this problem for a very long time and I installed Tailscale one weekend three years ago and was like, holy cow, this is amazing and I got a job here because I liked it so much.
Beautiful.
Well, I really appreciated you coming on the show.
Learned a lot.
Thanks for being here.
It was fun.
Yeah, thanks for having me.
Yeah, see you later.
This has been another episode of Talk Python To Me.
Thank you to our sponsors.
Be sure to check out what they're offering.
It really helps support the show.
Temporal is hosting their yearly conference, Temporal Replay.
Join your peers at Replay, the conference on orchestrating durable workflows and agents.
May 5 to 7 in San Francisco.
Visit talkpython.fm/temporal dash replay and use the code talkpython75, all one word, all caps, to save up to $449 on your ticket.
If you or your team needs to learn Python, we have over 270 hours of beginner and advanced courses on topics ranging from complete beginners to async code, Flask, Django, HTML, and even LLMs.
Best of all, there's no subscription in sight.
Browse the catalog at talkpython.fm.
And if you're not already subscribed to the show on your favorite podcast player, what are you waiting for?
Just search for Python in your podcast player.
We should be right at the top.
If you enjoy that geeky rap song, you can download the full track.
The link is actually in your podcast blur show notes.
This is your host, Michael Kennedy.
Thank you so much for listening.
I really appreciate it.
I'll see you next time.
Talk Python and me.
Can we be ready to roll?
Upgrading the code.
No fear of getting whole.
We tapped into that modern vibe overcame each storm.
Talk Python and me.
I think is the norm.