With the release of v1.2.0, the fundamentals are now stable and ready for further expansion.

The Docker images on Docker Hub are updated to v1.2.0 on the latest tag. A docker-compose.yml file is available on the docs, it'll get you up and running in no time. 🥳

What's Changed

We thoroughly reviewed the architecture and made some great improvements. While there are countless under-the-hood tweaks, here are the key highlights:

• Plenty of QoL improvements in the dashboard - filtering, pagination, search, and more! Check out the Dashboard documentation for screenshots. Definitely worth mentioning, but the dashboard has been completely rebuilt from the ground up, making its structure much simpler. This will enable faster iterations moving forward.
• There's now an asset API! Each asset represents a video (with basic metadata for now). This is the first step toward building a full-fledged video CMS.
• Stitcher support for live streams (including ad signaling) was introduced as part of the Montevideo Summercamp 2025, SGAI initiative. If you're interested in video engineering, we highly recommend joining us next year! It's open, it's free and it's all about learning.
• We've moved away from the idea of a top-level config.env file and switched to using separate .env files for each project. If you're using the Docker images, you can still configure them generically (thanks to Docker Compose). Check out an example at this link.
• We switched from Elysia (Bun web framework) to Hono for both the API and Stitcher. We now have fewer dependencies, and the OpenAPI spec generation is more flexible.
• Syncing to and from S3 has been unreliable - if the connection drops, the job would fail. We replaced the s3-sync-client package with custom syncing code, giving us better control over retries and failures.
• Stitcher has been significantly improved! You can now manually schedule VAST ads at specific positions, add a list of assets manually, and much more. Check out the dedicated Stitcher section in the documentation for more details.
• Stitcher now has out-of-the-box support for Cloudflare Workers, and Cloudflare KV, making it incredibly easy to scale.

Note that we've made some significant changes: @superstreamer/player is no longer a full-featured player with a UI. Instead, it now serves as a facade on top of HLS.js. This allows you to build your own controls in the framework of your choice. The API is designed to be intuitive and easy to extend, making customisation straightforward.

We've refocused on supporting existing open source initiatives. One standout project we’re working with is Media Chrome, and we're currently ensuring compatibility with the player SDK. It's still a work in progress, but you can check out our progress here. We believe the right approach is to integrate with existing solutions in the OSS community, rather than creating yet another alternative.

From now on, we're going to strictly follow semver too.

Until next time! 👋