1
00:00:00,000 --> 00:00:03,500
Welcome to the Deep Dive, the place where we cut through the noise, take a stack of

2
00:00:03,500 --> 00:00:07,880
complex sources, and basically hand you the crucial knowledge you need.

3
00:00:07,880 --> 00:00:12,040
Now, if you're anything like us, you probably spend a lot of time in communication

4
00:00:12,040 --> 00:00:17,040
apps, you know, Slack, Discord, maybe Rocket, chat, if you're self-hosting.

5
00:00:17,040 --> 00:00:20,880
Oh, yeah, definitely. Where work happens or, well, where we talk about work

6
00:00:20,880 --> 00:00:21,720
happening.

7
00:00:21,720 --> 00:00:26,870
Exactly. We chat, share links, try to manage projects. But what if your chat app

8
00:00:26,870 --> 00:00:29,120
wasn't just like a container for all that stuff?

9
00:00:29,120 --> 00:00:33,160
What if it was more like the operating system for your entire digital workspace?

10
00:00:33,160 --> 00:00:34,760
Hmm. Interesting idea.

11
00:00:34,760 --> 00:00:38,710
That's kind of the premise today. We're diving deep into tail chat. It's an

12
00:00:38,710 --> 00:00:41,760
application with a, frankly, pretty bold claim.

13
00:00:41,760 --> 00:00:46,800
It calls itself the next generation, no I am application in your own workspace.

14
00:00:46,800 --> 00:00:49,920
No. Okay. That's the key bit we need to unpack, I guess.

15
00:00:49,920 --> 00:00:53,370
All right. Is it just clever marketing? Or is this open source tool really doing

16
00:00:53,370 --> 00:00:56,200
something fundamentally different for team collaboration?

17
00:00:56,520 --> 00:01:01,220
So our mission today, unpack the tech, the philosophy behind tail chat, and see how

18
00:01:01,220 --> 00:01:05,280
it aims to turn group chat into, well, a customized application platform.

19
00:01:05,280 --> 00:01:09,790
Okay. Let's unpack this then. That no I am concept. It's really the core motivation

20
00:01:09,790 --> 00:01:11,240
driving the whole project.

21
00:01:11,240 --> 00:01:12,920
So what's the problem they're trying to solve?

22
00:01:12,920 --> 00:01:18,390
Well, the creators looked at the current instant messaging landscape. Slack,

23
00:01:18,390 --> 00:01:23,960
Discord, Teams, and SAR limitation. These apps mostly just focus on the chat itself.

24
00:01:24,360 --> 00:01:26,680
Sending messages, maybe a gif, a file link.

25
00:01:26,680 --> 00:01:27,560
Standard stuff.

26
00:01:27,560 --> 00:01:32,360
Yeah, standard stuff. But tail chat's philosophy is that I am is inherently about

27
00:01:32,360 --> 00:01:34,640
multi-person collaboration.

28
00:01:34,640 --> 00:01:35,040
Yeah.

29
00:01:35,040 --> 00:01:40,130
Right. So if collaboration is happening there anyway, the application itself should

30
00:01:40,130 --> 00:01:42,120
shoulder more responsibility.

31
00:01:42,120 --> 00:01:42,560
Gaining.

32
00:01:42,560 --> 00:01:46,240
Meaning it should be able to like forward external applications, manage complex

33
00:01:46,240 --> 00:01:49,960
workflows, all directly through that chat interface you're already using.

34
00:01:50,040 --> 00:01:53,420
Ah, okay. So it's not just where you talk about the project, it could be the hub

35
00:01:53,420 --> 00:01:55,400
where you actually do the project stuff too.

36
00:01:55,400 --> 00:02:00,590
Precisely. And that's why Noam stands for not only I am, it's designed as this

37
00:02:00,590 --> 00:02:04,480
highly customized application platform, but centered around that familiar I am

38
00:02:04,480 --> 00:02:04,920
interface.

39
00:02:04,920 --> 00:02:06,440
Like a mini OS for your team.

40
00:02:06,440 --> 00:02:10,810
Kind of. Imagine your chat screen isn't just messages, but more like a custom

41
00:02:10,810 --> 00:02:15,680
desktop for your team's work. Third party apps become enhanced functions.

42
00:02:16,120 --> 00:02:20,280
And the key thing holding it all together is this powerful plug-in system. That's

43
00:02:20,280 --> 00:02:22,600
the glue connection layer they talk about.

44
00:02:22,600 --> 00:02:26,700
That distinction platform versus just a messaging client that really feels like the

45
00:02:26,700 --> 00:02:27,760
core difference.

46
00:02:27,760 --> 00:02:28,240
It is.

47
00:02:28,240 --> 00:02:32,990
And for those of you listening who value transparency, our research shows tail chat

48
00:02:32,990 --> 00:02:36,720
is very much a modern open source application. It's all up on GitHub.

49
00:02:36,720 --> 00:02:38,640
Yep. Apache 2.0 license.

50
00:02:38,640 --> 00:02:38,920
Yeah.

51
00:02:38,920 --> 00:02:39,880
Pretty permissive.

52
00:02:39,960 --> 00:02:44,900
And it's got some traction, too, like 3.4K stars, hundreds of forks. So there's a

53
00:02:44,900 --> 00:02:47,080
real community building around this idea.

54
00:02:47,080 --> 00:02:51,220
They even have, like, nightly builds if you want the absolute latest, though maybe

55
00:02:51,220 --> 00:02:52,760
not the most stable code.

56
00:02:52,760 --> 00:02:54,320
Right, the usual trade off with nightly builds.

57
00:02:54,320 --> 00:02:58,110
OK, before we get into the how they pull this off, we really want to thank the

58
00:02:58,110 --> 00:03:00,440
supporter of this deep dive, SafeServer.

59
00:03:00,440 --> 00:03:04,520
SafeServer really gets the power of owning your own software ecosystem.

60
00:03:05,120 --> 00:03:10,070
They handle the hosting for exactly this kind of powerful, self-managed software

61
00:03:10,070 --> 00:03:10,960
like TailChat.

62
00:03:10,960 --> 00:03:14,320
And they support you in your whole digital transformation journey.

63
00:03:14,320 --> 00:03:16,720
So if you're thinking about running something like this yourself.

64
00:03:16,720 --> 00:03:21,240
Yeah, check them out. You can find more info at www.SafeServer.de.

65
00:03:21,240 --> 00:03:26,050
All right, so we've got the philosophy down. Not only I am, but philosophy is one

66
00:03:26,050 --> 00:03:26,560
thing.

67
00:03:26,560 --> 00:03:31,420
What's the actual user experience like? If I fire up TailChat, what does this

68
00:03:31,420 --> 00:03:33,040
vision look like day to day?

69
00:03:33,320 --> 00:03:35,920
Well, the core messenger functions are all there, as you'd expect.

70
00:03:35,920 --> 00:03:40,880
Basic messages, text, links, mentioning people, images, files, and you can add

71
00:03:40,880 --> 00:03:41,440
reactions.

72
00:03:41,440 --> 00:03:43,280
You know, the usual thumbs up or emoji stuff.

73
00:03:43,280 --> 00:03:44,200
OK, familiar ground.

74
00:03:44,200 --> 00:03:47,640
Familiar ground. But the difference really comes in the organizational structure

75
00:03:47,640 --> 00:03:48,720
around those messages.

76
00:03:48,720 --> 00:03:50,880
They use this two level group space concept.

77
00:03:50,880 --> 00:03:51,480
Two levels.

78
00:03:51,480 --> 00:03:55,470
Yeah, so you can divide different topics or projects using panels within a larger

79
00:03:55,470 --> 00:03:56,280
group space.

80
00:03:56,280 --> 00:03:59,080
And the customization here is apparently pretty deep.

81
00:03:59,440 --> 00:04:03,340
You can create your own unique group space layouts just by dragging and dropping

82
00:04:03,340 --> 00:04:04,080
panels around.

83
00:04:04,080 --> 00:04:05,880
Hmm, that sounds flexible.

84
00:04:05,880 --> 00:04:09,990
If it's meant to be your platform, it needs to adapt, right, to whatever your team

85
00:04:09,990 --> 00:04:10,760
actually does.

86
00:04:10,760 --> 00:04:15,480
Exactly. Whether you're a big enterprise or just a small team or even using it

87
00:04:15,480 --> 00:04:16,320
personally.

88
00:04:16,320 --> 00:04:21,630
And think about it, if this becomes your central hub, the communication volume

89
00:04:21,630 --> 00:04:22,880
could explode.

90
00:04:22,880 --> 00:04:25,200
Yeah, finding anything could become a nightmare.

91
00:04:25,200 --> 00:04:28,640
Right. Which is likely why they've built in an AI assistant.

92
00:04:28,640 --> 00:04:30,240
It's not just a gimmick.

93
00:04:30,240 --> 00:04:32,400
Using things like ChatGPT, I assume.

94
00:04:32,400 --> 00:04:34,480
Yeah, it agrees with large language models.

95
00:04:34,480 --> 00:04:38,400
So the assistant can help improve your wording, maybe simplify things.

96
00:04:38,400 --> 00:04:41,880
But crucially, it can summarize long conversation histories.

97
00:04:41,880 --> 00:04:45,880
Oh, that's huge. If all your decisions end up in chat, summaries are essential.

98
00:04:45,880 --> 00:04:50,160
Absolutely. And managing all that, plus potentially sensitive project data,

99
00:04:50,160 --> 00:04:53,940
especially if you're self-hosting for privacy, requires some serious control

100
00:04:53,940 --> 00:04:54,800
mechanisms.

101
00:04:54,800 --> 00:04:57,440
Good point. What about security and permissions?

102
00:04:57,440 --> 00:05:01,730
They seem to emphasize that the docs highlight privacy, like only invited members

103
00:05:01,730 --> 00:05:02,680
can join a group.

104
00:05:02,680 --> 00:05:05,400
Seems basic, but important for locking down a workspace.

105
00:05:05,400 --> 00:05:06,600
Keeps randoms out.

106
00:05:06,600 --> 00:05:11,080
Yep. And adding friends requires not just their nickname, but also this random

107
00:05:11,080 --> 00:05:12,200
string of numbers.

108
00:05:12,200 --> 00:05:16,400
Just another layer to prevent unwanted contact or accidental ads.

109
00:05:16,400 --> 00:05:20,170
Makes sense, especially if an enterprise is aiming for that digital sovereignty

110
00:05:20,170 --> 00:05:20,600
goal.

111
00:05:20,600 --> 00:05:21,960
You need control.

112
00:05:21,960 --> 00:05:25,600
Absolutely. Which brings us neatly to group roles.

113
00:05:25,600 --> 00:05:28,760
Tailchat includes a built-in RBAC system.

114
00:05:28,760 --> 00:05:31,000
RBAC. Role-based access control.

115
00:05:31,000 --> 00:05:35,710
Exactly. So instead of just giving everyone broad admin or user permissions, you

116
00:05:35,710 --> 00:05:37,240
get much more granular.

117
00:05:37,240 --> 00:05:41,420
Think of it like digital key cards for specific rooms or tools within your custom

118
00:05:41,420 --> 00:05:42,280
workspace.

119
00:05:42,280 --> 00:05:46,960
So you could say only the QA team gets access to the deployment plugin, maybe.

120
00:05:46,960 --> 00:05:48,240
Precisely that kind of thing.

121
00:05:48,240 --> 00:05:51,460
Or maybe only certain people can see the panel where sensitive financial

122
00:05:51,460 --> 00:05:52,600
discussions happen.

123
00:05:52,600 --> 00:05:56,150
Permissions are matched based on the role you assign someone and specific

124
00:05:56,150 --> 00:05:57,160
permission points.

125
00:05:57,160 --> 00:06:00,400
And importantly, plugins can easily integrate with this system.

126
00:06:00,400 --> 00:06:03,080
Ah. So plugins can define their own permissions too.

127
00:06:03,080 --> 00:06:07,720
Yes. This flexibility means you can set up tail chat to be really rigorous, like

128
00:06:07,720 --> 00:06:08,960
for regulated enterprise.

129
00:06:08,960 --> 00:06:13,800
Or keep it more open and fun for, say, a creative team or just personal use.

130
00:06:13,800 --> 00:06:18,900
Okay. This is starting to sound less like just a chat app and more like, well, a

131
00:06:18,900 --> 00:06:19,680
platform.

132
00:06:19,680 --> 00:06:22,720
And that's where the underlying design becomes really fascinating.

133
00:06:22,720 --> 00:06:27,080
That's what enables the whole know-I-am vision and lets it scale.

134
00:06:27,080 --> 00:06:30,000
Let's get technical for a second then. What's under the hood?

135
00:06:30,000 --> 00:06:34,240
Okay. So the tech stack is pretty modern, built on React and TypeScript.

136
00:06:34,240 --> 00:06:38,420
But the architecture is the real story here. It uses a front-end microkernel

137
00:06:38,420 --> 00:06:39,440
architecture.

138
00:06:39,440 --> 00:06:41,640
Microkernel on the front end. Interesting.

139
00:06:41,640 --> 00:06:44,720
And on the back end, it uses a microservice architecture.

140
00:06:44,720 --> 00:06:50,680
Whoa, okay. Microservices. That sounds potentially complicated to manage,

141
00:06:50,680 --> 00:06:53,480
especially for someone maybe just spinning this up using one of those quick

142
00:06:53,480 --> 00:06:54,760
deployment tools you mentioned.

143
00:06:54,760 --> 00:06:59,510
That's a really fair question. It definitely sounds more complex than a single monolithic

144
00:06:59,510 --> 00:07:00,320
application.

145
00:07:00,320 --> 00:07:04,820
Is there a trade-off there? Are they sacrificing ease of setup for this platform

146
00:07:04,820 --> 00:07:05,800
flexibility?

147
00:07:05,800 --> 00:07:07,440
There's always a trade-off, right? Yeah.

148
00:07:07,440 --> 00:07:11,840
But the argument for microservices here is that this structure actually makes the

149
00:07:11,840 --> 00:07:14,680
platform inherently more resilient and scalable.

150
00:07:14,680 --> 00:07:17,920
Which you need if it's going to potentially replace several other tools.

151
00:07:17,920 --> 00:07:20,520
How so? Can you break that down a bit? Sure.

152
00:07:20,520 --> 00:07:24,200
Think of a traditional monolithic app like one big machine doing everything.

153
00:07:24,200 --> 00:07:28,450
If one part breaks or gets overloaded, the whole machine might slow down or stop.

154
00:07:28,450 --> 00:07:29,080
Right.

155
00:07:29,080 --> 00:07:32,850
Microservices are more like a collection of smaller specialized machines, each

156
00:07:32,850 --> 00:07:34,440
doing one job really well.

157
00:07:34,440 --> 00:07:38,520
User authentication, message processing, managing plugins, whatever.

158
00:07:38,520 --> 00:07:42,840
If one machine, say the one handling file uploads, gets overloaded,

159
00:07:42,840 --> 00:07:46,410
you can just add more power to that specific machine without messing with the

160
00:07:46,410 --> 00:07:47,000
others.

161
00:07:47,000 --> 00:07:49,720
Ah, I see. Scale, just the parts that need it.

162
00:07:49,720 --> 00:07:54,360
Exactly. So for you, the user, the takeaway is that this architecture makes TailChat

163
00:07:54,360 --> 00:07:54,600
ready

164
00:07:54,600 --> 00:07:59,680
for potentially large-scale use and handles growth much more gracefully from the

165
00:07:59,680 --> 00:08:00,200
get-go,

166
00:08:00,200 --> 00:08:03,880
even if it might seem more complex initially. Okay, that makes sense.

167
00:08:03,880 --> 00:08:07,590
It's building for the platform vision from the ground up. So the architecture

168
00:08:07,590 --> 00:08:07,960
supports

169
00:08:07,960 --> 00:08:12,970
the platform idea, and the plugins are how users actually experience that not-only-I-am

170
00:08:12,970 --> 00:08:13,960
functionality.

171
00:08:13,960 --> 00:08:18,360
Precisely. The plugin system is designed to let developers integrate other

172
00:08:18,360 --> 00:08:19,400
applications

173
00:08:19,400 --> 00:08:24,920
much more deeply and naturally than just, say, embedding a web page using an iframe,

174
00:08:24,920 --> 00:08:28,440
which is often how older TAP platforms handle integrations.

175
00:08:28,440 --> 00:08:32,440
Right. Let's get concrete, then. What kind of things can these plugins actually do?

176
00:08:32,440 --> 00:08:34,360
Because this is where the real value seems to be.

177
00:08:34,360 --> 00:08:38,680
Totally. So you're not just messaging about a task anymore. Instead of, you know,

178
00:08:38,680 --> 00:08:38,840
stopping

179
00:08:38,840 --> 00:08:43,420
your chat, opening Zoom in another tab, starting a call, copying the link, pasting

180
00:08:43,420 --> 00:08:43,720
it back.

181
00:08:43,720 --> 00:08:45,080
The usual awkward dance.

182
00:08:45,080 --> 00:08:48,920
Yeah. The plugins might allow you to just start that video call right inside the

183
00:08:48,920 --> 00:08:49,640
tail chat channel.

184
00:08:49,640 --> 00:08:51,560
Okay, that cuts down friction. What else?

185
00:08:51,560 --> 00:08:55,720
Collaboration tools. Instead of linking out to Miro or Google Docs,

186
00:08:55,720 --> 00:09:01,330
imagine having a collaborative online drawing board plugin or a rich text editor

187
00:09:01,330 --> 00:09:01,640
running

188
00:09:01,640 --> 00:09:06,840
inside the chat channel itself. Everyone can see and edit in real time, right there.

189
00:09:06,840 --> 00:09:11,960
That drastically reduces context twitching, which, let's be honest,

190
00:09:11,960 --> 00:09:14,360
is a huge productivity killer these days.

191
00:09:14,360 --> 00:09:15,080
It really is.

192
00:09:15,080 --> 00:09:15,480
Yeah.

193
00:09:15,480 --> 00:09:19,400
And this platform approach extends to how you connect third-party apps, too.

194
00:09:19,400 --> 00:09:24,350
They offer different integration methods, simple URL requests using an open API app

195
00:09:24,350 --> 00:09:25,240
standard,

196
00:09:25,240 --> 00:09:28,520
or even building a full backend plugin for deeper integration.

197
00:09:28,520 --> 00:09:30,360
So lots of options for developers.

198
00:09:30,360 --> 00:09:33,840
Yeah. You could have plugins for end-to-end encryption if you need that extra

199
00:09:33,840 --> 00:09:34,600
security layer,

200
00:09:34,600 --> 00:09:38,600
or plugins that receive custom push notifications from your other tools,

201
00:09:38,600 --> 00:09:41,640
like your CI-CD pipeline or project management system,

202
00:09:41,640 --> 00:09:43,800
directly into your tail chat interface.

203
00:09:43,800 --> 00:09:45,240
Keeps everything in one place.

204
00:09:45,240 --> 00:09:48,920
Now, we should probably mention a quick caveat we found in the source material.

205
00:09:48,920 --> 00:09:51,080
Yes. The developer interface.

206
00:09:51,080 --> 00:09:53,400
Right. While the core app is stable,

207
00:09:53,400 --> 00:09:58,200
the interface exposed for third-party developers is still evolving.

208
00:09:58,200 --> 00:10:00,520
They say it's generally backward compatible,

209
00:10:00,520 --> 00:10:04,680
but there's still a possibility of breaking changes as they refine things.

210
00:10:04,680 --> 00:10:07,720
Which is pretty standard for an active open source project,

211
00:10:07,720 --> 00:10:09,160
especially one moving this fast.

212
00:10:09,160 --> 00:10:13,160
But definitely something for potential plugin developers to keep in mind.

213
00:10:13,160 --> 00:10:17,120
Good note. Okay, so practically speaking, how do people use tail chat? What

214
00:10:17,120 --> 00:10:17,800
platforms?

215
00:10:17,800 --> 00:10:19,400
Well, it's fundamentally built on HTML,

216
00:10:19,400 --> 00:10:24,040
so the core experience should work on any modern browser, any OS.

217
00:10:24,040 --> 00:10:24,920
Web-first.

218
00:10:24,920 --> 00:10:29,240
Web-first, yeah. But they do offer dedicated clients for mobile and desktop.

219
00:10:29,240 --> 00:10:33,720
These likely provide better integration with the operating system.

220
00:10:33,720 --> 00:10:37,480
Things like native notifications, maybe better screenshot tools,

221
00:10:37,480 --> 00:10:40,440
stuff you can't always do perfectly just in a browser tab.

222
00:10:40,440 --> 00:10:44,680
Right, OS specific features. And you mentioned quick deployment options earlier.

223
00:10:44,680 --> 00:10:48,680
Yeah, the docs mentioned things like deploying easily on CLOs or Cloud Run.

224
00:10:48,680 --> 00:10:54,440
These newer platform as a service options that simplify running containerized apps.

225
00:10:54,440 --> 00:10:58,280
Okay, interesting. Makes it potentially less daunting to get started than

226
00:10:58,280 --> 00:11:00,440
managing a full microservice setup manually.

227
00:11:00,440 --> 00:11:04,520
Hopefully, yeah. So if we try and connect this all back to the bigger picture,

228
00:11:04,520 --> 00:11:10,200
tail chat isn't really just aiming to be a slightly better Discord or Slack clone.

229
00:11:10,200 --> 00:11:12,040
Seems like it's trying to solve a bigger problem.

230
00:11:12,040 --> 00:11:15,000
I think so. It feels like it's trying to tackle tool fatigue.

231
00:11:15,000 --> 00:11:20,150
You know, that feeling of constantly jumping between your chat app, your project

232
00:11:20,150 --> 00:11:20,840
manager,

233
00:11:20,840 --> 00:11:24,440
your video call tool, your document editor.

234
00:11:24,440 --> 00:11:25,880
Oh, I know that feeling well.

235
00:11:25,880 --> 00:11:30,520
By abstracting functions into plugins from the start and using that scalable

236
00:11:30,520 --> 00:11:34,680
microservice architecture, it really becomes this potential single hub,

237
00:11:34,680 --> 00:11:40,200
a highly customizable application platform that you control potentially on your own

238
00:11:40,200 --> 00:11:41,080
infrastructure.

239
00:11:41,080 --> 00:11:44,120
Giving you maximum control and customization,

240
00:11:44,120 --> 00:11:47,720
ideally reducing that need to switch apps constantly.

241
00:11:47,720 --> 00:11:50,760
That seems to be the goal. It's a different philosophy,

242
00:11:50,760 --> 00:11:53,800
emphasizing expansion and integration right from the core,

243
00:11:53,800 --> 00:11:57,800
rather than just being a linear messaging tool with some bots tacked on.

244
00:11:57,800 --> 00:12:02,090
It's genuinely impressive that they've built this potentially complex, self-managed

245
00:12:02,090 --> 00:12:02,440
platform.

246
00:12:02,440 --> 00:12:06,990
But that does bring us to the big question we kind of want to leave you, the

247
00:12:06,990 --> 00:12:07,800
listener, with.

248
00:12:07,800 --> 00:12:09,160
The trade-off question again.

249
00:12:09,160 --> 00:12:13,720
Yeah. Given the potential complexity, even with easier deployment options,

250
00:12:13,720 --> 00:12:17,910
of owning and managing this entire collaboration ecosystem, this whole Noyan

251
00:12:17,910 --> 00:12:18,600
platform,

252
00:12:18,600 --> 00:12:22,520
does that level of digital sovereignty and deep customization

253
00:12:22,520 --> 00:12:26,280
truly outweigh the sheer convenience of just using the big centralized

254
00:12:26,280 --> 00:12:28,120
hosted platforms we're all used to?

255
00:12:28,120 --> 00:12:29,720
It's a fundamental question, isn't it?

256
00:12:29,720 --> 00:12:32,040
Ease of use versus control and ownership.

257
00:12:32,040 --> 00:12:37,160
Exactly. It forces us to ask, what's the real value proposition for you?

258
00:12:37,160 --> 00:12:40,600
Where do you draw the line between convenience and digital control?

259
00:12:40,600 --> 00:12:42,760
Something to definitely mull over.

260
00:12:43,560 --> 00:12:46,240
Well, that's certainly food for thought.

261
00:12:46,240 --> 00:12:51,090
Thank you for joining us on this deep dive into TailChat and its norm approach to

262
00:12:51,090 --> 00:12:52,640
collaboration.

263
00:12:52,640 --> 00:12:54,240
Getting interesting to explore.

264
00:12:54,240 --> 00:12:57,140
And one more huge thanks to our supporter, Safe Server.

265
00:12:57,140 --> 00:13:00,800
If you're considering taking control and hosting powerful open source software like

266
00:13:00,800 --> 00:13:05,350
TailChat and need help accelerating your digital transformation, they are the

267
00:13:05,350 --> 00:13:05,920
people to check

268
00:13:05,920 --> 00:13:06,920
out.

269
00:13:06,920 --> 00:13:09,480
Find out more at www.safeserver.de.

270
00:13:09,480 --> 00:13:12,620
That's www.safeserver.de.

271
00:13:12,620 --> 00:13:14,940
Thanks again for listening and we'll catch you on the next Deep Dive!