About StreamUP

We build the OBS tools we wanted for our own streams

StreamUP is 4 people who stream, and who kept hitting the same walls in OBS. Rather than put up with them, we started building our way out. Everything here got made because one of us needed it on a Tuesday night.

The team

Who actually makes this

4 of us, spread across the UK and the Netherlands. All of us stream.

Andi, who streams as Andilippi

Andi

/Andilippi

Based in the UK. Makes the effects and widgets, and the tutorials that go with them. Spends most of his week on YouTube and live on Twitch helping people get their setups working.

Socials →
Silver, who streams as Silverlink

Silver

/Silverlink

DevOps engineer from the Netherlands, and the reason a lot of this holds together. Streams 3 times a week. Mostly third‑person action, easily jumpscared, fond of weird noises.

Socials →
TD, who streams as CodeWithTD

TD

/CodeWithTD

UK‑based coder, fluent in C#, JavaScript and GDScript. Has built a pile of Streamer.bot extensions and streams the coding sessions while he does it, which is how most of them get tested.

Socials →
Waldo, who streams as WaldoAndFriends

Waldo

/WaldoAndFriends

Software developer by day, Twitch streamer by night, also from the Netherlands. Plays family‑friendly, story‑driven games, dabbles in horror, and adds interactivity to everything he touches.

Socials →
What we believe

The rules we build to

4 things we argue about often enough that they may as well be written down.

OBS can already do it

Most tools drop a browser source on top of OBS and leave it there. We would rather use what OBS and Streamer.bot already do well, natively, even when that is the slower way to build something.

If you cannot change it, it is not yours

Colours, sounds, timing, triggers. Every one of them should be yours to move. An overlay you cannot touch is our design with your name on it, and there are already plenty of those.

Show the working

Our OBS plugins are open source on GitHub and the docs are public. When something is broken we say it is broken, rather than quietly shipping a fix and hoping nobody noticed.

Nobody learns from a settings panel

Half the job is the tutorial that goes with the thing. If it takes a video and a docs page before it makes sense, that video and that page are part of the product, not an afterthought.

How it works

Most of it starts in Discord

Someone complains about a thing OBS will not do. Someone else says they have hit that too. A few weeks later it exists. That is genuinely the process, and it is the reason the Discord matters more to us than any roadmap.

Come and moan at us