1
00:00:00,000 --> 00:00:04,700
Okay. So if you've ever planned, you know, a pretty significant event, could be

2
00:00:04,700 --> 00:00:10,530
anything, a marathon, a big conference, maybe even just a local workshop series,

3
00:00:10,530 --> 00:00:15,340
you definitely know that feeling of being kind of handcuffed by your ticketing

4
00:00:15,340 --> 00:00:15,800
provider.

5
00:00:15,800 --> 00:00:17,880
Absolutely. Those hidden fees that just pop up.

6
00:00:17,880 --> 00:00:21,600
Right. Or having basically zero ability to make it look like your brand.

7
00:00:21,600 --> 00:00:26,380
And the worst part? Maybe. Waiting weeks, sometimes longer, just to get the money

8
00:00:26,380 --> 00:00:27,680
from your ticket sales.

9
00:00:27,720 --> 00:00:32,960
Oh, that waiting period. It really shifts all the financial risk onto you, the

10
00:00:32,960 --> 00:00:33,960
organizer, doesn't it?

11
00:00:33,960 --> 00:00:39,410
It does. You end up having to float cash for everything, marketing, logistics,

12
00:00:39,410 --> 00:00:43,160
venue deposits, all while the platform sits on your income.

13
00:00:43,160 --> 00:00:46,680
It feels like a really bad trade off. You get maybe some convenience from a big

14
00:00:46,680 --> 00:00:49,360
platform, but you lose so much financial control.

15
00:00:49,360 --> 00:00:51,920
Exactly. An unacceptable trade off for many.

16
00:00:51,960 --> 00:00:56,230
But that's why we're here today. We are diving deep into a tool that's really built

17
00:00:56,230 --> 00:00:59,040
from the ground up to fix those specific problems.

18
00:00:59,040 --> 00:01:02,280
It puts the organizer, meaning you, the listener first.

19
00:01:02,280 --> 00:01:03,120
That's promising.

20
00:01:03,120 --> 00:01:07,060
We're exploring high events. It's billed as a comprehensive, open source event

21
00:01:07,060 --> 00:01:11,580
management and ticket selling platform, and it seems to be making waves already got

22
00:01:11,580 --> 00:01:14,400
over, what, 3,200 stars on GitHub?

23
00:01:14,400 --> 00:01:18,570
Yeah, that's significant traction in the open source space. Shows there's real

24
00:01:18,570 --> 00:01:19,200
interest.

25
00:01:19,240 --> 00:01:23,170
Before we jump into the details though, we really want to thank the supporter who

26
00:01:23,170 --> 00:01:25,400
makes this whole deep dive possible today.

27
00:01:25,400 --> 00:01:27,920
Our exploration is supported by Safe Server.

28
00:01:27,920 --> 00:01:31,880
They handle the hosting for software like this and can really support your digital

29
00:01:31,880 --> 00:01:32,920
transformation.

30
00:01:32,920 --> 00:01:37,280
You can find out more at www.safeserver.de.

31
00:01:37,280 --> 00:01:39,160
So our mission today is pretty straightforward.

32
00:01:39,160 --> 00:01:44,180
We need to unpack what high events actually is, explain how this whole open source

33
00:01:44,180 --> 00:01:48,320
idea applies in the world of event ticketing, which maybe isn't obvious.

34
00:01:48,360 --> 00:01:52,980
And crucially highlight the features that could make this a genuine game changer,

35
00:01:52,980 --> 00:01:55,730
especially if you're just starting out organizing events and need something

36
00:01:55,730 --> 00:01:56,200
flexible.

37
00:01:56,200 --> 00:02:00,600
And I think what's really key here based on the sources is this idea of freedom.

38
00:02:00,600 --> 00:02:05,140
It's not just presented as a cheaper option, but as a complete toolbox designed for

39
00:02:05,140 --> 00:02:07,880
you to own long term, not just rent short term.

40
00:02:07,880 --> 00:02:09,000
OK, let's start right there.

41
00:02:09,000 --> 00:02:17,480
Segment one, the core pitch, open source, low fees and getting your money fast.

42
00:02:17,520 --> 00:02:21,680
So in simple terms, what exactly is high events?

43
00:02:21,680 --> 00:02:23,920
Well, think of it as a feature packed platform.

44
00:02:23,920 --> 00:02:26,440
It's open source. You can host it yourself if you want.

45
00:02:26,440 --> 00:02:31,570
And it handles pretty much the whole event lifecycle management, online ticket

46
00:02:31,570 --> 00:02:35,400
sales, works for small workshops, works for huge music festivals.

47
00:02:35,400 --> 00:02:37,280
Right. But you mentioned self hosted.

48
00:02:37,280 --> 00:02:41,030
And I know for some organizers, especially beginners, that might immediately sound

49
00:02:41,030 --> 00:02:42,360
daunting, too technical.

50
00:02:42,360 --> 00:02:44,000
And they've clearly thought about that.

51
00:02:44,040 --> 00:02:48,120
The platform offers two very distinct paths forward, which is, I think, crucial for

52
00:02:48,120 --> 00:02:49,360
making it accessible.

53
00:02:49,360 --> 00:02:51,880
That is key. Yeah, you don't need to be a server admin from day one.

54
00:02:51,880 --> 00:02:54,680
So what are those two paths for someone learning about this?

55
00:02:54,680 --> 00:02:59,440
OK, so the first one, this is the sort of low friction, easy entry option is the

56
00:02:59,440 --> 00:03:01,040
high events cloud.

57
00:03:01,040 --> 00:03:03,000
OK, it's fully managed by them.

58
00:03:03,000 --> 00:03:04,680
Zero installation for you.

59
00:03:04,680 --> 00:03:07,280
They handle the security, the scaling, the updates.

60
00:03:07,280 --> 00:03:10,680
You basically sign up, put your event details in and you can start selling tickets

61
00:03:10,680 --> 00:03:11,680
almost immediately.

62
00:03:11,720 --> 00:03:14,520
So kind of like the standard sauce model we see elsewhere.

63
00:03:14,520 --> 00:03:16,440
Focus on your event, not the tech.

64
00:03:16,440 --> 00:03:19,040
Exactly. That's the pitch for the cloud version.

65
00:03:19,040 --> 00:03:23,080
But the second path, that's where the open source power really comes in, right?

66
00:03:23,080 --> 00:03:24,000
The self-hosted option.

67
00:03:24,000 --> 00:03:25,000
Precisely.

68
00:03:25,000 --> 00:03:27,200
That's the core of the open source promise.

69
00:03:27,200 --> 00:03:28,960
No vendor lock-in.

70
00:03:28,960 --> 00:03:32,960
You get complete, like, 100% control over the whole system.

71
00:03:32,960 --> 00:03:34,560
Meaning you control your data.

72
00:03:34,560 --> 00:03:38,480
Your data, the look and feel when you update, everything.

73
00:03:38,520 --> 00:03:43,040
And the beauty is, a beginner could start with the cloud for convenience,

74
00:03:43,040 --> 00:03:45,560
but then maybe as they grow,

75
00:03:45,560 --> 00:03:49,200
or if they need really deep integration with other systems they use,

76
00:03:49,200 --> 00:03:52,640
they have the option to migrate to the self-hosted version later

77
00:03:52,640 --> 00:03:54,600
without losing everything and starting over.

78
00:03:54,600 --> 00:03:55,760
Okay, that makes sense.

79
00:03:55,760 --> 00:03:56,800
Now let's talk money,

80
00:03:56,800 --> 00:04:00,400
because this is where things get potentially very attractive.

81
00:04:00,400 --> 00:04:04,280
The sources mention this claim of being 70% cheaper than competitors.

82
00:04:04,280 --> 00:04:05,320
Does that really hold up?

83
00:04:05,320 --> 00:04:06,680
Where do those savings come from?

84
00:04:06,720 --> 00:04:09,960
It seems to hold up primarily because their fee structure

85
00:04:09,960 --> 00:04:12,720
is just fundamentally different, is really lean.

86
00:04:12,720 --> 00:04:15,840
Well, first off, if you're running free events, completely free,

87
00:04:15,840 --> 00:04:18,080
zero platform fees from high events.

88
00:04:18,080 --> 00:04:19,480
Okay, that's a good start.

89
00:04:19,480 --> 00:04:22,320
And for paid events, where competitors might charge, you know,

90
00:04:22,320 --> 00:04:26,800
3.5%, 4%, maybe even more, plus a hefty fixed fee per ticket.

91
00:04:26,800 --> 00:04:28,480
Yeah, those can add up fast.

92
00:04:28,480 --> 00:04:33,760
High events charges just 0.75% plus a flat 0.40 cents per ticket.

93
00:04:33,800 --> 00:04:40,520
Wow, okay, 0.75% plus 40 cents versus potentially 4% plus maybe a dollar or more.

94
00:04:40,520 --> 00:04:41,240
Exactly.

95
00:04:41,240 --> 00:04:43,240
That is, that's not just a small difference.

96
00:04:43,240 --> 00:04:46,440
On a large event, say 5,000 attendees,

97
00:04:46,440 --> 00:04:50,920
that could easily mean tens of thousands of dollars staying in the organizer's

98
00:04:50,920 --> 00:04:51,320
pocket.

99
00:04:51,320 --> 00:04:54,760
Absolutely. It goes straight back into your event budget or your bottom line.

100
00:04:54,760 --> 00:04:58,480
And the financial perks don't actually stop at just the low fees.

101
00:04:58,480 --> 00:05:00,360
They integrate directly with Stripe Connect.

102
00:05:00,360 --> 00:05:02,960
And the crucial benefit here is instant payouts.

103
00:05:03,000 --> 00:05:04,520
Instant, like really instant.

104
00:05:04,520 --> 00:05:05,840
Pretty much. You don't wait two weeks.

105
00:05:05,840 --> 00:05:07,560
You don't even wait two days, typically.

106
00:05:07,560 --> 00:05:08,880
As soon as someone buys a ticket,

107
00:05:08,880 --> 00:05:11,120
that revenue becomes available to you through Stripe.

108
00:05:11,120 --> 00:05:15,160
OK, that directly tackles that cash flow problem we mentioned right at the start.

109
00:05:15,160 --> 00:05:18,480
No more floating costs while waiting for a payout.

110
00:05:18,480 --> 00:05:22,120
Exactly. It solves a huge operational headache for organizers.

111
00:05:22,120 --> 00:05:24,640
All right. So it's cheaper. You get your money faster.

112
00:05:24,640 --> 00:05:28,240
That brings us to segment two, the features.

113
00:05:28,240 --> 00:05:30,160
If you're saving that much money,

114
00:05:30,200 --> 00:05:35,430
are you losing out on the tools that professional organizers actually need day to

115
00:05:35,430 --> 00:05:35,800
day?

116
00:05:35,800 --> 00:05:37,720
That's always the question, isn't it?

117
00:05:37,720 --> 00:05:41,520
But looking at the feature list, it seems surprisingly comprehensive.

118
00:05:41,520 --> 00:05:42,840
They haven't skimped.

119
00:05:42,840 --> 00:05:44,560
So what kind of tools are we talking about?

120
00:05:44,560 --> 00:05:49,200
Things that maybe other platforms hide behind higher tiers or charge extra for?

121
00:05:49,200 --> 00:05:52,480
Well, the ticketing flexibility seems really strong.

122
00:05:52,480 --> 00:05:56,480
You can create multiple ticket types, easily standard, paid ones, obviously,

123
00:05:56,520 --> 00:06:01,560
free tickets, donation-based tickets, even tiered tickets like early bird or VIP.

124
00:06:01,560 --> 00:06:03,840
OK, standard stuff, but necessary.

125
00:06:03,840 --> 00:06:05,720
What about marketing tools around tickets?

126
00:06:05,720 --> 00:06:09,240
Yep. They've got promo codes covered for discounts or pre-sales

127
00:06:09,240 --> 00:06:11,280
and something called advanced ticket locking.

128
00:06:11,280 --> 00:06:12,720
Ticket locking. What's that?

129
00:06:12,720 --> 00:06:15,040
It means you can restrict certain ticket types.

130
00:06:15,040 --> 00:06:19,320
So they're only visible or purchasable if someone enters a specific code.

131
00:06:19,320 --> 00:06:22,400
Good for member only sales, sponsor tickets, that sort of thing.

132
00:06:22,400 --> 00:06:24,040
Ah, gotcha. OK.

133
00:06:24,040 --> 00:06:26,400
What about managing attendance numbers?

134
00:06:26,440 --> 00:06:29,520
Capacity can be tricky, especially with different ticket types

135
00:06:29,520 --> 00:06:31,760
maybe sharing the same space.

136
00:06:31,760 --> 00:06:33,400
Right. And they seem to handle that well.

137
00:06:33,400 --> 00:06:35,400
You've got fine-grained capacity management.

138
00:06:35,400 --> 00:06:38,760
You can set an overall event limit or limits on individual ticket types.

139
00:06:38,760 --> 00:06:43,360
OK. But the really neat feature is what they call capacity assignments.

140
00:06:43,360 --> 00:06:45,160
Imagine you have a conference, right?

141
00:06:45,160 --> 00:06:47,160
And maybe there are three workshops happening,

142
00:06:47,160 --> 00:06:52,320
but the total room capacity for all workshop attendees combined is, say, 200.

143
00:06:52,320 --> 00:06:54,880
Right. You don't want to sell 100 tickets for each workshop

144
00:06:54,920 --> 00:06:57,280
if the total space only holds 200.

145
00:06:57,280 --> 00:07:00,320
Exactly. This system lets you link those different workshop

146
00:07:00,320 --> 00:07:02,680
tickets to a shared capacity pool.

147
00:07:02,680 --> 00:07:06,760
It tracks the total sold across all link types, preventing overselling.

148
00:07:06,760 --> 00:07:10,680
That's actually really smart for multi-track events or complex setups.

149
00:07:10,680 --> 00:07:13,560
OK. Beyond just getting people in, what about other revenue streams?

150
00:07:13,560 --> 00:07:16,280
Can you sell, like, merch or add-ons?

151
00:07:16,280 --> 00:07:19,040
Yep. There's a built-in product sales feature.

152
00:07:19,040 --> 00:07:21,800
So you can easily add t-shirts, books, parking passes,

153
00:07:21,800 --> 00:07:24,080
whatever extras you want to offer alongside the tickets.

154
00:07:24,120 --> 00:07:27,000
And taxes, fees. That gets complicated.

155
00:07:27,000 --> 00:07:28,800
They seem to cover that, too.

156
00:07:28,800 --> 00:07:34,160
You can apply custom taxes and fees either per product or on the entire order.

157
00:07:34,160 --> 00:07:36,320
That's pretty essential for proper accounting,

158
00:07:36,320 --> 00:07:39,240
especially for larger organizations dealing with different tax rules.

159
00:07:39,240 --> 00:07:40,600
Oh, certainly.

160
00:07:40,600 --> 00:07:43,160
OK. Shifting focus a bit to the attendee side.

161
00:07:43,160 --> 00:07:45,160
What's the experience like for them?

162
00:07:45,160 --> 00:07:47,480
And what control do you have over their data?

163
00:07:47,480 --> 00:07:49,960
I remember needing very specific info once,

164
00:07:49,960 --> 00:07:52,720
like meal choices or accessibility needs.

165
00:07:52,760 --> 00:07:56,120
Well, first big point is data ownership,

166
00:07:56,120 --> 00:07:58,360
especially with the self-hosted option. It's your data.

167
00:07:58,360 --> 00:07:59,000
Right.

168
00:07:59,000 --> 00:08:02,280
And to collect it, you can design custom checkout forms,

169
00:08:02,280 --> 00:08:03,880
ask exactly the questions you need,

170
00:08:03,880 --> 00:08:08,080
dietary needs, t-shirt sizes, how did you hear about us, anything.

171
00:08:08,080 --> 00:08:08,880
Nice.

172
00:08:08,880 --> 00:08:11,680
And after they've bought the ticket, managing attendees.

173
00:08:11,680 --> 00:08:12,640
Seems robust.

174
00:08:12,640 --> 00:08:15,520
You get attendee management tools to easily search for people,

175
00:08:15,520 --> 00:08:19,200
edit their details if needed, cancel orders, issue refunds.

176
00:08:19,200 --> 00:08:21,240
Pretty standard, but essential stuff.

177
00:08:21,280 --> 00:08:23,120
What about communicating with them?

178
00:08:23,120 --> 00:08:26,600
Say, last minute change, maybe a speaker cancellation,

179
00:08:26,600 --> 00:08:29,960
and you only want to email the people who signed up for that specific session.

180
00:08:29,960 --> 00:08:32,080
Yeah, they have a bulk messaging tool for that.

181
00:08:32,080 --> 00:08:34,800
You can filter your attendee list by ticket type

182
00:08:34,800 --> 00:08:37,000
or maybe by custom question answers

183
00:08:37,000 --> 00:08:40,600
and send targeted emails or messages just to that specific group.

184
00:08:40,600 --> 00:08:43,240
That kind of targeted communication is gold,

185
00:08:43,240 --> 00:08:46,280
especially when things change quickly near the event date.

186
00:08:46,280 --> 00:08:47,360
Absolutely.

187
00:08:47,360 --> 00:08:50,360
And one more thing on the attendee front for international reach.

188
00:08:50,400 --> 00:08:53,200
It supports multiple languages out of the box.

189
00:08:53,200 --> 00:08:57,600
English, German, Spanish, Portuguese, French, several others.

190
00:08:57,600 --> 00:08:59,320
OK, that's a solid base.

191
00:08:59,320 --> 00:09:03,320
Let's move into segment three, customization and actually using the tech.

192
00:09:03,320 --> 00:09:06,920
One of the biggest gripes with older platforms is always the branding.

193
00:09:06,920 --> 00:09:09,160
Looks dated, doesn't match your site.

194
00:09:09,160 --> 00:09:12,480
The sources say, hi, events offers complete design control.

195
00:09:12,480 --> 00:09:14,600
How does that work in practice?

196
00:09:14,600 --> 00:09:17,960
They seem to focus on making powerful tools intuitive.

197
00:09:17,960 --> 00:09:19,560
There's a homepage designer, for instance.

198
00:09:19,600 --> 00:09:23,320
It's a visual editor, live preview lets you tweak colors, layouts,

199
00:09:23,320 --> 00:09:26,400
add your branding elements, all without needing to write code.

200
00:09:26,400 --> 00:09:28,880
So you can make the event page itself look good.

201
00:09:28,880 --> 00:09:32,760
But what if I already have a great website for my organization or event?

202
00:09:32,760 --> 00:09:37,040
I don't want to send people off to some high dot events, my event page necessarily.

203
00:09:37,040 --> 00:09:38,200
Totally understandable.

204
00:09:38,200 --> 00:09:40,480
And that's where their embeddable ticket widget comes in.

205
00:09:40,480 --> 00:09:41,440
Oh, OK.

206
00:09:41,440 --> 00:09:45,400
It's designed to let you drop the entire ticket selection and checkout process

207
00:09:45,400 --> 00:09:47,560
right onto your existing website.

208
00:09:47,600 --> 00:09:52,360
They say it works easily with common platforms like React, WordPress, Wix, Squarespace.

209
00:09:52,360 --> 00:09:53,320
How easy?

210
00:09:53,320 --> 00:09:55,160
Like copy paste a code snippet.

211
00:09:55,160 --> 00:09:56,280
Pretty much.

212
00:09:56,280 --> 00:09:57,680
Just a few lines of code.

213
00:09:57,680 --> 00:10:00,760
And the widget appears seamlessly within your site's design.

214
00:10:00,760 --> 00:10:02,840
Keeps the whole journey feeling professional

215
00:10:02,840 --> 00:10:05,400
and maintains your brand identity from start to finish.

216
00:10:05,400 --> 00:10:07,720
That's huge for user experience.

217
00:10:07,720 --> 00:10:09,840
OK, fast forward to the event day itself.

218
00:10:09,840 --> 00:10:11,080
Doors open.

219
00:10:11,080 --> 00:10:13,200
How smooth is the check-in process?

220
00:10:13,200 --> 00:10:17,320
They seem to prioritize simplicity in using readily available tech.

221
00:10:17,360 --> 00:10:20,680
Entry management is done via QR codes on the tickets.

222
00:10:20,680 --> 00:10:22,480
And check-in uses a web-based tool.

223
00:10:22,480 --> 00:10:25,440
It's mobile-friendly, so your staff can use phones or tablets.

224
00:10:25,440 --> 00:10:28,800
No need for special hardware or installing specific native apps.

225
00:10:28,800 --> 00:10:30,000
That's convenient.

226
00:10:30,000 --> 00:10:32,000
Less hassle for the check-in crew.

227
00:10:32,000 --> 00:10:33,240
What about managing that crew?

228
00:10:33,240 --> 00:10:35,120
If I have volunteers checking people in,

229
00:10:35,120 --> 00:10:37,400
maybe someone else handling issues at a help desk.

230
00:10:37,400 --> 00:10:40,760
They've got multi-user access with role-based controls.

231
00:10:40,760 --> 00:10:43,920
Meaning you can create different accounts for your staff members

232
00:10:43,920 --> 00:10:46,080
and assign specific permissions.

233
00:10:46,120 --> 00:10:49,320
So check-in staff might only have access to scan tickets

234
00:10:49,320 --> 00:10:51,080
for a specific entry point,

235
00:10:51,080 --> 00:10:54,840
while a manager might have rights to look up orders or issue refunds.

236
00:10:54,840 --> 00:10:58,360
Ensures people only see and do what they need to.

237
00:10:58,360 --> 00:11:00,920
Good for security and organization.

238
00:11:00,920 --> 00:11:03,920
Okay, let's circle back quickly to that self-hosting option.

239
00:11:03,920 --> 00:11:05,760
We know the cloud version is easy,

240
00:11:05,760 --> 00:11:08,640
but for the organizer who wants that ultimate control,

241
00:11:08,640 --> 00:11:10,400
maybe integrate it deeply,

242
00:11:10,400 --> 00:11:13,920
the platform uses tech like PHP and TypeScript.

243
00:11:13,960 --> 00:11:16,200
Is setting it up yourself a nightmare?

244
00:11:16,200 --> 00:11:18,120
You know, it seems surprisingly manageable,

245
00:11:18,120 --> 00:11:20,280
mainly because they've leaned heavily on Docker.

246
00:11:20,280 --> 00:11:21,840
Ah, Docker.

247
00:11:21,840 --> 00:11:23,240
For listeners who might not know,

248
00:11:23,240 --> 00:11:25,480
think of it like putting the entire application

249
00:11:25,480 --> 00:11:28,440
and all its requirements, the database, the web server settings,

250
00:11:28,440 --> 00:11:32,120
everything into a self-contained box, makes setup much simpler.

251
00:11:32,120 --> 00:11:33,440
That's a perfect analogy.

252
00:11:33,440 --> 00:11:37,360
So the main technical prerequisite is just having Docker and Docker Compose

253
00:11:37,360 --> 00:11:39,200
installed on your server or machine.

254
00:11:39,200 --> 00:11:39,880
And then?

255
00:11:39,920 --> 00:11:44,830
The quick start guide basically boils down to clone their code repository from

256
00:11:44,830 --> 00:11:45,880
GitHub,

257
00:11:45,880 --> 00:11:47,600
navigate into the directory,

258
00:11:47,600 --> 00:11:50,280
run a command to generate a couple of unique security keys.

259
00:11:50,280 --> 00:11:50,720
Okay.

260
00:11:50,720 --> 00:11:55,080
And then run one single command, Docker Compose up E or D.

261
00:11:55,080 --> 00:11:58,240
And that should, in theory, build and start everything needed.

262
00:11:58,240 --> 00:12:00,560
So while there's some technical understanding needed,

263
00:12:00,560 --> 00:12:02,520
it's not like you're manually installing

264
00:12:02,520 --> 00:12:05,640
and configuring dozens of separate software components.

265
00:12:05,640 --> 00:12:06,520
Exactly.

266
00:12:06,520 --> 00:12:08,320
Docker streamlines it significantly.

267
00:12:08,320 --> 00:12:08,680
Yeah.

268
00:12:08,720 --> 00:12:10,960
This self-hosting path is definitely for those

269
00:12:10,960 --> 00:12:12,640
who want that absolute control,

270
00:12:12,640 --> 00:12:14,760
maybe want to customize the code itself,

271
00:12:14,760 --> 00:12:17,080
own their data infrastructure completely,

272
00:12:17,080 --> 00:12:19,720
and have zero reliance on the high events company

273
00:12:19,720 --> 00:12:21,080
for the software hosting.

274
00:12:21,080 --> 00:12:22,760
It's about enabling true ownership.

275
00:12:22,760 --> 00:12:23,640
Right.

276
00:12:23,640 --> 00:12:24,920
Okay, let's wrap this up.

277
00:12:24,920 --> 00:12:26,200
Outro time.

278
00:12:26,200 --> 00:12:27,240
So putting it all together,

279
00:12:27,240 --> 00:12:29,160
what does high events really mean for you,

280
00:12:29,160 --> 00:12:31,240
the event organizer, listening right now?

281
00:12:31,240 --> 00:12:33,840
Well, it seems to deliver on some critical points.

282
00:12:33,840 --> 00:12:36,040
First, potentially serious cost savings

283
00:12:36,080 --> 00:12:39,960
with that claimed 70% cheaper fee structure

284
00:12:39,960 --> 00:12:41,040
compared to the big guys.

285
00:12:41,040 --> 00:12:42,280
Definitely a major draw.

286
00:12:42,280 --> 00:12:45,280
Second, much more control over design, branding,

287
00:12:45,280 --> 00:12:46,840
and how you integrate ticketing

288
00:12:46,840 --> 00:12:48,920
into your existing online presence.

289
00:12:48,920 --> 00:12:50,760
Through things like the embeddable widget.

290
00:12:50,760 --> 00:12:51,520
Exactly.

291
00:12:51,520 --> 00:12:53,640
And third, real flexibility.

292
00:12:53,640 --> 00:12:56,360
You can choose the convenience of their cloud service to start,

293
00:12:56,360 --> 00:12:58,440
or you can go for total ownership and control

294
00:12:58,440 --> 00:13:00,600
with the self-hosted open source version.

295
00:13:00,600 --> 00:13:01,920
It looks built to scale,

296
00:13:01,920 --> 00:13:04,680
handling everything from, say, a local 10K race

297
00:13:04,720 --> 00:13:06,240
to a major nightclub opening.

298
00:13:06,240 --> 00:13:07,160
A wide range.

299
00:13:07,160 --> 00:13:09,040
And at least, and maybe a final thought,

300
00:13:09,040 --> 00:13:12,960
when a platform like this commits to being open source and self-hostable,

301
00:13:12,960 --> 00:13:14,840
it does something fundamental.

302
00:13:14,840 --> 00:13:17,120
It decentralizes the technology.

303
00:13:17,120 --> 00:13:20,520
It takes power away from just a few large platform providers.

304
00:13:20,520 --> 00:13:23,480
So the provocative question for you, the listener, is...

305
00:13:23,480 --> 00:13:26,320
What new opportunities does that level of software ownership

306
00:13:26,320 --> 00:13:28,040
actually create for you?

307
00:13:28,040 --> 00:13:31,960
Could you build truly unique, specialized experiences for your audience?

308
00:13:31,960 --> 00:13:34,560
Maybe integrate hyper-local payment methods?

309
00:13:34,600 --> 00:13:37,200
Develop custom features specific to your niche,

310
00:13:37,200 --> 00:13:41,250
all without ever worrying about being logged into a single platform's roadmap or

311
00:13:41,250 --> 00:13:42,280
pricing.

312
00:13:42,280 --> 00:13:45,760
That shift in control is potentially very powerful.

313
00:13:45,760 --> 00:13:47,600
Something definitely worth thinking about.

314
00:13:47,600 --> 00:13:50,320
If you're feeling constrained by your current ticketing setup,

315
00:13:50,320 --> 00:13:54,160
the source documentation for high events seems like a very worthwhile read.

316
00:13:54,160 --> 00:13:57,920
And one more time, a huge thank you to our supporter for this deep dive.

317
00:13:57,920 --> 00:14:00,680
SafeServer takes care of the hosting of this software

318
00:14:00,680 --> 00:14:03,480
and supports you in your digital transformation.

319
00:14:03,520 --> 00:14:06,600
More info is under www.SafeServer.de.

320
00:14:06,600 --> 00:14:08,600
Thanks for diving deep with us today.

321
00:14:08,600 --> 00:14:11,720
Until next time, keep creating those amazing event experiences.