1
00:00:00,000 --> 00:00:04,160
Welcome back to the Deep Dive. Today we're getting into something really

2
00:00:04,160 --> 00:00:04,640
interesting,

3
00:00:04,640 --> 00:00:09,920
digital independence, basically taking control of your own tools. But first, a

4
00:00:09,920 --> 00:00:10,880
massive thank you to

5
00:00:10,880 --> 00:00:15,470
our sponsor, Safeserver.de. They handle software hosting and are great at

6
00:00:15,470 --> 00:00:16,720
supporting digital

7
00:00:16,720 --> 00:00:20,650
transformation. If you're thinking about taking charge of your digital stuff, check

8
00:00:20,650 --> 00:00:21,040
them out at

9
00:00:21,040 --> 00:00:27,070
www.safeserver.de. They help make these deep dives happen. So have you ever had

10
00:00:27,070 --> 00:00:28,000
that feeling, you

11
00:00:28,000 --> 00:00:31,190
know, where you're using digital tools maybe for remote work and you're just not

12
00:00:31,190 --> 00:00:31,840
sure where your

13
00:00:31,840 --> 00:00:34,880
data is or if the connection is going to hold up? Or maybe you just want something

14
00:00:34,880 --> 00:00:35,520
more secure,

15
00:00:35,520 --> 00:00:38,960
more flexible, perhaps even just helping out family with their computer without all

16
00:00:38,960 --> 00:00:39,120
the

17
00:00:39,120 --> 00:00:43,040
usual headaches. Well, if that sounds familiar, you're in the right place. Today we're

18
00:00:43,040 --> 00:00:43,680
diving

19
00:00:43,680 --> 00:00:49,200
into REST Desk. So REST Desk, it's an open source remote desktop app. Think of it

20
00:00:49,200 --> 00:00:50,160
as a real alternative

21
00:00:50,160 --> 00:00:54,780
to the big names, you know, TeamViewer, AnyDesk, Splashtop, and our mission today.

22
00:00:54,780 --> 00:00:55,680
Simple. We want

23
00:00:55,680 --> 00:00:59,760
to unpack what REST Desk is, why its self-hosting thing is, well, a bit of a game

24
00:00:59,760 --> 00:01:00,640
changer, and how

25
00:01:00,640 --> 00:01:04,910
it gives people and companies back control over their data, better security, and a

26
00:01:04,910 --> 00:01:06,320
ton of flexibility.

27
00:01:06,320 --> 00:01:10,320
We're aiming to make this super clear, a really easy entry point for anyone curious

28
00:01:10,320 --> 00:01:11,520
about this tool.

29
00:01:11,520 --> 00:01:16,080
So yeah, let's jump right in. Okay, let's unpack this. REST Desk gets called yet

30
00:01:16,080 --> 00:01:16,800
another remote

31
00:01:16,800 --> 00:01:21,260
desktop software, but the interesting part is that it's open source and it's

32
00:01:21,260 --> 00:01:22,720
written in REST,

33
00:01:22,720 --> 00:01:28,220
and they claim it works out of the box, no configuration required. That sounds,

34
00:01:28,220 --> 00:01:28,320
well,

35
00:01:28,320 --> 00:01:33,440
almost too easy. Yeah, yeah. For someone maybe not super technical with servers,

36
00:01:33,440 --> 00:01:38,240
how easy is it to get started? Is it really click and go, or are there still some

37
00:01:38,240 --> 00:01:38,400
things

38
00:01:38,400 --> 00:01:42,430
you need to understand? That's a really good question because, you know, it hits on

39
00:01:42,430 --> 00:01:42,800
a real

40
00:01:42,800 --> 00:01:47,430
pain point people have with standard software as a service, SaaS platforms. Think

41
00:01:47,430 --> 00:01:47,760
about those

42
00:01:47,760 --> 00:01:51,370
subscription services. Sometimes the performance is shaky, right? You don't really

43
00:01:51,370 --> 00:01:52,160
know what's going

44
00:01:52,160 --> 00:01:56,270
on behind the curtain. And there's always that nagging worry about data security.

45
00:01:56,270 --> 00:01:57,040
Russdesk kind

46
00:01:57,040 --> 00:02:01,040
of flips that by focusing on self-hosting. And yeah, they've worked hard to make it

47
00:02:01,040 --> 00:02:01,440
surprisingly

48
00:02:01,440 --> 00:02:05,380
simple for the power it gives you. If you step back, self-hosting has some major

49
00:02:05,380 --> 00:02:06,480
perks. First up,

50
00:02:06,480 --> 00:02:11,500
data sovereignty. Okay, data sovereignty. Yeah, sounds important. It really is. It's

51
00:02:11,500 --> 00:02:11,920
not just

52
00:02:11,920 --> 00:02:16,300
jargon. It's about control and meeting regulations. Let's say you run a small

53
00:02:16,300 --> 00:02:17,280
business, maybe

54
00:02:17,280 --> 00:02:22,230
accounting. With a typical tool, your client's financial data might end up on

55
00:02:22,230 --> 00:02:23,520
servers. Who knows

56
00:02:23,520 --> 00:02:28,240
where? Different country, maybe. That could be a regulatory nightmare. Self-hosting.

57
00:02:28,240 --> 00:02:29,520
Your data stays

58
00:02:29,520 --> 00:02:33,670
on your servers, under your roof, basically. Makes audits easier, removes that

59
00:02:33,670 --> 00:02:34,640
uncertainty.

60
00:02:34,640 --> 00:02:40,240
Okay, so you physically control where the sensitive stuff lives. Makes sense.

61
00:02:40,240 --> 00:02:41,040
Exactly. And

62
00:02:41,040 --> 00:02:46,400
that leads right into point two. Enhanced security. When you deploy Russdesk on-premise

63
00:02:46,400 --> 00:02:46,880
on your own

64
00:02:46,880 --> 00:02:51,030
computers or servers, your data isn't passing through some third-party company

65
00:02:51,030 --> 00:02:51,840
system. Right.

66
00:02:51,840 --> 00:02:55,870
Cuts out the middleman. Precisely. It reduces the attack surface, strengthens your

67
00:02:55,870 --> 00:02:56,240
security,

68
00:02:56,240 --> 00:02:59,510
because you control the whole path. Then there's performance and reliability. When

69
00:02:59,510 --> 00:02:59,840
you own the

70
00:02:59,840 --> 00:03:03,080
hardware, you manage the resources. You're not sharing bandwidth or server power

71
00:03:03,080 --> 00:03:03,760
with thousands

72
00:03:03,760 --> 00:03:08,630
of other users, like on a big commercial service. So better uptime, smoother

73
00:03:08,630 --> 00:03:09,920
performance, less of

74
00:03:09,920 --> 00:03:14,210
that frustrating lag or unexpected downtime. You're in control. That direct control

75
00:03:14,210 --> 00:03:15,040
seems key.

76
00:03:15,040 --> 00:03:20,070
Absolutely. And it also means incredible flexibility and customization. Self-hosting

77
00:03:20,070 --> 00:03:20,640
lets you tweak

78
00:03:20,640 --> 00:03:25,490
Rust Desk for exactly what you need. They even have this custom client feature. Oh,

79
00:03:25,490 --> 00:03:26,000
what's that?

80
00:03:26,000 --> 00:03:31,070
It lets you brand the client app, put your own company name, logo, icon on it. That's

81
00:03:31,070 --> 00:03:31,440
a level of

82
00:03:31,440 --> 00:03:35,050
personalization you just don't get from off-the-shelf tools. And while the basic

83
00:03:35,050 --> 00:03:36,080
setup is simple, if you

84
00:03:36,080 --> 00:03:41,590
want to dive deeper, there are like over 90 configuration options. Wow. Okay. So

85
00:03:41,590 --> 00:03:42,480
simple start,

86
00:03:42,480 --> 00:03:47,570
but deep customization if needed. Exactly. You can fine-tune access controls,

87
00:03:47,570 --> 00:03:48,160
optimize bandwidth

88
00:03:48,160 --> 00:03:52,350
for video, all sorts of things. Real granular control. And yes, back to your

89
00:03:52,350 --> 00:03:53,440
original question,

90
00:03:53,440 --> 00:03:58,080
it really is designed for ease of deployment. It sounds complex, maybe, setting up

91
00:03:58,080 --> 00:03:58,560
a server,

92
00:03:58,560 --> 00:04:02,700
but Rust Desk has built-in features to help with network configuration and server

93
00:04:02,700 --> 00:04:03,680
setup. For anyone

94
00:04:03,680 --> 00:04:07,120
comfortable with a command line, the Docker setup is honestly super straightforward.

95
00:04:07,120 --> 00:04:07,680
It's basically

96
00:04:07,680 --> 00:04:12,250
three quick commands, install Docker, download a file, run Docker, compose up. Boom,

97
00:04:12,250 --> 00:04:12,880
your server's

98
00:04:12,880 --> 00:04:17,360
running. Okay, three commands. That does sound accessible. So, data sovereignty,

99
00:04:17,360 --> 00:04:19,200
security,

100
00:04:19,200 --> 00:04:24,800
performance. It sounds really appealing, especially if you felt kind of trapped by

101
00:04:24,800 --> 00:04:26,000
cloud services.

102
00:04:26,000 --> 00:04:30,400
But what about the flip side? What's the learning curve moving from a simple SaaS

103
00:04:30,400 --> 00:04:31,280
tool to

104
00:04:31,280 --> 00:04:34,880
self-hosting? Is it really just those Docker commands, or do you need to think

105
00:04:34,880 --> 00:04:35,920
about server

106
00:04:35,920 --> 00:04:39,650
updates and maintenance that the cloud provider usually handles? That is a crucial

107
00:04:39,650 --> 00:04:40,480
point. Getting

108
00:04:40,480 --> 00:04:46,160
started is easy, yes. But self-hosting does mean taking on responsibility. You gain

109
00:04:46,160 --> 00:04:46,800
control,

110
00:04:46,800 --> 00:04:50,080
but you also need to maintain that server environment updates, security patches,

111
00:04:50,080 --> 00:04:50,400
that sort

112
00:04:50,400 --> 00:04:54,100
of thing. Right, it's not just set and forget forever. Not entirely, no. But the

113
00:04:54,100 --> 00:04:54,400
Rust Desk

114
00:04:54,400 --> 00:04:57,620
community is really active, and the documentation is pretty good. They try to make

115
00:04:57,620 --> 00:04:58,320
that transition

116
00:04:58,320 --> 00:05:02,330
smooth. And this actually brings up an important point that developers make. Like

117
00:05:02,330 --> 00:05:03,280
any powerful

118
00:05:03,280 --> 00:05:07,380
tool, you need to use it responsibly. They're very clear. They don't support or

119
00:05:07,380 --> 00:05:08,160
condone any

120
00:05:08,160 --> 00:05:12,650
unethical or illegal use. Things like unauthorized access, spying, anything like

121
00:05:12,650 --> 00:05:13,680
that. It's strictly

122
00:05:13,680 --> 00:05:18,120
against their guidelines. The tool is meant for legitimate, secure, controlled

123
00:05:18,120 --> 00:05:19,200
remote access.

124
00:05:19,200 --> 00:05:23,810
Good to know. They state that clearly. Okay, so we've talked tech benefits, but who's

125
00:05:23,810 --> 00:05:24,080
actually

126
00:05:24,080 --> 00:05:29,220
using this day-to-day? Who benefits most from this level of control? We saw some

127
00:05:29,220 --> 00:05:30,000
survey data.

128
00:05:30,000 --> 00:05:34,640
Over a thousand cell posters responded, and it shows a really diverse range of uses.

129
00:05:34,640 --> 00:05:35,600
About 37%

130
00:05:35,600 --> 00:05:40,150
use it for IT support, which makes sense, right? If you're fixing someone's

131
00:05:40,150 --> 00:05:41,280
computer remotely,

132
00:05:41,280 --> 00:05:46,660
you need a rock-solid, secure connection. No drops, no data leaks. Rust Desk

133
00:05:46,660 --> 00:05:47,680
provides that direct

134
00:05:47,680 --> 00:05:52,080
link. Yeah, critical for support roles. And 25% are using it for IT administration,

135
00:05:52,080 --> 00:05:53,280
managing systems.

136
00:05:53,280 --> 00:05:58,160
Another 29% for remote work, which is huge for everyone now. And then about 9% are

137
00:05:58,160 --> 00:05:58,880
in industrial

138
00:05:58,880 --> 00:06:02,570
settings or other specialized areas. So it's quite versatile. Maybe you listening

139
00:06:02,570 --> 00:06:03,040
fit into one of

140
00:06:03,040 --> 00:06:06,400
those, or maybe it sparks an idea for a problem you could solve with this. And the

141
00:06:06,400 --> 00:06:06,960
tech underneath

142
00:06:06,960 --> 00:06:11,360
is definitely built for that kind of broad use. First off, multi-platform support

143
00:06:11,360 --> 00:06:12,320
is key. It runs

144
00:06:12,320 --> 00:06:18,680
smoothly on Windows, MacOs, Linux, even Android. Oh, Android too. Nice. Yeah, so

145
00:06:18,680 --> 00:06:19,280
you can connect

146
00:06:19,280 --> 00:06:23,280
from pretty much any device to any other device. Essential these days with everyone

147
00:06:23,280 --> 00:06:23,840
using different

148
00:06:23,840 --> 00:06:28,650
things. And something really cool is the web client. A web client. So access from a

149
00:06:28,650 --> 00:06:29,440
browser.

150
00:06:29,440 --> 00:06:33,950
Exactly. You can host it yourself on your own server using your own domain name.

151
00:06:33,950 --> 00:06:34,400
Makes access

152
00:06:34,400 --> 00:06:38,400
super flexible. No need to install the app everywhere. And they're working on a new

153
00:06:38,400 --> 00:06:38,720
version,

154
00:06:38,720 --> 00:06:43,560
a V2 preview, that promises things like better video codecs, international keyboard

155
00:06:43,560 --> 00:06:44,240
support,

156
00:06:44,240 --> 00:06:48,370
clipboard sharing, even file transfer. That's getting really comprehensive for a

157
00:06:48,370 --> 00:06:48,880
web-based

158
00:06:48,880 --> 00:06:53,090
solution. Wow. File transfer directly in the browser client, self-hosted. That's

159
00:06:53,090 --> 00:06:53,520
powerful.

160
00:06:53,520 --> 00:06:58,370
It really is. And just briefly, under the hood, like we said, it's mostly written

161
00:06:58,370 --> 00:06:58,880
in Rust.

162
00:06:58,880 --> 00:07:03,280
Which is known for security and speed, right? Exactly. Rust helps prevent a lot of

163
00:07:03,280 --> 00:07:03,600
common

164
00:07:03,600 --> 00:07:08,170
security bugs, which is vital for remote access software. For the interface, the

165
00:07:08,170 --> 00:07:08,880
desktop apps

166
00:07:08,880 --> 00:07:13,300
use either Flutter or CIDR. And it's built in a modular way. There are separate

167
00:07:13,300 --> 00:07:14,160
bits for screen

168
00:07:14,160 --> 00:07:20,400
capture, LibScrap, keyboard mouse control, LibCentigo, and the server parts, server,

169
00:07:20,400 --> 00:07:25,390
handling audio, video, etc. So it's not just one big monolithic thing. Right. And

170
00:07:25,390 --> 00:07:26,320
that modularity

171
00:07:26,320 --> 00:07:32,560
helps with development speed, optimizing specific parts, and overall stability. All

172
00:07:32,560 --> 00:07:33,360
crucial for a

173
00:07:33,360 --> 00:07:38,330
tool you rely on for access. And fundamentally, it's truly open source. It uses the

174
00:07:38,330 --> 00:07:39,760
AGPL 3.0 license,

175
00:07:39,760 --> 00:07:43,770
which means total transparency. You could look at every line of code, and if you

176
00:07:43,770 --> 00:07:44,640
modify it and share

177
00:07:44,640 --> 00:07:48,670
it, you have to share your changes too. Ah, so it fosters collaboration and keeps

178
00:07:48,670 --> 00:07:49,520
things open.

179
00:07:49,520 --> 00:07:53,790
Precisely. It builds a trustworthy ecosystem where the community helps ensure it

180
00:07:53,790 --> 00:07:54,880
stays secure

181
00:07:54,880 --> 00:07:58,660
and keeps getting better. That's fantastic. It really feels like, you know, you're

182
00:07:58,660 --> 00:07:58,880
getting

183
00:07:58,880 --> 00:08:02,880
something built by a community, not just a black box from a corporation. It's built

184
00:08:02,880 --> 00:08:03,440
in public. You

185
00:08:03,440 --> 00:08:06,680
can see the whole process. And that community impact is huge. The numbers are

186
00:08:06,680 --> 00:08:07,600
pretty staggering,

187
00:08:07,600 --> 00:08:12,920
actually. Rust Desk has over 10 million client downloads, over 1 million Docker

188
00:08:12,920 --> 00:08:13,840
downloads.

189
00:08:13,840 --> 00:08:18,290
That's people setting up their own servers. A million self-hosted servers. Wow.

190
00:08:18,290 --> 00:08:18,960
Yeah. And

191
00:08:18,960 --> 00:08:24,000
maybe even more telling. They estimate over 3 million alive devices actively using

192
00:08:24,000 --> 00:08:24,640
it. These

193
00:08:24,640 --> 00:08:29,140
aren't just downloads. People are using this daily. Shows it's reliable. And if you

194
00:08:29,140 --> 00:08:30,000
look at GitHub,

195
00:08:30,000 --> 00:08:36,800
the community engagement is massive. Over 91,000 stars, 13,000 forks. Huge numbers

196
00:08:36,800 --> 00:08:37,440
for an open

197
00:08:37,440 --> 00:08:41,690
source project. Absolutely. Yeah. And 303 contributors, people actually writing

198
00:08:41,690 --> 00:08:42,000
code,

199
00:08:42,000 --> 00:08:46,400
plus over 22,000 community members active on various platforms. Yeah. It really

200
00:08:46,400 --> 00:08:46,880
highlights

201
00:08:46,880 --> 00:08:51,370
that built-in public idea. Someone posts a feature request. Maybe someone else

202
00:08:51,370 --> 00:08:52,000
across the world

203
00:08:52,000 --> 00:08:55,700
implements it. It's dynamic. That's the power of open source right there. Totally.

204
00:08:55,700 --> 00:08:56,320
And its global

205
00:08:56,320 --> 00:08:59,770
reach is clear too. It supports 45 languages. That's thanks to community

206
00:08:59,770 --> 00:09:00,720
translation efforts.

207
00:09:00,720 --> 00:09:03,920
If you want to connect, they're active on Discord, Twitter, Reddit, YouTube, and of

208
00:09:03,920 --> 00:09:04,880
course GitHub.

209
00:09:04,880 --> 00:09:08,540
Lots of places to get involved or find help. Definitely. And it's constantly

210
00:09:08,540 --> 00:09:09,280
evolving.

211
00:09:09,280 --> 00:09:14,160
Just recently, the enhanced access controls and the pro server version user level

212
00:09:14,160 --> 00:09:14,880
permissions,

213
00:09:14,880 --> 00:09:19,360
device groups, more granular control. They're also focused on keeping it working

214
00:09:19,360 --> 00:09:19,920
for people,

215
00:09:19,920 --> 00:09:24,400
like finding workarounds to keep it running on older systems like Windows 7, even

216
00:09:24,400 --> 00:09:25,040
as underlying

217
00:09:25,040 --> 00:09:29,270
tech like Flutter changes. It shows dedication to the user base. What a journey

218
00:09:29,270 --> 00:09:30,640
through Rust Desk.

219
00:09:30,640 --> 00:09:35,970
We've really seen how this open source approach delivers exceptional control, solid

220
00:09:35,970 --> 00:09:36,640
security,

221
00:09:36,640 --> 00:09:41,280
and real flexibility, especially with self-hosting. It's definitely a strong contender

222
00:09:41,280 --> 00:09:41,680
against the

223
00:09:41,680 --> 00:09:44,910
usual suspects, putting you back in the driver's seat with your data and

224
00:09:44,910 --> 00:09:46,240
connections. And thinking

225
00:09:46,240 --> 00:09:50,500
bigger picture for a moment, it leads to a question maybe for you to mull over. If

226
00:09:50,500 --> 00:09:51,200
self-hosting can do

227
00:09:51,200 --> 00:09:56,470
this for remote access, give back data sovereignty, allow deep customization, where

228
00:09:56,470 --> 00:09:56,960
else in your

229
00:09:56,960 --> 00:10:01,930
digital life, or maybe your work, could you benefit from taking back control? From

230
00:10:01,930 --> 00:10:02,720
exploring open

231
00:10:02,720 --> 00:10:05,760
source alternatives, what are the broader possibilities when we think about

232
00:10:05,760 --> 00:10:06,560
decentralization

233
00:10:06,560 --> 00:10:10,390
and user empowerment in tech? Something to think about. A really great question to

234
00:10:10,390 --> 00:10:11,200
end on, food for

235
00:10:11,200 --> 00:10:16,880
thought, definitely. And one last massive thank you to our sponsor, safeserver.de.

236
00:10:16,880 --> 00:10:17,360
They're the ones to

237
00:10:17,360 --> 00:10:21,400
check out for software hosting and help with your digital transformation. Find them

238
00:10:21,400 --> 00:10:21,600
at

239
00:10:21,600 --> 00:10:27,200
www.safeserver.de. That wraps up this deep dive. Thanks so much for tuning in and

240
00:10:27,200 --> 00:10:27,680
we'll catch you