RSS hosting
An RSS feed built to what Apple Podcasts expects, with chapters and transcript. Immediate or scheduled publishing, files stored in Europe.
The situation
A podcast lives through its RSS feed: that is what Apple Podcasts, Spotify and the other listening apps read. Often the feed is kept by a host separate from the production tool, and each episode is downloaded on one side to be uploaded on the other, with its metadata typed in again.
Built-in feed
Hosting is turned on show by show, in the show settings. The feed is then built from the published, public episodes, newest first. Its address appears in the settings and in the Distribution tab, ready to copy.
The feed carries what Apple Podcasts expects: cover, author, category, owner contact, explicit flag, season, number and episode type. It also carries the Podcast 2.0 extensions: chapters, transcript and a stable show identifier. The cover is checked before upload, in the square format Apple requires.
Publishing and scheduling
The MP3 rendered by the editor is already the one the feed serves: no export in between. An episode goes out at once, or on a set date, and then publishes itself within the following minute. An unpublished episode goes back to the rendered stage. A private episode stays out of the feed.
AI post-production adds chapters, a transcript and detailed notes to each episode, which listening apps read in the feed.
Distribution to platforms
Platforms subscribe to the feed and read the episodes from it. Submission happens once on each platform's site, then the following episodes arrive on their own. The Distribution tab gives the link and the steps for Spotify, Apple Podcasts, Deezer, Amazon Music and Podcast Index.
Each published episode also has an embeddable player, to place on a website.
Storage in Europe
The shows' audio files and covers are stored in Europe, and the feed serves them to listening apps from there.
Still missing
Listening statistics are not available yet. Submission to platforms is not automatic. Importing an existing podcast from another host is not available yet. Redirecting the feed to another host exists on the server side, but cannot be set from the interface yet.
By use case: internal podcast, media team.