Castopod Hosting

How Castopod works

Castopod stores podcast shows and episodes, publishes their RSS feeds, and provides web pages where listeners can discover and play content. Creators upload audio, artwork, descriptions, chapters, and supported Podcasting 2.0 metadata. The feed is then submitted or connected to podcast directories and listening applications according to each directory’s separate process.

The platform also includes analytics, clips or soundbites, embeddable players, social features based on the fediverse, and tools for audience engagement or monetisation links. The first-run installer creates the administrator and first podcast. Uploading an episode does not automatically grant music, image, guest, or distribution rights, so creators must clear the material they publish.

Key Castopod features

Podcast and episode pages sit beside standards-based RSS feeds, allowing one hosted source to serve websites and compatible listening applications. Built-in analytics help publishers examine consumption, while chapters, transcripts, clips, and Podcasting 2.0 fields enrich supported players. Social features can connect shows to federated conversations.

Directory distribution remains an external relationship. Apple Podcasts, Spotify, and other catalogues have their own accounts, rules, reviews, and processing times. External monetisation providers, payment services, and social networks are also separate. Castopod supplies the hosting and publishing system, not automatic acceptance or commercial reach on those platforms.

Castopod vs Buzzsprout

Castopod is a self-hosted podcast publishing platform with feeds, websites, analytics, social capabilities, and open podcast metadata. Buzzsprout is a provider-managed podcast hosting service that combines distribution guidance, statistics, podcast websites, monetisation options, and commercial audio tools.

Buzzsprout may suit creators who prefer vendor-operated infrastructure and a guided managed workflow. Castopod is attractive when a publisher wants to control the application, MariaDB records, feeds, and media storage. That control brings responsibility for storage, setup, directory relationships, rights, backups, and account security.

Who uses Castopod

Independent podcasters can publish a show from their own domain, networks can organise several programmes, and organisations can distribute interviews, training audio, or public updates. Communities interested in federated discussion may value its social layer.

The platform is not an audio-rights service, advertising network, or directory. Publishers remain responsible for editing quality, legal releases, music licensing, accessibility material, directory submissions, and the long-term storage needed for their catalogue.

Self-hosting Castopod: requirements and cost

Castopod demand is driven by episode count, audio size, downloads, concurrent listeners, analytics, artwork, transcripts, clips, and background processing. MariaDB stores shows, episodes, users, analytics, and configuration, while persistent media storage holds audio and images. Database memory is outside the exported application minimum, and media capacity becomes the practical limit as a catalogue grows.

AvaHost maps Castopod to Plan 2 at €5. MariaDB is included but unmanaged, with custom-domain HTTPS, automatic application updates, and scheduled backups. Application email is disabled, so mail notifications, invitations, and recovery are unavailable. For an expanding audio archive, 50 GB on Plan 3 is a realistic starting point, while 100 GB on Plan 4 better suits a large library.