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

2
00:00:01,640 --> 00:00:05,320
This is your shortcut, really, to understanding complex topics

3
00:00:05,320 --> 00:00:07,760
without getting completely lost in all the details.

4
00:00:07,760 --> 00:00:09,680
Now, before we jump into today's subject, which

5
00:00:09,680 --> 00:00:12,440
I think is fascinating, we want to give a huge shout out

6
00:00:12,440 --> 00:00:13,760
to Safe Server.

7
00:00:13,760 --> 00:00:16,240
They actually take care of the hosting for the software

8
00:00:16,240 --> 00:00:17,760
we're talking about today.

9
00:00:17,760 --> 00:00:20,520
They provide really robust infrastructure and great support

10
00:00:20,520 --> 00:00:22,000
for digital transformation.

11
00:00:22,000 --> 00:00:27,640
You can find out more about what they do at www.safeserver.de.

12
00:00:27,640 --> 00:00:29,760
All right, let's dive right in.

13
00:00:29,760 --> 00:00:32,320
So we live in this hybrid-connected world, right?

14
00:00:32,320 --> 00:00:34,080
And we're just bombarded, I mean,

15
00:00:34,080 --> 00:00:36,560
constantly with this massive amount of information,

16
00:00:36,560 --> 00:00:39,500
trying to stay genuinely well-informed about the latest

17
00:00:39,500 --> 00:00:41,120
tech or how industries are changing.

18
00:00:41,120 --> 00:00:42,840
Well, without getting totally overwhelmed,

19
00:00:42,840 --> 00:00:44,600
it feels like a full-time job.

20
00:00:44,600 --> 00:00:46,360
And that's exactly why we do the deep dive

21
00:00:46,360 --> 00:00:47,880
to cut through all that noise for you.

22
00:00:47,880 --> 00:00:50,160
We pull out the most important bits, the key insights,

23
00:00:50,160 --> 00:00:53,000
so you can grasp these tricky subjects quickly and clearly.

24
00:00:53,000 --> 00:00:54,340
Today, we're zoning in on Kistra.

25
00:00:54,340 --> 00:00:56,840
It's an open source, workful automation platform.

26
00:00:56,840 --> 00:00:59,360
Our mission today, we're going to unpack Kistra,

27
00:00:59,360 --> 00:01:01,760
break it down so that really anyone,

28
00:01:01,760 --> 00:01:03,120
whether you're a seasoned developer

29
00:01:03,120 --> 00:01:05,120
or maybe just starting to explore automation,

30
00:01:05,120 --> 00:01:07,440
can get what it is, why it's actually so powerful,

31
00:01:07,440 --> 00:01:10,880
and crucially, how it's making complex operations

32
00:01:10,880 --> 00:01:13,160
much simpler for teams all over the world.

33
00:01:13,160 --> 00:01:15,600
Yeah, and what's really interesting about Kistra, I think,

34
00:01:15,600 --> 00:01:19,320
is how it fundamentally rethinks the whole orchestration

35
00:01:19,320 --> 00:01:20,840
and scheduling of code.

36
00:01:20,840 --> 00:01:24,660
It's really designed to bring some order to that chaos

37
00:01:24,660 --> 00:01:26,600
we often see, streamlining automation

38
00:01:26,600 --> 00:01:28,440
across loads of different systems.

39
00:01:28,440 --> 00:01:31,280
And as we'll get into, its declarative approach,

40
00:01:31,280 --> 00:01:32,760
combined with this, well,

41
00:01:32,760 --> 00:01:34,960
remarkably intuitive visual interface,

42
00:01:34,960 --> 00:01:37,880
it's really key to making this powerful tech

43
00:01:37,880 --> 00:01:40,680
genuinely accessible, much more so than

44
00:01:40,680 --> 00:01:41,920
many traditional tools.

45
00:01:41,920 --> 00:01:44,120
Okay, let's unpack that right from the start.

46
00:01:44,120 --> 00:01:46,280
Workflow automation, orchestration,

47
00:01:46,280 --> 00:01:49,780
I mean, these terms can sound a bit jargony, can't they?

48
00:01:49,780 --> 00:01:51,160
But let's think about a common pain point,

49
00:01:51,160 --> 00:01:52,880
that feeling, you know, when a critical report

50
00:01:52,880 --> 00:01:54,820
depends on like five different systems,

51
00:01:54,820 --> 00:01:56,840
or a key business process means someone has to

52
00:01:56,840 --> 00:01:59,280
manually kick off scripts, check logs,

53
00:01:59,280 --> 00:02:01,680
and just sort of hope nothing breaks.

54
00:02:01,680 --> 00:02:02,820
We've all been there, right?

55
00:02:02,820 --> 00:02:03,660
Absolutely.

56
00:02:03,660 --> 00:02:06,620
So what is this workflow automation exactly?

57
00:02:06,620 --> 00:02:09,200
And why can't we just string things together manually

58
00:02:09,200 --> 00:02:11,040
or use simpler tools?

59
00:02:11,040 --> 00:02:13,880
What's the chaos that needs something like Kestra?

60
00:02:13,880 --> 00:02:14,920
That's a really good way to put it,

61
00:02:14,920 --> 00:02:16,280
that chaos you mentioned.

62
00:02:16,280 --> 00:02:19,000
That's precisely what Kestra was built to tame.

63
00:02:19,000 --> 00:02:21,640
See, historically, when you needed to automate

64
00:02:21,640 --> 00:02:24,260
a sequence of tasks, let's say,

65
00:02:24,260 --> 00:02:25,800
pulling data from a database,

66
00:02:25,800 --> 00:02:27,360
doing some transformation,

67
00:02:27,360 --> 00:02:30,080
then loading it somewhere else, like an analytics tool,

68
00:02:30,080 --> 00:02:32,420
we'd often end up stitching together custom scripts,

69
00:02:32,420 --> 00:02:34,400
maybe using cron jobs for scheduling,

70
00:02:34,400 --> 00:02:37,440
or perhaps older, more complex tools like Apache Airflow.

71
00:02:37,440 --> 00:02:39,920
Or even simpler, sometimes quite limited services

72
00:02:39,920 --> 00:02:43,240
like Zapier or NNN for lighter tasks.

73
00:02:43,240 --> 00:02:48,240
The problem is, as soon as things get even slightly complex,

74
00:02:48,240 --> 00:02:51,880
multiple dependencies, proper error handling, retries,

75
00:02:51,880 --> 00:02:53,960
different systems need to talk, version control

76
00:02:53,960 --> 00:02:55,840
may be needing real-time responses.

77
00:02:55,840 --> 00:02:58,680
Those approaches, they become brittle, fast,

78
00:02:58,680 --> 00:03:01,600
they're hard to monitor, a nightmare to scale reliably.

79
00:03:01,600 --> 00:03:03,160
Kestrel comes in as an event-driven

80
00:03:03,160 --> 00:03:05,120
declarative orchestration platform

81
00:03:05,120 --> 00:03:07,260
to basically solve that headache.

82
00:03:07,260 --> 00:03:09,800
Its core purpose is making both scheduled workflows,

83
00:03:09,800 --> 00:03:11,400
like that daily report you mentioned,

84
00:03:11,400 --> 00:03:13,760
and event-driven workflows, like reacting instantly

85
00:03:13,760 --> 00:03:15,080
when a new customer signs up,

86
00:03:15,080 --> 00:03:18,540
making those easy and, really importantly, resilient.

87
00:03:18,540 --> 00:03:21,700
It sort of abstracts away a lot of the tricky underlying stuff,

88
00:03:21,700 --> 00:03:23,640
letting you define what needs to happen,

89
00:03:23,640 --> 00:03:25,080
rather than having to manually script

90
00:03:25,080 --> 00:03:27,400
how to handle every single failure or dependency.

91
00:03:27,400 --> 00:03:28,900
Okay, that makes a lot of sense,

92
00:03:28,900 --> 00:03:33,680
bringing order to that potential spaghetti of tasks.

93
00:03:33,680 --> 00:03:35,720
And here's where I think it gets really interesting,

94
00:03:35,720 --> 00:03:37,540
especially for someone who maybe doesn't live

95
00:03:37,540 --> 00:03:40,280
and breathe code day in, day out.

96
00:03:40,280 --> 00:03:42,120
Kestrel has this core idea.

97
00:03:42,120 --> 00:03:44,940
Everything as code and from the UI.

98
00:03:44,940 --> 00:03:48,720
Now, that sounds almost contradictory.

99
00:03:48,720 --> 00:03:51,400
Like, on one hand, you've got the rigor of code

100
00:03:51,400 --> 00:03:53,900
for developers, but then you're saying non-coders

101
00:03:53,900 --> 00:03:55,480
can use the UI.

102
00:03:55,480 --> 00:03:56,900
How does that actually bridge the gap?

103
00:03:56,900 --> 00:03:59,440
Is there a tension there or is it seamless?

104
00:03:59,440 --> 00:04:01,220
It's actually a really brilliant fusion

105
00:04:01,220 --> 00:04:04,020
and it pretty much eliminates that tension you might expect.

106
00:04:04,020 --> 00:04:06,480
So when we talk about a declarative YAML interface,

107
00:04:06,480 --> 00:04:08,520
think of it like writing a simple recipe.

108
00:04:08,520 --> 00:04:10,960
You're describing what you want the final dish to be,

109
00:04:10,960 --> 00:04:13,680
not giving super detailed step-by-step instructions

110
00:04:13,680 --> 00:04:15,520
for every single chop and stir.

111
00:04:15,520 --> 00:04:17,580
You say, I want to extract data here,

112
00:04:17,580 --> 00:04:20,200
transform it like this, then load it there.

113
00:04:20,200 --> 00:04:22,080
Kestra handles the how,

114
00:04:22,080 --> 00:04:25,000
including the tricky bits like error handling, retries,

115
00:04:25,000 --> 00:04:26,840
managing the state of the workflow.

116
00:04:26,840 --> 00:04:29,680
In this declarative way, it's not just simpler,

117
00:04:29,680 --> 00:04:31,400
it's actually way more robust.

118
00:04:31,400 --> 00:04:33,520
Your workflow is defined precisely

119
00:04:33,520 --> 00:04:35,180
in a format humans can read,

120
00:04:35,180 --> 00:04:37,420
which makes it easier to version control, test,

121
00:04:37,420 --> 00:04:39,280
ensure it runs the same way everywhere.

122
00:04:39,280 --> 00:04:40,520
It's like a blueprint.

123
00:04:40,520 --> 00:04:43,460
You write these workflows using Kestra's built-in code editor

124
00:04:43,460 --> 00:04:45,200
right there for the YAML.

125
00:04:45,200 --> 00:04:47,760
But, and this is the magic bit that bridges the gap,

126
00:04:47,760 --> 00:04:50,640
you can also build and visualize the exact same workflow

127
00:04:50,640 --> 00:04:51,840
directly from the UI.

128
00:04:51,840 --> 00:04:52,880
It's got drag and drop,

129
00:04:52,880 --> 00:04:54,580
it has auto-completion to help you,

130
00:04:54,580 --> 00:04:56,280
real-time checks to see if it makes sense.

131
00:04:56,280 --> 00:04:58,480
And the truly seamless part,

132
00:04:58,480 --> 00:05:00,160
when you drag a new task in the UI

133
00:05:00,160 --> 00:05:01,880
or change a setting visually,

134
00:05:01,880 --> 00:05:06,360
the underlying YAML code adjusts automatically, instantly.

135
00:05:06,360 --> 00:05:08,000
So the core logic, the orchestration,

136
00:05:08,000 --> 00:05:10,240
it's always managed declaratively in code,

137
00:05:10,240 --> 00:05:12,640
even if you built it all by clicking and dragging.

138
00:05:12,640 --> 00:05:15,320
This means, say, a data engineer could tweak some YAML,

139
00:05:15,320 --> 00:05:16,720
and then maybe a business analyst

140
00:05:16,720 --> 00:05:19,120
could visually check out, the flow makes sense.

141
00:05:19,120 --> 00:05:20,960
It makes collaboration way easier.

142
00:05:20,960 --> 00:05:21,800
Wow, okay.

143
00:05:21,800 --> 00:05:23,640
And, yeah, to keep things proper,

144
00:05:23,640 --> 00:05:26,440
it even has built-in Git integration.

145
00:05:26,440 --> 00:05:28,720
So your UI built workflows,

146
00:05:28,720 --> 00:05:30,320
still versioned, still managed,

147
00:05:30,320 --> 00:05:31,760
like any other piece of code.

148
00:05:31,760 --> 00:05:34,000
That really is a powerful combination.

149
00:05:34,000 --> 00:05:36,720
It sounds like it makes creating things much easier,

150
00:05:36,720 --> 00:05:40,160
but you still get all the benefits of managing it as code.

151
00:05:40,160 --> 00:05:42,280
So, okay, if I'm someone looking

152
00:05:42,280 --> 00:05:45,940
to start automating something, what are the basic terms?

153
00:05:45,940 --> 00:05:48,760
The building blocks I need to get my head around in Kestra

154
00:05:48,760 --> 00:05:51,080
to actually start building a workflow.

155
00:05:51,080 --> 00:05:51,920
Give us the basics.

156
00:05:51,920 --> 00:05:53,600
Absolutely, let's break down the main pieces

157
00:05:53,600 --> 00:05:54,920
you'll work with, the fundamental thing,

158
00:05:54,920 --> 00:05:57,240
the whole process of the recipe you wanna run,

159
00:05:57,240 --> 00:05:58,080
that's called a flow.

160
00:05:58,080 --> 00:05:59,000
A flow, got it.

161
00:05:59,000 --> 00:06:01,880
Think of it as the complete automated sequence,

162
00:06:01,880 --> 00:06:04,000
an entire data pipeline, maybe,

163
00:06:04,000 --> 00:06:06,600
or a multi-step approval process.

164
00:06:06,600 --> 00:06:09,400
Now, within that flow, each individual action,

165
00:06:09,400 --> 00:06:11,240
each step, like run this Python script,

166
00:06:11,240 --> 00:06:15,040
move that file, send an email, call an API, that's a task.

167
00:06:15,040 --> 00:06:16,880
Okay, tasks are the steps in the flow.

168
00:06:16,880 --> 00:06:18,800
Exactly, they're the specific ingredients

169
00:06:18,800 --> 00:06:20,720
and instructions in your recipe.

170
00:06:20,720 --> 00:06:23,480
Then you have triggers, they decide how your flow starts.

171
00:06:23,480 --> 00:06:25,760
You've got scheduled triggers, pretty simple,

172
00:06:25,760 --> 00:06:28,680
like setting an alarm clock, run this flow every hour

173
00:06:28,680 --> 00:06:31,000
or every Tuesday at 3 p.m., whatever you need.

174
00:06:31,000 --> 00:06:33,480
And crucially, Keystra is really strong

175
00:06:33,480 --> 00:06:35,280
with event-driven triggers.

176
00:06:35,280 --> 00:06:37,800
This lets your flow react instantly to something happening.

177
00:06:37,800 --> 00:06:40,420
Maybe a new file appears in cloud storage

178
00:06:40,420 --> 00:06:42,800
or a message pops up in a Kafka topic

179
00:06:42,800 --> 00:06:44,920
or even a specific API call comes in.

180
00:06:44,920 --> 00:06:46,040
Reactive, okay.

181
00:06:46,040 --> 00:06:46,880
Yeah.

182
00:06:46,880 --> 00:06:48,440
And for keeping things organized,

183
00:06:48,440 --> 00:06:51,760
especially as you build more flows, you use namespaces.

184
00:06:51,760 --> 00:06:52,920
They're basically like folders,

185
00:06:52,920 --> 00:06:55,040
just ways to group related flows together,

186
00:06:55,040 --> 00:06:56,360
keep things tidy.

187
00:06:56,360 --> 00:06:59,360
And inputs and variables add flexibility.

188
00:06:59,360 --> 00:07:01,940
They let you customize flows and tasks on the fly

189
00:07:01,940 --> 00:07:03,480
so you can reuse the same flow

190
00:07:03,480 --> 00:07:04,880
for slightly different situations

191
00:07:04,880 --> 00:07:05,900
without copying everything.

192
00:07:05,900 --> 00:07:06,740
Makes sense.

193
00:07:06,740 --> 00:07:08,220
And finally, to see all this,

194
00:07:08,220 --> 00:07:09,600
that intuitive UI we mentioned

195
00:07:09,600 --> 00:07:11,820
gives you a live topology view.

196
00:07:11,820 --> 00:07:14,760
Technically, it's a directed acyclic graph.

197
00:07:14,760 --> 00:07:15,600
A DAG.

198
00:07:15,600 --> 00:07:16,440
A DAG.

199
00:07:16,440 --> 00:07:17,280
Think of it like a flow chart

200
00:07:17,280 --> 00:07:19,440
or a roadmap for your workflow.

201
00:07:19,440 --> 00:07:21,280
Each task is a box.

202
00:07:21,280 --> 00:07:24,380
Arrows show how data moves and what depends on what.

203
00:07:24,380 --> 00:07:26,640
It's super important because it ensures tasks

204
00:07:26,640 --> 00:07:27,840
run on the right order,

205
00:07:27,840 --> 00:07:29,080
avoids messy loops,

206
00:07:29,080 --> 00:07:31,400
and lets you see dependencies at a glance.

207
00:07:31,400 --> 00:07:33,480
Makes even really complex stuff

208
00:07:33,480 --> 00:07:35,680
much easier to understand visually.

209
00:07:35,680 --> 00:07:38,280
That DAG view sounds incredibly useful,

210
00:07:38,280 --> 00:07:40,280
especially when things get complicated.

211
00:07:40,280 --> 00:07:42,620
Now you mentioned one of Kestra's standout features

212
00:07:42,620 --> 00:07:45,080
is its rich plugin ecosystem.

213
00:07:45,080 --> 00:07:46,640
That sounds powerful.

214
00:07:46,640 --> 00:07:48,120
When you say plugin ecosystem,

215
00:07:48,120 --> 00:07:50,520
what kind of things can these plugins actually do?

216
00:07:50,520 --> 00:07:51,880
How comprehensive is it?

217
00:07:51,880 --> 00:07:53,600
Can it really connect to almost anything?

218
00:07:53,600 --> 00:07:54,840
Oh, it really is comprehensive.

219
00:07:54,840 --> 00:07:57,320
This is where Kestra's flexibility just shines.

220
00:07:57,320 --> 00:07:59,680
It basically future-proofs your automation.

221
00:07:59,680 --> 00:08:01,920
The plugin system means you can, first off,

222
00:08:01,920 --> 00:08:04,000
run scripts in pretty much any language you like.

223
00:08:04,000 --> 00:08:08,920
Python, Node.js, R, Go, Shell, Java, even just SQL,

224
00:08:08,920 --> 00:08:11,460
whatever your team knows or what's best for the job.

225
00:08:11,460 --> 00:08:13,160
And you can run them anywhere.

226
00:08:13,160 --> 00:08:14,960
On the machine, Kestra is running on, sure,

227
00:08:14,960 --> 00:08:17,640
but also on remote servers using SSH,

228
00:08:17,640 --> 00:08:19,920
or scale out using containers with built-in Docker

229
00:08:19,920 --> 00:08:21,180
and Kubernetes support.

230
00:08:21,180 --> 00:08:22,600
Super versatile.

231
00:08:22,600 --> 00:08:25,440
But the real power is connecting to other systems.

232
00:08:25,440 --> 00:08:27,500
For instance, plugins let you extract and load data

233
00:08:27,500 --> 00:08:29,120
from a huge range of sources.

234
00:08:29,120 --> 00:08:32,200
We're talking traditional databases, Postgresql, MySlick,

235
00:08:32,200 --> 00:08:34,960
Oracle NoSQL ones like MongoDB or Redis,

236
00:08:34,960 --> 00:08:38,100
cloud storage like AWS S3, Google Cloud Storage,

237
00:08:38,100 --> 00:08:40,920
Azure Blob Storage, countless APIs.

238
00:08:40,920 --> 00:08:41,760
Wow.

239
00:08:41,760 --> 00:08:43,720
So you're pulling data from some old legacy system

240
00:08:43,720 --> 00:08:45,940
and mixing it with data from a modern cloud service.

241
00:08:45,940 --> 00:08:47,360
Kestra handles that.

242
00:08:47,360 --> 00:08:49,720
You can also set up flows to react to real-time events

243
00:08:49,720 --> 00:08:53,480
from message systems like Kafka, RabbitMQ, Redis Streams,

244
00:08:53,480 --> 00:08:56,360
or the big cloud ones, AWS SQS, Google PubSub,

245
00:08:56,360 --> 00:08:57,660
Azure Event Hubs.

246
00:08:57,660 --> 00:09:00,460
Imagine kicking off a fraud check instantly

247
00:09:00,460 --> 00:09:02,420
when a new transaction message appears.

248
00:09:02,420 --> 00:09:03,300
Yeah, powerful.

249
00:09:03,300 --> 00:09:05,540
And it deeply integrates with the major clouds,

250
00:09:05,540 --> 00:09:10,140
AWS, Google Cloud, Azure for everything,

251
00:09:10,140 --> 00:09:12,800
managing servers, triggering serverless functions,

252
00:09:12,800 --> 00:09:16,160
orchestrating data warehouses like Snowflake or Databricks,

253
00:09:16,160 --> 00:09:18,300
and of course, keeping people informed.

254
00:09:18,300 --> 00:09:20,440
There are tons of plugins for notifications,

255
00:09:20,440 --> 00:09:22,760
sending messages to Slack, Teams, email,

256
00:09:22,760 --> 00:09:24,840
even triggering alerts in PagerDuty

257
00:09:24,840 --> 00:09:27,440
so the right people know if something needs attention.

258
00:09:27,440 --> 00:09:30,060
Currently, there are over 600-plus plugins available,

259
00:09:30,060 --> 00:09:31,040
ready to go.

260
00:09:31,040 --> 00:09:32,480
Plus, users can build their own

261
00:09:32,480 --> 00:09:34,920
or contribute new ones back to the community.

262
00:09:34,920 --> 00:09:36,360
So yeah, the goal is really to connect

263
00:09:36,360 --> 00:09:38,360
to virtually anything you're already using.

264
00:09:38,360 --> 00:09:40,720
You're not locked in the one way of doing things.

265
00:09:40,720 --> 00:09:42,020
That level of connection,

266
00:09:42,020 --> 00:09:43,620
tying everything together like that,

267
00:09:43,620 --> 00:09:45,560
it sounds incredibly valuable.

268
00:09:45,560 --> 00:09:47,480
But okay, beyond just the tech specs,

269
00:09:47,480 --> 00:09:49,860
what does this all actually mean for the teams,

270
00:09:49,860 --> 00:09:51,920
the people using Kestra day-to-day?

271
00:09:51,920 --> 00:09:53,880
What's the real impact they're seeing?

272
00:09:53,880 --> 00:09:56,160
And who really benefits most?

273
00:09:56,160 --> 00:09:59,220
Yeah, it translates into some really significant,

274
00:09:59,220 --> 00:10:02,500
tangible benefits for a surprisingly wide range of people.

275
00:10:02,500 --> 00:10:06,020
Kestra positions itself as being for every developer.

276
00:10:06,020 --> 00:10:08,120
And that seems true.

277
00:10:08,120 --> 00:10:09,880
Data engineers building pipelines,

278
00:10:09,880 --> 00:10:13,080
software engineers orchestrating services or CICD,

279
00:10:13,080 --> 00:10:15,760
even marketing ops folks automating campaigns,

280
00:10:15,760 --> 00:10:18,920
platform engineers automating infrastructure.

281
00:10:18,920 --> 00:10:20,760
It really does help unify teams,

282
00:10:20,760 --> 00:10:23,180
breaks down those silos you sometimes see.

283
00:10:23,180 --> 00:10:25,440
What really scans out in feedback is how often users

284
00:10:25,440 --> 00:10:28,480
praise its simplicity and user experience.

285
00:10:28,480 --> 00:10:30,880
You hear things like beginner-friendly, so easy to use,

286
00:10:30,880 --> 00:10:34,680
fantastic web UI, extremely approachable and clear.

287
00:10:34,680 --> 00:10:36,760
People often say it's much simpler to get going with

288
00:10:36,760 --> 00:10:39,260
compared to alternatives like, say, Airflow or Prefect.

289
00:10:39,260 --> 00:10:40,100
Right.

290
00:10:40,100 --> 00:10:42,580
And that simplicity, it's not just nice to have,

291
00:10:42,580 --> 00:10:45,160
it directly leads to faster time to value.

292
00:10:45,160 --> 00:10:47,720
We see reports from companies saying they deliver in days

293
00:10:47,720 --> 00:10:49,080
what once took weeks,

294
00:10:49,080 --> 00:10:51,680
achieving things like 5x deployment speed.

295
00:10:51,680 --> 00:10:53,840
That points to less time fighting the tool,

296
00:10:53,840 --> 00:10:55,560
more time building the actual solution.

297
00:10:55,560 --> 00:10:56,840
Definitely a plus.

298
00:10:56,840 --> 00:11:00,520
And you see big jumps in productivity and efficiency.

299
00:11:00,520 --> 00:11:02,880
Things like 10x faster workflow completion,

300
00:11:02,880 --> 00:11:05,120
an 80% boost in team efficiency,

301
00:11:05,120 --> 00:11:08,320
even a 75% reduction in operational cost

302
00:11:08,320 --> 00:11:10,840
by automating stuff that was manual before.

303
00:11:10,840 --> 00:11:12,640
It's also built for scalability.

304
00:11:12,640 --> 00:11:14,860
It's proven to handle millions of workflows

305
00:11:14,860 --> 00:11:16,160
in production environments

306
00:11:16,160 --> 00:11:19,040
with over 400 million plus workflows executed

307
00:11:19,040 --> 00:11:22,280
across its user base so it can handle serious load.

308
00:11:22,280 --> 00:11:25,800
Plus, that flexibility and no vendor lock-in is key.

309
00:11:25,800 --> 00:11:27,640
Write your logic in any language,

310
00:11:27,640 --> 00:11:29,880
deploy Kestra wherever makes sense for you,

311
00:11:29,880 --> 00:11:33,720
on-prem, hybrid cloud, any major cloud provider you choose.

312
00:11:33,720 --> 00:11:36,400
That's important. Yeah, and to make starting even easier,

313
00:11:36,400 --> 00:11:38,980
there are over 250 plus blueprints.

314
00:11:38,980 --> 00:11:41,100
These are like pre-built templates for common tasks,

315
00:11:41,100 --> 00:11:43,880
pulling data from Salesforce to Snowflake, for example.

316
00:11:43,880 --> 00:11:45,580
There's likely a blueprint that gets you

317
00:11:45,580 --> 00:11:47,800
like 90% of the way there straight away.

318
00:11:47,800 --> 00:11:50,520
Okay, those blueprints sound like a great starting point.

319
00:11:50,520 --> 00:11:53,480
Well, that paints a really comprehensive picture

320
00:11:53,480 --> 00:11:57,760
from taming that initial chaos of complex processes

321
00:11:57,760 --> 00:12:00,840
to enabling really powerful, flexible,

322
00:12:00,840 --> 00:12:04,560
but also it seems surprisingly easy to manage automation.

323
00:12:04,560 --> 00:12:06,740
Kestra really does seem to cover a lot of ground.

324
00:12:06,740 --> 00:12:10,440
That unique mix of everything is code and from the UI,

325
00:12:10,440 --> 00:12:12,360
the huge plugin ecosystem,

326
00:12:12,360 --> 00:12:15,680
and just that focus on making orchestration accessible,

327
00:12:15,680 --> 00:12:17,800
those are clearly its big strengths.

328
00:12:17,800 --> 00:12:19,480
Sounds like a potential game changer

329
00:12:19,480 --> 00:12:21,840
for teams maybe struggling with their current tools.

330
00:12:21,840 --> 00:12:24,640
Absolutely, and this kind of leads to an important question

331
00:12:24,640 --> 00:12:27,440
maybe for you, our listener, to think about.

332
00:12:27,440 --> 00:12:30,440
What repetitive task, what complex data flow,

333
00:12:30,440 --> 00:12:32,040
or maybe what integration challenge

334
00:12:32,040 --> 00:12:33,640
exists in your world right now

335
00:12:33,640 --> 00:12:35,280
that could potentially be simplified,

336
00:12:35,280 --> 00:12:38,440
made more reliable, using a tool like Kestra.

337
00:12:38,440 --> 00:12:40,800
Is there something you do manually every week?

338
00:12:40,800 --> 00:12:43,100
Data stuck in silos that needs connecting.

339
00:12:43,100 --> 00:12:45,360
If you are curious and you want to see it in action,

340
00:12:45,360 --> 00:12:46,880
you can actually try their live demo.

341
00:12:46,880 --> 00:12:48,040
There's no installation needed,

342
00:12:48,040 --> 00:12:49,580
you just play with it in your browser.

343
00:12:49,580 --> 00:12:50,680
Or if you want to get hands on,

344
00:12:50,680 --> 00:12:52,920
check out the quick start installation guide.

345
00:12:52,920 --> 00:12:54,480
It literally takes about five minutes

346
00:12:54,480 --> 00:12:56,560
to get it running locally with Docker.

347
00:12:56,560 --> 00:13:00,880
You'll have the Kestra UI up at http.localhost.8080.

348
00:13:00,880 --> 00:13:03,840
And definitely check out their community on Slack and YouTube.

349
00:13:03,840 --> 00:13:05,880
Lots of help, lots of examples there too.

350
00:13:05,880 --> 00:13:07,520
Great resources.

351
00:13:07,520 --> 00:13:09,880
And remember, this deep dive was made possible

352
00:13:09,880 --> 00:13:11,720
thanks to the support of Safe Server.

353
00:13:11,720 --> 00:13:13,580
They're your partner for robust hosting

354
00:13:13,580 --> 00:13:16,840
and really seamless digital transformation solutions.

355
00:13:16,840 --> 00:13:21,480
Do visit www.safeserver.de to learn more about them.

356
00:13:21,480 --> 00:13:22,560
Thank you so much for joining us

357
00:13:22,560 --> 00:13:23,960
on this deep dive into Kestra.

358
00:13:23,960 --> 00:13:26,460
We look forward to exploring another fascinating topic