1
00:00:00,000 --> 00:00:02,000
Welcome back to the deep dive.

2
00:00:02,000 --> 00:00:05,680
So today we're looking at, well, it's more than just a piece of technology.

3
00:00:05,680 --> 00:00:10,160
We're really examining kind of declaration of digital independence.

4
00:00:10,160 --> 00:00:14,880
We're diving into how you can fundamentally reshape your infrastructure

5
00:00:14,880 --> 00:00:20,000
to get total control over your real time alerts and your messaging.

6
00:00:20,000 --> 00:00:23,240
Yeah, I mean, have you ever tried to automate a critical alert

7
00:00:23,240 --> 00:00:25,880
maybe from a server or just a home script?

8
00:00:25,880 --> 00:00:27,360
And then you find the commercial service

9
00:00:27,360 --> 00:00:29,840
you're relying on is, I don't know, rate limiting you.

10
00:00:29,840 --> 00:00:34,320
Or even worse, it's gathering metadata about when your systems are under stress.

11
00:00:34,320 --> 00:00:37,840
Exactly. That frustration that the lack of autonomy is precisely

12
00:00:37,840 --> 00:00:41,240
what this project we're exploring today called Goatify was built to solve.

13
00:00:41,240 --> 00:00:44,720
It's just a really elegant open source tool for self-hosted messaging.

14
00:00:44,720 --> 00:00:47,560
And our mission today, especially for the learner, is to, you know,

15
00:00:47,560 --> 00:00:50,960
cut through the jargon and show you the straightforward elegance of Goatify.

16
00:00:50,960 --> 00:00:56,000
It's a simple, reliable, self-hosted solution to two pretty big problems.

17
00:00:56,000 --> 00:01:00,960
Information overload and vendor lock-in with commercial push services.

18
00:01:00,960 --> 00:01:03,800
So we're aiming for digital autonomy that's actually achievable.

19
00:01:03,800 --> 00:01:07,280
Yeah, even for someone who's just starting out on their self-hosting journey.

20
00:01:07,280 --> 00:01:09,360
And the promise is pretty powerful.

21
00:01:09,360 --> 00:01:14,000
A straightforward, reliable way to push messages and get instant notifications

22
00:01:14,000 --> 00:01:17,960
from all your services, all your scripts, all your devices.

23
00:01:17,960 --> 00:01:20,720
And it's all managed by you on hardware you control.

24
00:01:20,720 --> 00:01:25,220
It's about being informed, but, you know, instantly without compromising your

25
00:01:25,220 --> 00:01:25,720
privacy.

26
00:01:25,720 --> 00:01:29,760
And without relying on some centralized corporate gatekeepers.

27
00:01:29,760 --> 00:01:32,280
Right. And of course, taking control of this kind of infrastructure

28
00:01:32,280 --> 00:01:36,520
requires some reliable support, which brings us to our partner for this deep dive.

29
00:01:36,520 --> 00:01:39,960
We want to thank the supporter of this deep dive, Safe Server.

30
00:01:39,960 --> 00:01:43,280
Safe Server handles the hosting of this type of self-hosted software

31
00:01:43,280 --> 00:01:46,360
and actively supports you in your digital transformation,

32
00:01:46,360 --> 00:01:49,480
which makes that jump to autonomy a whole lot simpler.

33
00:01:49,480 --> 00:01:54,960
You can find more information about their services at www.safeserver.de.

34
00:01:54,960 --> 00:01:57,800
Okay, so let's unpack this. Let's start with the genesis, the why.

35
00:01:57,800 --> 00:02:01,760
I mean, why did the creators feel the need to build Goatify from the ground up?

36
00:02:01,760 --> 00:02:05,160
You know, when services like email or even commercial push notifications

37
00:02:05,160 --> 00:02:08,080
were already out there, what problem was left unsolved?

38
00:02:08,080 --> 00:02:11,360
Well, what's fascinating here is that the motivation wasn't really

39
00:02:11,360 --> 00:02:13,680
about inventing some totally new concept.

40
00:02:13,680 --> 00:02:18,200
It was more about providing a rock solid

41
00:02:18,200 --> 00:02:21,360
community maintained implementation of an old one.

42
00:02:21,360 --> 00:02:24,520
They saw a pretty glaring gap in the open source world.

43
00:02:24,520 --> 00:02:28,320
They needed a, and I'm quoting here, simple server for sending

44
00:02:28,320 --> 00:02:31,320
and receiving messages in real time per WebSocket.

45
00:02:31,320 --> 00:02:33,800
And the source material specifically mentions that a lot of the existing

46
00:02:33,800 --> 00:02:36,960
open source notification projects were just abandoned.

47
00:02:36,960 --> 00:02:40,760
Right. And imagine building a crucial piece of your infrastructure

48
00:02:40,760 --> 00:02:44,240
on a platform that just suddenly stops getting maintained.

49
00:02:44,240 --> 00:02:46,440
It introduces this fragility.

50
00:02:46,440 --> 00:02:50,440
So the creators had this core non-negotiable requirement.

51
00:02:50,440 --> 00:02:53,600
The tool had to be something that can be self-hosted and,

52
00:02:53,600 --> 00:02:55,280
you know, maintained robustly.

53
00:02:55,280 --> 00:02:59,040
And that need for self-hosting, that's the strategic pivot, isn't it?

54
00:02:59,040 --> 00:03:01,680
Because when you look at the landscape, there are, as the source says,

55
00:03:01,680 --> 00:03:04,480
many free and commercial push services out there.

56
00:03:04,480 --> 00:03:07,080
But those services, they inherently know a massive amount

57
00:03:07,080 --> 00:03:09,440
about the metadata of your operational environment.

58
00:03:09,440 --> 00:03:12,600
Exactly. The core philosophical benefit,

59
00:03:12,600 --> 00:03:16,440
which is also the practical benefit for you, is made really explicit.

60
00:03:16,440 --> 00:03:18,920
You control your data. Think about it.

61
00:03:18,920 --> 00:03:22,240
When you route all your system alerts from backup complete

62
00:03:22,240 --> 00:03:26,080
to server temperature critical through a third-party service,

63
00:03:26,080 --> 00:03:28,480
well, that third party collects data.

64
00:03:28,480 --> 00:03:31,520
Data on when you're busiest, how often your systems are alerting.

65
00:03:31,520 --> 00:03:33,800
And what level of criticality they operate at.

66
00:03:33,800 --> 00:03:36,760
That metadata trail can be incredibly revealing.

67
00:03:36,760 --> 00:03:39,800
The Goatify just eliminates that exposure entirely.

68
00:03:39,800 --> 00:03:42,720
It means the only entity that knows your server is panicking

69
00:03:42,720 --> 00:03:46,000
at three in the morning is, well, you.

70
00:03:46,000 --> 00:03:48,720
It fundamentally alters your privacy posture.

71
00:03:48,720 --> 00:03:50,160
You aren't just gaining convenience.

72
00:03:50,160 --> 00:03:53,640
You are literally removing a layer of trust and risk.

73
00:03:53,640 --> 00:03:57,120
So, yeah, the value prop is simplicity, reliability, and total control.

74
00:03:57,120 --> 00:04:00,040
So if that's the why, let's really dig into the what.

75
00:04:00,040 --> 00:04:01,920
How does this system actually work?

76
00:04:01,920 --> 00:04:03,320
What's the engine under the hood?

77
00:04:03,320 --> 00:04:06,040
OK, so the heart of the project is the Goatify server.

78
00:04:06,040 --> 00:04:08,720
And it's built around, let's say, three functional pillars

79
00:04:08,720 --> 00:04:10,280
that all need to talk to each other.

80
00:04:10,280 --> 00:04:11,440
Great. What's the first pillar?

81
00:04:11,440 --> 00:04:13,680
Pillar one is sending messages.

82
00:04:13,680 --> 00:04:16,120
This is handled through a REST API.

83
00:04:16,120 --> 00:04:17,440
And we should probably break that down.

84
00:04:17,440 --> 00:04:20,800
A REST API is just a perfectly standardized web address

85
00:04:20,800 --> 00:04:22,200
you can send information to.

86
00:04:22,200 --> 00:04:23,240
That's a great way to put it.

87
00:04:23,240 --> 00:04:24,800
For a beginner, this is crucial.

88
00:04:24,800 --> 00:04:28,360
It means any modern programming language, any shell script.

89
00:04:28,360 --> 00:04:31,920
I mean, any web hook can push a message to Goatify

90
00:04:31,920 --> 00:04:34,200
just by sending a structured web request.

91
00:04:34,200 --> 00:04:36,840
So if I have a simple script that finishes a task,

92
00:04:36,840 --> 00:04:39,400
I can just use a quick command, like cURL,

93
00:04:39,400 --> 00:04:42,200
to hit that API endpoint, push the message,

94
00:04:42,200 --> 00:04:43,920
and Goatify just captures it.

95
00:04:43,920 --> 00:04:44,800
Precisely.

96
00:04:44,800 --> 00:04:48,120
The REST API is the standardized door for information

97
00:04:48,120 --> 00:04:49,200
entering the system.

98
00:04:49,200 --> 00:04:50,760
OK, so that's getting messages in.

99
00:04:50,760 --> 00:04:51,960
What about getting them out?

100
00:04:51,960 --> 00:04:54,520
That's pillar two, receiving messages.

101
00:04:54,520 --> 00:04:56,600
And this is the real-time secret sauce.

102
00:04:56,600 --> 00:04:58,400
It's handled via WebSocket.

103
00:04:58,400 --> 00:04:59,440
WebSocket.

104
00:04:59,440 --> 00:05:02,240
So if the REST API is like placing an order at a counter?

105
00:05:02,240 --> 00:05:05,080
Then the WebSocket is like having a direct, dedicated,

106
00:05:05,080 --> 00:05:07,200
persistent telephone line that's always

107
00:05:07,200 --> 00:05:09,840
open between your server and your client device,

108
00:05:09,840 --> 00:05:10,640
like your phone.

109
00:05:10,640 --> 00:05:13,520
And that persistence is so important, isn't it?

110
00:05:13,520 --> 00:05:16,400
I mean, why not just have the mobile app constantly check

111
00:05:16,400 --> 00:05:17,800
the server every minute?

112
00:05:17,800 --> 00:05:18,640
That process.

113
00:05:18,640 --> 00:05:19,240
Polling, right?

114
00:05:19,240 --> 00:05:20,520
Yeah, polling is slow.

115
00:05:20,520 --> 00:05:23,720
And it's incredibly inefficient on the battery and the network.

116
00:05:23,720 --> 00:05:26,240
For a true instant notification, you

117
00:05:26,240 --> 00:05:29,400
really need that two-way persistent connection

118
00:05:29,400 --> 00:05:31,120
that a WebSocket provides.

119
00:05:31,120 --> 00:05:34,680
When the server gets that message via the REST API, boom,

120
00:05:34,680 --> 00:05:37,520
it immediately sends it down the already open WebSocket

121
00:05:37,520 --> 00:05:38,160
connection.

122
00:05:38,160 --> 00:05:39,200
It's instant.

123
00:05:39,200 --> 00:05:41,560
That does raise a critical question for mobile users,

124
00:05:41,560 --> 00:05:42,400
though.

125
00:05:42,400 --> 00:05:44,460
If that connection is persistent,

126
00:05:44,460 --> 00:05:46,300
the telephone line is always open.

127
00:05:46,300 --> 00:05:48,600
Doesn't that create a huge battery drain?

128
00:05:48,600 --> 00:05:51,120
That's why people often rely on native Google or Apple

129
00:05:51,120 --> 00:05:51,920
services.

130
00:05:51,920 --> 00:05:52,920
That's a great question.

131
00:05:52,920 --> 00:05:55,280
And it's where the advantage of using a modern lightweight

132
00:05:55,280 --> 00:05:58,360
protocol comes in, and also the fact it's written in Go.

133
00:05:58,360 --> 00:06:00,760
While any persistent connection will use more power

134
00:06:00,760 --> 00:06:03,760
than a sleeping one, the overhead is minimized.

135
00:06:03,760 --> 00:06:06,080
The mobile clients are designed to manage that connection

136
00:06:06,080 --> 00:06:09,160
efficiently, so the power drain is focused purely

137
00:06:09,160 --> 00:06:10,580
on maintaining that link.

138
00:06:10,580 --> 00:06:11,240
That makes sense.

139
00:06:11,240 --> 00:06:12,200
It's a key distinction.

140
00:06:12,200 --> 00:06:14,100
And then there's pillar three, the admin side.

141
00:06:14,100 --> 00:06:14,600
Right.

142
00:06:14,600 --> 00:06:16,640
The third function is just management.

143
00:06:16,640 --> 00:06:18,640
This is straightforward but essential.

144
00:06:18,640 --> 00:06:21,800
Creating users, generating specific API tokens

145
00:06:21,800 --> 00:06:24,040
for your different applications, and controlling

146
00:06:24,040 --> 00:06:25,480
which clients can connect.

147
00:06:25,480 --> 00:06:27,360
And the great news is, you don't have

148
00:06:27,360 --> 00:06:29,360
to live on the command line to do all this.

149
00:06:29,360 --> 00:06:30,640
No, not at all.

150
00:06:30,640 --> 00:06:35,000
The server, quoting again, includes a sleek web ooey.

151
00:06:35,000 --> 00:06:37,440
For anyone new to this, that web interface

152
00:06:37,440 --> 00:06:39,000
is your control panel.

153
00:06:39,000 --> 00:06:41,140
It makes management infinitely easier.

154
00:06:41,140 --> 00:06:44,440
And you mentioned it's written in Go or Golang.

155
00:06:44,440 --> 00:06:47,400
Why does that matter for someone just getting started?

156
00:06:47,400 --> 00:06:49,560
Well, Go is famous for its stability.

157
00:06:49,560 --> 00:06:51,040
It's really performant.

158
00:06:51,040 --> 00:06:53,880
And it has an incredibly small memory footprint.

159
00:06:53,880 --> 00:06:56,500
For a notification server that needs to run 247

160
00:06:56,500 --> 00:07:00,600
on minimal resources, maybe a tiny VPS or a Raspberry Pi.

161
00:07:00,600 --> 00:07:03,560
Go provides that stability without the huge resource

162
00:07:03,560 --> 00:07:05,280
overhead you'd get with other languages.

163
00:07:05,280 --> 00:07:06,040
Exactly.

164
00:07:06,040 --> 00:07:07,700
And for the setup itself, the developers

165
00:07:07,700 --> 00:07:09,080
have made it dramatically simpler.

166
00:07:09,080 --> 00:07:12,440
They automatically build Docker images on every single release.

167
00:07:12,440 --> 00:07:15,140
Which is the gold standard for easy deployment now.

168
00:07:15,140 --> 00:07:17,520
If you know Docker, this means you can install the entire

169
00:07:17,520 --> 00:07:20,160
Go Defy server with all its dependencies perfectly

170
00:07:20,160 --> 00:07:22,320
contained in just a few commands.

171
00:07:22,320 --> 00:07:25,040
And that isolation is critical for keeping your notification

172
00:07:25,040 --> 00:07:28,160
service stable and separate from everything else on your server.

173
00:07:28,160 --> 00:07:30,200
This is where it gets really interesting for me,

174
00:07:30,200 --> 00:07:33,920
because a server is pretty useless without clients, right?

175
00:07:33,920 --> 00:07:35,480
Go Defy isn't just a back end.

176
00:07:35,480 --> 00:07:37,200
It's a full ecosystem.

177
00:07:37,200 --> 00:07:37,960
It is.

178
00:07:37,960 --> 00:07:40,120
And the most important component for daily use

179
00:07:40,120 --> 00:07:43,600
is obviously the mobile client, Go Defy Android.

180
00:07:43,600 --> 00:07:44,920
This is the app on your phone that

181
00:07:44,920 --> 00:07:47,880
subscribes to that persistent message stream via the web

182
00:07:47,880 --> 00:07:48,400
socket.

183
00:07:48,400 --> 00:07:50,680
So My Server Script pushes a message.

184
00:07:50,680 --> 00:07:53,240
The Go Defy server gets it via that REST API.

185
00:07:53,240 --> 00:07:55,800
And the client instantly displays it.

186
00:07:55,800 --> 00:07:58,320
What does the app actually do when it gets the data?

187
00:07:58,320 --> 00:08:00,520
It creates a standard traditional push

188
00:08:00,520 --> 00:08:02,920
notification right on your phone screen.

189
00:08:02,920 --> 00:08:05,000
And this is how your internal infrastructure

190
00:08:05,000 --> 00:08:06,480
can alert you instantly.

191
00:08:06,480 --> 00:08:08,960
But, and this is the crucial part,

192
00:08:08,960 --> 00:08:12,560
without ever involving Google's push services.

193
00:08:12,560 --> 00:08:16,280
Which guarantees that end-to-end data control.

194
00:08:16,280 --> 00:08:18,480
I do see the source material has the legal note

195
00:08:18,480 --> 00:08:21,520
about Google Play and the Google Play logo

196
00:08:21,520 --> 00:08:23,560
are trademarks of Google LLC.

197
00:08:23,560 --> 00:08:26,320
Right, which just reminds us where you download the client,

198
00:08:26,320 --> 00:08:31,120
but the actual message routing is 100% self-hosted.

199
00:08:31,120 --> 00:08:33,480
That is a fundamental difference compared

200
00:08:33,480 --> 00:08:36,780
to using something like PushOver or even Telegram,

201
00:08:36,780 --> 00:08:39,320
where the message still have to pass through a corporate server

202
00:08:39,320 --> 00:08:40,680
before it hits your device.

203
00:08:40,680 --> 00:08:41,640
Absolutely.

204
00:08:41,640 --> 00:08:44,760
And the ecosystem also supports pushing messages in other ways.

205
00:08:44,760 --> 00:08:46,640
There's also the GoDeFi clay.

206
00:08:46,640 --> 00:08:48,860
The command line interface, who is that for?

207
00:08:48,860 --> 00:08:51,000
It's really designed for system administrators

208
00:08:51,000 --> 00:08:52,880
and automation scripts, people who prefer

209
00:08:52,880 --> 00:08:54,640
interacting with the terminal.

210
00:08:54,640 --> 00:08:57,040
The source confirms the CLIs is not required.

211
00:08:57,040 --> 00:08:59,840
You can just use the REST API directly with cURL.

212
00:08:59,840 --> 00:09:02,600
But the CLI offers a more user-friendly scripted

213
00:09:02,600 --> 00:09:05,200
alternative when you're already in a Linux environment.

214
00:09:05,200 --> 00:09:07,560
It just simplifies that API interaction.

215
00:09:07,560 --> 00:09:09,360
And moving back to the server itself,

216
00:09:09,360 --> 00:09:11,840
we have to talk about longevity and customization.

217
00:09:11,840 --> 00:09:14,120
For any long-term infrastructure project,

218
00:09:14,120 --> 00:09:16,520
features like plugins and clear documentation

219
00:09:16,520 --> 00:09:17,640
are just paramount.

220
00:09:17,640 --> 00:09:18,520
They really are.

221
00:09:18,520 --> 00:09:20,880
And beyond basic user management,

222
00:09:20,880 --> 00:09:22,800
the server supports plugins.

223
00:09:22,800 --> 00:09:24,880
This allows the community or power users

224
00:09:24,880 --> 00:09:26,800
to extend the functionality.

225
00:09:26,800 --> 00:09:28,360
For instance, you could integrate

226
00:09:28,360 --> 00:09:30,680
specific types of authentication or message

227
00:09:30,680 --> 00:09:33,760
processing before an alert even goes out.

228
00:09:33,760 --> 00:09:36,760
It keeps the core server light, but allows for complexity

229
00:09:36,760 --> 00:09:37,560
if you need it.

230
00:09:37,560 --> 00:09:38,660
And the documentation.

231
00:09:38,660 --> 00:09:39,840
It's robust.

232
00:09:39,840 --> 00:09:42,160
It covers installation, configuration,

233
00:09:42,160 --> 00:09:46,280
and most importantly, detailed instructions for that REST API.

234
00:09:46,280 --> 00:09:48,480
If you want to integrate this with your own projects,

235
00:09:48,480 --> 00:09:50,480
the API docs are your guide.

236
00:09:50,480 --> 00:09:52,920
And for people building mission-critical automation,

237
00:09:52,920 --> 00:09:56,840
knowing the code is reliable is, well, it's essential.

238
00:09:56,840 --> 00:09:58,640
How does Goatify make sure it's not

239
00:09:58,640 --> 00:10:01,180
going to become one of those abandoned projects?

240
00:10:01,180 --> 00:10:03,960
The source highlights a very mature quality assurance

241
00:10:03,960 --> 00:10:04,860
process.

242
00:10:04,860 --> 00:10:07,160
It mentions that several static code analyzers

243
00:10:07,160 --> 00:10:10,840
and many unintended 2N tests are run on every TravisSci build.

244
00:10:10,840 --> 00:10:12,400
Which, for the learner, basically

245
00:10:12,400 --> 00:10:15,000
means that every time a developer changes the code,

246
00:10:15,000 --> 00:10:17,400
the system automatically puts it through rigorous testing

247
00:10:17,400 --> 00:10:18,800
to make sure nothing breaks.

248
00:10:18,800 --> 00:10:19,880
Precisely.

249
00:10:19,880 --> 00:10:22,540
That commitment ensures the code base stays reliable

250
00:10:22,540 --> 00:10:26,240
and functional, making it a truly dependable backbone.

251
00:10:26,240 --> 00:10:30,120
And if we connect that rigor to the bigger picture,

252
00:10:30,120 --> 00:10:33,280
what does the thriving, open source nature of Goatify

253
00:10:33,280 --> 00:10:35,600
tell us about the project's viability?

254
00:10:35,600 --> 00:10:38,000
It tells us the project has achieved critical mass

255
00:10:38,000 --> 00:10:39,480
and community trust.

256
00:10:39,480 --> 00:10:41,160
The foundation is the licensing.

257
00:10:41,160 --> 00:10:44,000
It's under the MIT license, which is highly permissive.

258
00:10:44,000 --> 00:10:45,760
It's free and open source, designed

259
00:10:45,760 --> 00:10:47,360
to be used by almost anyone.

260
00:10:47,360 --> 00:10:49,940
And the community metrics, they really bear that trust out.

261
00:10:49,940 --> 00:10:51,920
We saw massive engagement on the GitHub repo.

262
00:10:51,920 --> 00:10:52,720
Oh, absolutely.

263
00:10:52,720 --> 00:10:57,280
It has 13.9k stars, that is huge in the open source world.

264
00:10:57,280 --> 00:10:59,600
It's a massive signal of approval.

265
00:10:59,600 --> 00:11:02,120
And it's been forked 770 times, meaning

266
00:11:02,120 --> 00:11:05,120
nearly 800 other developers are actively adapting it.

267
00:11:05,120 --> 00:11:06,480
This is not a hobby project.

268
00:11:06,480 --> 00:11:08,800
No, it's a living piece of infrastructure.

269
00:11:08,800 --> 00:11:10,520
The project has benefited from the work

270
00:11:10,520 --> 00:11:13,840
of 46 different contributors, with the code mostly

271
00:11:13,840 --> 00:11:17,160
in Go and TypeScript for that great web interface.

272
00:11:17,160 --> 00:11:20,620
This broad base is the opposite of an abandoned project.

273
00:11:20,620 --> 00:11:23,000
And they ensure consistency through versioning,

274
00:11:23,000 --> 00:11:24,920
using Sember for every release.

275
00:11:24,920 --> 00:11:27,760
So users know exactly what to expect when they update.

276
00:11:27,760 --> 00:11:30,360
With 66 releases already published,

277
00:11:30,360 --> 00:11:33,280
it just signals continuous, stable development.

278
00:11:33,280 --> 00:11:35,720
So to quickly summarize the key takeaways then,

279
00:11:35,720 --> 00:11:39,000
Goatify offers a self-hosted, open-source alternative

280
00:11:39,000 --> 00:11:41,920
for real-time notifications that really prioritizes

281
00:11:41,920 --> 00:11:43,320
your digital autonomy.

282
00:11:43,320 --> 00:11:46,160
It gives you total end-to-end control over your data

283
00:11:46,160 --> 00:11:49,560
by leveraging that versatile REST API for sending messages

284
00:11:49,560 --> 00:11:50,880
and the persistent web socket

285
00:11:50,880 --> 00:11:52,520
for pushing them directly to your devices.

286
00:11:52,520 --> 00:11:54,560
You know, this raises an important question

287
00:11:54,560 --> 00:11:57,800
for anyone aiming for maximum digital autonomy.

288
00:11:57,800 --> 00:12:00,640
How strategically crucial is it to have a tool

289
00:12:00,640 --> 00:12:03,420
that completely separates your internal infrastructure,

290
00:12:03,420 --> 00:12:05,000
your monitoring, your scripts,

291
00:12:05,000 --> 00:12:08,160
from the notification services of large commercial companies?

292
00:12:08,160 --> 00:12:09,520
The ability to alert yourself

293
00:12:09,520 --> 00:12:11,360
without involving any third party,

294
00:12:11,360 --> 00:12:13,600
it fundamentally changes your risk profile

295
00:12:13,600 --> 00:12:15,080
and your operational freedom.

296
00:12:15,080 --> 00:12:15,960
Absolutely.

297
00:12:15,960 --> 00:12:19,400
And here's a final provocative thought for you to explore.

298
00:12:19,400 --> 00:12:21,040
Beyond just simple server alerts,

299
00:12:21,040 --> 00:12:24,340
how could integrating a simple API-driven messaging server

300
00:12:24,340 --> 00:12:26,840
like Goatify transform the automation

301
00:12:26,840 --> 00:12:28,960
of your personal or your work environment?

302
00:12:28,960 --> 00:12:30,280
I mean, think about integrating it

303
00:12:30,280 --> 00:12:32,560
into complex approval workflows

304
00:12:32,560 --> 00:12:34,680
or delivering time-sensitive reports

305
00:12:34,680 --> 00:12:37,040
or just completely transforming the responsiveness

306
00:12:37,040 --> 00:12:38,920
of your smart home setup.

307
00:12:38,920 --> 00:12:41,480
This deep dive was made possible by Safe Server.

308
00:12:41,480 --> 00:12:43,840
They handle hosting the type of software we discuss

309
00:12:43,840 --> 00:12:46,640
and support your journey toward digital transformation.

310
00:12:46,640 --> 00:12:49,120
Find out how they can help you master your infrastructure

311
00:12:49,120 --> 00:12:52,240
at www.safeserver.de.

312
00:12:52,240 --> 00:12:53,960
Thank you for joining us for this deep dive.

313
00:12:53,960 --> 00:12:54,800
Go explore.