Rebuilt a streaming frontend with Ploy

I have no technical background, so when I first tried Ploy it seemed like a good way for me to build landing pages. I started by building a better one for Splatter (www.splatter.se), a Swedish horror streaming service I run on the side. Then the scope got a little out of hand, and over a few summer nights while on vacation, I ended up replacing the entire front end, keeping only the existing streaming backend and CDN. It now includes a live catalogue of 550+ films, individual film pages, search, genre and country pages, signup and Stripe checkout, subscriber accounts, and playback.

One of my first aha moments with ploy came when it replaced our paid consent management service with a custom-built consent layer. It took only a few prompts and saves us hundreds of dollars a year, which is a meaningful amount for a project like this.

Search performance had been flat for about a year at Splatter, but now impressions and clicks have risen sharply, and paying subscribers are up around 10% over the last two weeks. Ploy helped turn the live catalogue into a proper SEO surface, with server-rendered film pages, structured data, internal links, and sitemaps. Some of the subscriber growth is due to paid marketing, so I can’t isolate the effect of the new front end. But the catalogue, film pages, and shorter path to checkout are definitely contributing.

Happy to compare notes with anyone building with ploy on top of an existing product or backend.