What is PodSaid?

PodSaid is an embeddable Q&A widget for podcast and church sermon archives. PodSaid turns your podcast or church sermon library into a Q&A widget your visitors can talk to. Someone lands on your site, clicks the launcher, asks a question in plain English — and the widget answers using your own content, with every fact linked back to the exact moment in the exact episode or sermon it came from.

The whole product is two pieces: a widget you paste on your site, and a backend we run for you. You never touch the backend, and the widget is a two-line paste.

The widget is a Web Component — a standard browser custom element (<ask-pod-widget>) plus a single <script> tag from our CDN. Two lines of HTML, no build step, no framework requirement, no npm install.

Renders a floating chat launcher in the corner of your site. Visitors click, ask, get cited answers.
Runs inside a Shadow DOM, so your theme’s CSS can’t reach it and its CSS can’t leak into your site. No conflicts.
Works on any site that can render an HTML tag — WordPress, Squarespace, Wix, Webflow, Subsplash, Rock RMS, plain HTML, React, Next.js, everything else. See Embedding the widget for the per-platform paste.
Configurable via CSS variables — accent color, font, launcher label, spacing. See Customization.

This is the piece you install. Time from paste to live widget: about 3 minutes on most platforms.

The backend

Behind the widget is a pipeline you never see. When you sign up and point us at your RSS feed or YouTube channel, we:

Fetch every episode.
Transcribe the audio — YouTube captions when they exist and are clean, Whisper otherwise.
Chunk and embed the transcripts into a vector store, timestamped so we can jump back to the exact moment.
Serve the widget’s queries — a visitor’s question triggers a vector search across your corpus, and an LLM composes a cited answer from the top-matching chunks.

We run all of it. You don’t provision anything, don’t pay for OpenAI credits, don’t manage a database. See How ingest works for what the pipeline does between “you signed up” and “your widget is live.”

How they talk

The widget calls api.podsaid.com over HTTPS. Every request carries:

Your public pk_live_* key — pasted in the widget snippet, safe to embed in HTML (see the security model — same design as Stripe’s publishable keys).
The browser’s Origin header — which our server checks against your Allowed Origins list. Anything else gets a 403.

That’s the whole trust story. No secret key exists for the widget; nothing to leak from a client-side paste.

What you manage vs. what’s on us

You manage:

The widget paste on your site.
Your Allowed Origins list (the domains authorized to use your public key).
Optional CSS overrides to match your brand.

We manage:

Feed fetching, transcription, embeddings, vector storage.
The Q&A API — vector search, LLM prompt, citation generation.
Widget code, CDN, updates.

If it involves your content pipeline or answering questions, it’s on us. If it involves your site or your customer relationship with visitors, it’s on you.

Where to go next

Quickstart — signup to a live widget in about 5 minutes plus the async ingest wait
Embedding the widget — the platform picker, security model, and end-to-end install story
See it in action — screenshots of the widget on a real customer site
How ingest works — what the backend does between signup and “your widget is live”
Trial and plans — how the 14-day trial works (clock starts when your feed is ready, not at signup)
Widget errors — every reason code the widget can log, with a fix
Data and privacy — what we store, where it lives, how to delete it
Support — book time with Mark or email support

Or jump straight to your platform:

Any site (plain HTML)·WordPress·Squarespace·Subsplash·Rock RMS·Wix·Webflow·React·Next.js