Creator tooling · Laravel · Personal project
Content OS — the command center for a podcast that publishes everywhere.
A content distribution and growth system built to run Hamrah Podcast's own publishing — every episode's trailer, reels and quote posts tracked from draft to published, across YouTube, Instagram and Facebook, from one dashboard instead of three open tabs.
The problem
Recording an episode is one job. Getting it onto three platforms properly is another.
A podcast episode isn't one piece of content — it's a full episode, a trailer, three or four reels, and a couple of quote posts, each of which belongs on a different platform with different captions, different hashtags, and its own schedule. Doing that by hand across YouTube, Instagram and Facebook meant clips sitting finished and forgotten, platforms getting skipped, and no real way to tell which hook or which cut actually worked.
What it does
One workflow: create, organize, distribute, track, learn, reuse.
Campaigns, not loose files
An episode becomes a campaign with its own template — full episode, trailer, reels, quote posts — so nothing about it gets built or forgotten piecemeal.
A distribution matrix that shows the gaps
Every asset against every platform, in one grid — published, scheduled, ready, missing, or failed — so an untouched Facebook column is obvious instead of discovered a week later.
Variants tracked as first-class content
Hook A vs. Hook B, a longer cut vs. a shorter one — each variant keeps its own platform packaging and its own performance history, so "which version actually worked" has a real answer.
Rule-based growth actions, no AI subscription
An action engine surfaces what actually needs attention — a ready reel with no destination, a token about to expire, a winner nobody has reposted — without depending on a paid AI layer to work.
Why it holds up
Platform differences aren't hidden
A capability layer per platform means the composer only offers what YouTube, Instagram or Facebook actually support — no generic form pretending every network works the same way.
Publishing never blocks on a big upload
Every publish runs through a queued job with real stages — preflight, uploading, platform processing, verification — so a large video upload never holds a web request open.
Multi-workspace from the ground up
Hamrah Podcast and Viral Himachal live as separate workspaces with their own accounts, campaigns and analytics — a structure that's already ready for a client workspace later.
Want the real build story — the platform adapters and why it's a system, not a scheduler?
Read the full case study