About Pijama

Pijama is a watch-on-demand platform created to help independent and undistributed films reach viewers directly. The platform was launched by filmmaker brothers Pablo and Juan de Dios Larraín, with a focus on giving films a path to audiences beyond traditional distribution channels.

Unlike a standard subscription streaming platform, Pijama follows a rental-led model where viewers can discover and rent films on demand. Its catalog includes independent, festival-driven, and globally recognized films available for online viewing. But Pijama was not just building a viewing platform. It was building a complete digital workflow for film distribution — one where filmmakers and content partners could bring content online, manage key details, and reach audiences through a branded streaming experience. 

The Challenge

Pijama didn’t need a streaming platform. It needed its existing systems to become streaming-capable.

When Pijama came to Muvi, it already had:

• An internal content portal for managing film metadata and operations in-house
• A content partner portal where external partners upload films and manage availability
• A custom-built frontend — designed and owned by the Pijama team

The ask wasn’t “build us a platform.” It was: can your infrastructure plug into what we already have?

Specifically, they needed:

• API access to content management — so their internal portal could push metadata, manage titles, and control availability without anyone logging into a separate CMS
• AI subtitle generation via API — to handle accessibility and localization at scale for independent and international films
• A player that could drop into their existing frontend without rebuilding playback from scratch
• App distribution to extend reach beyond the web

How Muvi Helped

Muvi powered the streaming layer behind Pijama’s custom film workflow

Content Management Inside Their Portal

Pijama’s internal and partner portals connect directly with Muvi One’s content management layer through APIs. Metadata updates, content status changes, availability settings — the content operations that would normally happen inside a CMS can now happen from Pijama’s own portal.

Muvi powers the backend content management layer, while Pijama’s team continues working from the system they already use.

Their content partners manage film details through the partner portal they are already familiar with. Those updates are then passed to Muvi through APIs in real time, keeping the portal and streaming backend connected.

AI Subtitles Through API

Pijama uses Muvi’s AI Subtitles API to generate subtitles for films managed through their portal. The API fits into their existing ingest process — no manual exports, no third-party tool, no separate workflow step. It runs where the content already lives. 

Player SDK for Custom Playback

Pijama’s frontend was already built. Rather than swap it out, they integrated Muvi’s Player SDK to handle playback. They get full player functionality — adaptive streaming, DRM, quality controls — without writing a video player. 

Multi-Screen Apps Without Rebuilding the Backend

Pijama has availed apps for iOS, Android, Roku, LG TV, Samsung TV, Fire TV, and Android TV through Muvi APIs.

The same content workflows running through their internal and partner portals can feed into these app experiences through Muvi’s backend infrastructure. This helps Pijama manage content from its own system while delivering films across mobile and connected TV platforms.

The Outcome

A Custom Film Distribution Workflow Powered by Muvi

With Muvi, Pijama could build its streaming operation around the systems it already had.

The team did not have to abandon its internal portal, content partner workflows, or custom frontend. Instead, Pijama used Muvi APIs, AI Subtitles, Player SDK, and apps to connect those systems with a complete streaming backend.

Their content partners continued working inside Pijama’s own branded partner portal, not a separate Muvi CMS. Since the content management workflows were connected through APIs, partners could manage film details from the same familiar interface while Muvi powered the backend operations behind it.

The result was a fully white-labeled workflow where Pijama controlled the partner experience, the frontend experience, and the brand experience, while Muvi handled the streaming infrastructure in the background.

For Pijama, Muvi was not just a CMS.

It became the video infrastructure behind a custom independent film distribution platform.

Why This Example Matters

Most OTT platforms assume you’re starting from zero. Muvi’s API-first architecture doesn’t.

If your team has already built internal tooling, partner portals, or a custom frontend — you don’t have to scrap it to add streaming. You can use Muvi APIs to handle content management, Muvi’s AI Subtitles API for accessibility workflows, and the Player SDK for playback, while keeping your own systems as the interface your team actually uses.

This implementation is a good fit if you:

• Have an internal portal or partner dashboard you want to keep
• Need API-based content management rather than a CMS UI
• Want to sync content operations between your own system and a streaming backend
• Need AI subtitle generation as part of an existing ingest workflow
• Already have a frontend and need a player — not a full platform rebuild
• Want app distribution without migrating your backend

Ready to build a custom streaming workflow like Pijama? Start your 14-day free trial or explore Muvi’s Developer Portal.