In production

SmartStream

SaaS platform, event capture and delivery

People learn from what they just did, not from what somebody tells them about it hours later. SmartStream puts the recording of a session in the participant's own account within minutes of it ending, so they can watch it, see what to change, and change it on the next attempt the same day.

Built with touch and go Paragliding, and now offered to other organisations.

One day of training

Before

Session 1

Session 2

Session 3

End of day: verbal feedback

Applied tomorrow, from memory

With SmartStream

Session 1, then watch it

Session 2, corrected

Session 3, corrected again

Feedback lands while it is still relevant

Three improvements in one day

Minutes, not daysbetween doing something and reviewing it
Zero manual handlingof video, after the event is set up
In productionwith real organisations and real participants

The real win

The feedback loop closes inside the same day

The organisations using it report the same thing: the value is not that files arrive faster, it is that a participant can study their own material between one session and the next. The debrief used to come at the end of the day, and be applied the next morning from memory. Now the correction lands on the very next attempt.

  • A participant reviews what they just did before they do it again
  • An instructor points at a moment instead of describing it
  • Three attempts in a day become three improvements, not one
  • Nothing waits for the end of the day, and nothing has to be remembered overnight

Not my claim

The school says this on their own sales page

The clearest description of what SmartStream changes was not written by me. It is on the public page the school uses to sell the training, where they have every reason to be accurate about what a participant actually gets.

touch and go Paragliding, on paragliding.ch

“A few minutes after landing you get your personal flight video straight onto your phone.”

“You do not have to wait until the evening or the end of the course. You can apply the recommendations on your very next flight, which makes the learning noticeably faster and more lasting.”

Translated from German. The same page calls it a world first in paragliding safety training, lists data-protection compliance among the participant benefits, and links to AEP Consulting as the developer. Read it on their site

What disappears

Nobody processes video by hand any more

Set up the event and the people in it, and that is the last manual step. Recording, upload, processing, matching to the right person and release into their account all happen without anybody in the middle.

  • No cards read into a laptop, no renaming, no folders per person
  • No links sent one by one, and no chasing the ones that bounced
  • No evening spent on it, and no backlog when a busy day ends
  • Setting up the next event takes minutes, not a spreadsheet

From the field to the participant

Recordedoffline capable
Uploadedon its own
Processedserver side
In their accountone person only

Nobody presses anything between the first box and the last. Upload speed follows the connection: the platform measures how the last upload went and tunes the next one.

Told where they already are

A notification is only useful if it reaches somebody

Email is always on. Beyond that, a participant chooses their own channel and links it themselves, so the message arrives where they actually look rather than where it was convenient to send it.

  • Transactional email, tracked so a failed delivery is visible rather than assumed
  • Telegram and Signal, linked by the participant with a one-time code, and unlinked the same way
  • Bot logic built in house, not a third party sitting between you and your participants
  • Every language the platform speaks, in the interface and in the messages
ChannelWho decides
EmailAlways on
TelegramThe participant
SignalThe participant
Leaving a channelOne message, any time

Two portals, and privacy by design

An organiser and a participant are not the same person with different rights

They are two products with two jobs. Building them as one screen with permissions on top is how private material ends up in front of the wrong person, so here the separation sits in the data model. The material is people, recorded, usually while they are learning something, and it was treated as personal data from the first version rather than from the first complaint.

  • The organiser has their own login: events, participants, recordings and access in one place
  • The participant has their own portal, with an account created from the invitation and no forms to fight
  • Each person sees what is theirs, and there is no screen anywhere in the product where one participant could see another's material
  • Each organisation is isolated from every other one, in the model and not in a filter
  • A participant can ask for their data to be deleted, and there is a process behind that request
  • The terms and the privacy notice are recorded as accepted at a specific version, so what somebody agreed to is not a matter of memory

Under it

A year of work, mostly on the parts nobody sees

An upload queue that survives a restart. Media processing that blocks nothing. Separation between organisations and between people as a fact rather than a filter. And an installed app that will not update itself in the middle of a recording, because that is the moment it would matter most.

Offline-capable captureResumable upload, tuned to the connectionServer-side processingMulti-tenant by designSeparate participant portalEmail, Telegram, SignalMultilingualInstallable appAutomated test suite

See it running, on your own event

A live demo takes twenty minutes. A demo account lets you set up an event and watch the whole thing happen without anybody touching a file.