Skip to content
Merged
Show file tree
Hide file tree
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions app/foundation/page.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -810,7 +810,7 @@ function ChapterHeader({
const CHAPTERS = [
{ num: "01", label: "The Foundation" },
{ num: "02", label: "What We Do" },
{ num: "03", label: "The Network" },
{ num: "03", label: "The Project" },
// 04 / The Team is hidden until we have headshots — see the
// commented-out section in FoundationPage's render.
];
Expand Down Expand Up @@ -1177,8 +1177,8 @@ export default function FoundationPage() {
<div className="mx-auto max-w-3xl py-14 lg:py-40">
<ChapterHeader
num="03"
crumb="The Network"
title="About The Network"
crumb="The Project"
title="About The Project"
graphic={<NetworkGraphic />}
/>

Expand Down
52 changes: 52 additions & 0 deletions content/blog/builder-spotlight-frameworks.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
---
title: "Built from Inside the Stack"
description: "Building on Open Compute: Marco van Dijk, Founder of FrameWorks"
date: "2026-05-29"
category: "Ecosystem"
tags: ["builder-spotlight", "frameworks", "SPE", "live-streaming"]
image: "/images/blog/builder-spotlight-frameworks.svg"
imageAlt: "FrameWorks - Builder Spotlight"
draft: true
---
Comment on lines +1 to +10
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Add missing author in frontmatter.

The post frontmatter is missing author, which is required by the blog content contract.

✅ Suggested patch
 ---
 title: "Built from Inside the Stack"
 description: "Building on Open Compute: Marco van Dijk, Founder of FrameWorks"
 date: "2026-05-29"
+author: "Livepeer Team"
 category: "Ecosystem"
 tags: ["builder-spotlight", "frameworks", "SPE", "live-streaming"]
 image: "/images/blog/builder-spotlight-frameworks.svg"
 imageAlt: "FrameWorks - Builder Spotlight"
 draft: true
 ---

As per coding guidelines, “Blog posts must be written in markdown with YAML frontmatter (title, description, date, author, category, tags, image, draft)”.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
---
title: "Built from Inside the Stack"
description: "Building on Open Compute: Marco van Dijk, Founder of FrameWorks"
date: "2026-05-29"
category: "Ecosystem"
tags: ["builder-spotlight", "frameworks", "SPE", "live-streaming"]
image: "/images/blog/builder-spotlight-frameworks.svg"
imageAlt: "FrameWorks - Builder Spotlight"
draft: true
---
---
title: "Built from Inside the Stack"
description: "Building on Open Compute: Marco van Dijk, Founder of FrameWorks"
date: "2026-05-29"
author: "Livepeer Team"
category: "Ecosystem"
tags: ["builder-spotlight", "frameworks", "SPE", "live-streaming"]
image: "/images/blog/builder-spotlight-frameworks.svg"
imageAlt: "FrameWorks - Builder Spotlight"
draft: true
---
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@content/blog/builder-spotlight-frameworks.md` around lines 1 - 10, The YAML
frontmatter for the post titled "Built from Inside the Stack" is missing the
required author field; update the frontmatter block that contains
title/description/date/category/tags/image/draft to include an author: "<author
name or handle>" entry (e.g., author: "Marco van Dijk") so the file's
frontmatter satisfies the blog content contract; ensure the author key appears
alongside the existing keys and follows YAML formatting conventions.


Livepeer has had no shortage of builders over its nine-year history. Far fewer have worked on its core infrastructure from the inside, run a top-ranked orchestrator node on the supply side, and then founded a platform to succeed one of its flagship applications. Marco van Dijk has done all three.

![Marco van Dijk's timeline with Livepeer](/images/blog/builder-spotlight-frameworks/01_timeline.png)

Marco is a video streaming engineer and founder based in the Netherlands. His fingerprints are found across the Livepeer stack: in the media infrastructure that powered Studio, on the supply side as an independent GPU orchestrator, and now in **FrameWorks**, the next-generation live video platform built on Livepeer's open GPU network.

Marco has been building on Livepeer for five years. He arrived with an outsider's perspective on the network's capacity limits and a clear view of its potential to deliver a world-class streaming experience.

![Marco's contributions across the Livepeer stack](/images/blog/builder-spotlight-frameworks/02_stack.png)

## Skin in the game

Through his work with MistServer, an open source media toolkit, he contributed the backbone of Livepeer's original flagship product, Livepeer Studio. He built the ingest, real-time audio transcoding, protocol translation, transmuxing, VOD, and delivery capabilities that made up the lion's share of Studio's end-to-end live streaming infrastructure.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Use hyphenated compound adjective: open-source.

“open source media toolkit” should be “open-source media toolkit” when used before a noun.

🧰 Tools
🪛 LanguageTool

[grammar] ~24-~24: Use a hyphen to join words.
Context: ...hrough his work with MistServer, an open source media toolkit, he contributed the...

(QB_NEW_EN_HYPHEN)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@content/blog/builder-spotlight-frameworks.md` at line 24, In the sentence
inside builder-spotlight-frameworks.md that reads "open source media toolkit"
(the description of MistServer), change it to the hyphenated compound adjective
"open-source media toolkit" so the modifier used before the noun is
grammatically correct; ensure only that phrase is updated and surrounding
punctuation/spacing remains unchanged.


> "My work was already entangled with Livepeer through MistServer and the way I came to fully understand the protocol was by running it myself."

Marco soon came to understand Livepeer not just as a developer building on top of it, but as an operator with economic skin in the game. He spun up an orchestrator node, and what began as a way to learn how the pieces fit together quickly became something more serious: a top-ranked position, one of the largest independent stakes, and a community as passionate about tech and streaming as Marco was.

> "In December 2021 I brought a node online, mostly to learn how the supply side actually worked. It started as a way to learn. It did not stay that way. The first transcoding rewards rolled in and I came into contact with the community properly for the first time. I was overwhelmed by both their extreme hospitality and passion for discussing the tech. Pretty soon, I was hooked."

![Marco quote](/images/blog/builder-spotlight-frameworks/03_quote.png)

## Inspiration strikes

Marco's time working on the early network gave him a powerful combination of deep technical insight and the high-agency approach that only a founder-builder brings to complex advances like Livepeer's low-latency open compute stack. Not content with shaping Studio and running an orchestrator node, Marco started building a full media pipeline in 2023 to put himself in the position of a new broadcaster.

This experiment saw him wade deeper into the swirling waters of streaming at production scale, grappling with transcoding audio in real-time, transmuxing content between container formats and load-balancing across regions. These were productive years for Marco, during which he shipped a browser-based broadcast studio, network tooling, dashboards, orchestrator documentation, and **added text-to-video, picture-to-picture, and image-to-video to Livepeer's then-nascent AI capabilities.**

That's when the first seeds of FrameWorks came into being. The idea took shape in early 2025: **a fully self-contained, vertically integrated live video stack built on Livepeer, one that could handle ingest, transcoding, and delivery end-to-end, with Livepeer's open GPU network doing the heavy lifting.** A platform that realized the original Livepeer vision of open video infrastructure, from the encoder to the viewer's screen.

By February 2025, the proposal was [live on the Livepeer forum](https://forum.livepeer.org/t/pre-proposal-livepeer-frameworks-spe-pilot-phase/2773), and it soon received the community's endorsement. The build was underway.

![FrameWorks key capabilities](/images/blog/builder-spotlight-frameworks/04_keys.png)

## The convergence

Over a year down the line and Marco has built a brand new dev-focused live streaming and video platform on Livepeer, bringing a developer toolkit, embeddable players, a GraphQL API and full documentation making building streaming applications easy.

The platform also contains multi-framework player packages and embeddable video players for React, Svelte, Web Components and vanilla JavaScript, so video developers can drop FrameWorks playback into the stack they're already using.

Marco's half decade of building on Livepeer have shown how his deep knowledge of media and streaming can be implemented across the platform. FrameWorks is where that long stretch of work converges into a single platform a developer can pick up and build on.
37 changes: 37 additions & 0 deletions public/images/blog/builder-spotlight-frameworks.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.