Podcast Platform Development

Our company is engaged in the development, support and maintenance of sites of any complexity. From simple one-page sites to large-scale cluster systems built on micro services. Experience of developers is confirmed by certificates from vendors.
Development and maintenance of all types of websites:
Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Our competencies:
Development stages
Latest works
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1161
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1041
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    822
  • image_crm_chasseurs_493_0.webp
    CRM development for Chasseurs
    847
  • image_website-sbh_0.png
    Website development for SBH Partners
    999
  • image_website-_0.png
    Website development for Red Pear
    451

Podcast Platform Development

Podcasts are deceptively simple: an audio file + RSS. But once monetization, analytics, dynamic ad insertion, and support for multiple hosts per show are added, complexity skyrockets. Below is the architecture of a real platform, not just another RSS host.

RSS Feed as Core API

Podcast clients (Apple Podcasts, Spotify, Overcast) consume RSS. The feed must comply with Apple Podcasts and Podcast Namespace specifications (podcastindex.org):

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
  xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
  xmlns:podcast="https://podcastindex.org/namespace/1.0"
  xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>My Podcast</title>
    <link>https://example.com/podcast</link>
    <language>en</language>
    <itunes:author>John Doe</itunes:author>
    <itunes:category text="Technology"/>
    <itunes:image href="https://cdn.example.com/covers/show-1.jpg"/>
    <podcast:locked>yes</podcast:locked>
    <podcast:guid>urn:uuid:f8d3e2a1-...</podcast:guid>

    <item>
      <title>Ep. 42: Redis Internals</title>
      <guid isPermaLink="false">ep-42-redis-internals</guid>
      <pubDate>Fri, 14 Mar 2025 10:00:00 +0000</pubDate>
      <enclosure url="https://cdn.example.com/audio/ep42.mp3"
                 length="48291840" type="audio/mpeg"/>
      <itunes:duration>3456</itunes:duration>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:season>2</itunes:season>
      <itunes:episode>42</itunes:episode>
      <podcast:chapters type="application/json+chapters"
        url="https://cdn.example.com/chapters/ep42.json"/>
      <podcast:transcript url="https://cdn.example.com/transcripts/ep42.vtt"
        type="text/vtt"/>
    </item>
  </channel>
</rss>

Feed generation is not a static file but a dynamic endpoint with caching:

class PodcastFeedController extends Controller
{
    public function feed(string $slug): Response
    {
        $show = Show::with(['episodes' => function ($q) {
            $q->where('status', 'published')
              ->orderByDesc('published_at')
              ->limit(100); // most clients don't take more
        }])->where('slug', $slug)->firstOrFail();

        $xml = $this->feedBuilder->build($show);

        return response($xml, 200)
            ->header('Content-Type', 'application/rss+xml; charset=utf-8')
            ->header('Cache-Control', 'public, max-age=3600');
    }
}

Dynamic Ad Insertion (DAI)

Dynamic Ad Insertion is the primary monetization source. Two models: server-side (file is re-encoded with ads) and client-side (player loads ads separately via VAST).

Server-side via FFmpeg is more reliable and works in any client:

import subprocess
from pathlib import Path

def insert_ads(episode_path: str, ad_slots: list[dict]) -> str:
    """
    ad_slots: [{"position_sec": 0, "ad_path": "preroll.mp3"},
               {"position_sec": 600, "ad_path": "midroll.mp3"}]
    """
    parts = []
    prev = 0

    # Slice episode around ad insertions
    for slot in sorted(ad_slots, key=lambda x: x['position_sec']):
        pos = slot['position_sec']
        segment = f"/tmp/seg_{prev}_{pos}.mp3"
        subprocess.run([
            'ffmpeg', '-i', episode_path,
            '-ss', str(prev), '-to', str(pos),
            '-acodec', 'copy', segment, '-y'
        ], check=True)
        parts.extend([segment, slot['ad_path']])
        prev = pos

    # Tail after last ad
    tail = f"/tmp/seg_{prev}_end.mp3"
    subprocess.run([
        'ffmpeg', '-i', episode_path, '-ss', str(prev),
        '-acodec', 'copy', tail, '-y'
    ], check=True)
    parts.append(tail)

    # Concatenation
    list_file = "/tmp/concat_list.txt"
    with open(list_file, 'w') as f:
        for p in parts:
            f.write(f"file '{p}'\n")

    out = f"/tmp/episode_with_ads_{Path(episode_path).stem}.mp3"
    subprocess.run([
        'ffmpeg', '-f', 'concat', '-safe', '0',
        '-i', list_file, '-acodec', 'copy', out, '-y'
    ], check=True)

    return out

Episode Transcription

Transcription is needed for SEO, accessibility, and content search. OpenAI Whisper is the best balance of quality and cost:

import whisper
import json

def transcribe_episode(audio_path: str, language: str = 'en') -> dict:
    model = whisper.load_model('large-v3')
    result = model.transcribe(
        audio_path,
        language=language,
        word_timestamps=True,
        verbose=False
    )

    # Convert to WebVTT for podcast:transcript
    vtt_lines = ['WEBVTT\n']
    for seg in result['segments']:
        start = format_timestamp(seg['start'])
        end = format_timestamp(seg['end'])
        vtt_lines.append(f"{start} --> {end}")
        vtt_lines.append(seg['text'].strip())
        vtt_lines.append('')

    # Chapters JSON (podcastindex.org/namespace)
    chapters = detect_chapters(result['segments'])

    return {
        'vtt': '\n'.join(vtt_lines),
        'chapters': chapters,
        'full_text': result['text'],
        'duration': result['segments'][-1]['end'] if result['segments'] else 0
    }

def format_timestamp(seconds: float) -> str:
    h = int(seconds // 3600)
    m = int((seconds % 3600) // 60)
    s = seconds % 60
    return f"{h:02d}:{m:02d}:{s:06.3f}"

Listening Analytics

IAB Podcast Measurement Standards v2.1 is the industry standard. Main rule: one unique IP + User-Agent per 24 hours = one download, regardless of request count.

-- Deduplication per IAB v2.1
CREATE TABLE download_events (
  id            BIGSERIAL PRIMARY KEY,
  episode_id    BIGINT NOT NULL,
  ip_hash       TEXT NOT NULL,  -- SHA-256 for GDPR
  user_agent    TEXT,
  bytes_sent    BIGINT,
  created_at    TIMESTAMPTZ DEFAULT now()
);

-- Unique downloads per period
SELECT
  episode_id,
  COUNT(DISTINCT (ip_hash, LEFT(user_agent, 50))) AS unique_downloads
FROM download_events
WHERE created_at BETWEEN $1 AND $2
  AND bytes_sent > 0  -- exclude interrupted
GROUP BY episode_id;

Geo-analytics via MaxMind GeoIP2 — not from raw IPs (GDPR) but from pre-processed geo tags.

Subtitle Players and Chapters

Chapter markers are a killer feature for long episodes. Format podcast:chapters:

{
  "version": "1.2.0",
  "title": "Episode 42",
  "chapters": [
    { "startTime": 0, "title": "Intro", "img": "https://cdn.../ch0.jpg" },
    { "startTime": 120, "title": "Redis Data Structures" },
    { "startTime": 1800, "title": "Clustering", "url": "https://redis.io/docs/cluster" },
    { "startTime": 3000, "title": "Outro" }
  ]
}

Monetization: Subscriptions and Patreon Integration

Private RSS for paid subscribers — token in URL:

// Private feed with subscriber token
Route::get('/feed/{show}/{token}', function (string $show, string $token) {
    $subscriber = Subscriber::where('feed_token', $token)
        ->where('status', 'active')
        ->firstOrFail();

    // Log feed access (client analytics)
    FeedAccess::create([
        'subscriber_id' => $subscriber->id,
        'user_agent' => request()->userAgent(),
        'ip_hash' => hash('sha256', request()->ip()),
    ]);

    $show = Show::where('slug', $show)->firstOrFail();
    // Include bonus content for premium
    $episodes = $show->episodes()
        ->where('status', 'published')
        ->when(!$subscriber->is_premium, fn($q) => $q->where('is_premium', false))
        ->orderByDesc('published_at')
        ->get();

    return response($this->buildFeed($show, $episodes, $subscriber))
        ->header('Content-Type', 'application/rss+xml');
});

Audio Storage and Delivery

Podcasts are large files with uneven load (spike after episode release). S3 + CloudFront is the standard solution. Important: most clients make Range requests during playback for seeking — ensure your storage supports them.

# Proxying with signed token via Nginx
location /episode/ {
    set $signed 0;
    # Check signature via Lua or auth_request
    auth_request /validate-episode-access;
    proxy_pass https://s3.example.com/podcast-audio/;
    proxy_set_header Authorization "";  # remove our credentials
    add_header X-Robots-Tag "noindex"; # audio doesn't need indexing
}

Timeline

A platform with public shows, RSS per Apple/Spotify standard, file uploads, basic analytics (IAB-compatible), and built-in player: 8–10 weeks. DAI (dynamic ads), Whisper transcription, private RSS for paid subscribers, Stripe integration: another 5–7 weeks. Mobile apps for iOS/Android: a separate story.