Drop the episode.
Get the clips back.
Rendering off your machine, seats for your team, thumbnails you can edit, one brand kit, and the numbers each clip came back with. The CLI stays free and stays local.
What you get for paying
Close the laptop while it works
Transcription, scoring, crop, captions, and export all run on our hardware. Queue an episode and walk away.
- Runs on
- Two workers, ours
- To install
- Nothing
- Whisper and ffmpeg
- Already there
- A two hour episode
- Costs you the upload
- Your machine does
- Nothing else
A clip thumbnail you can actually edit
The CLI draws one mid-render and cuts it onto the front of the video. Here it is a separate 9:16 image.
- Backdrop
- Your own, reused across clips
- Headlines
- Written from the clip, kept
- Baked into the video
- Only if you ask
we quit
Your team gets a seat
An editor cuts, a producer signs off, and the role you hand out decides who can change what.
- Roles
- Owner, admin, editor, viewer
- Seats
- Move between people
- Approvals
- Live on the clip
- Guests
- Review with no account
Find out which clips held people
Views, retention, and click-through come back from your channel and get ranked by the kind of moment, the caption style, and the length they came from.
- Connect the channel
- Once
- Comes back
- Views, retention, click-through
- Ranked by
- Moment, caption style, length
- No connection
- Import the YouTube Studio CSV
- Under 8 clips
- It says so instead of guessing
Prefer story beats: they retain 64% on this channel versus 33% for banter.
And the parts the CLI keeps on one machine
Accent, ink, surface, type, and logo live once and are read by clips and thumbnails alike, so the video and the picture cannot drift.
How it cuts, how it is captioned, what plays before and after: one named object per look instead of options retyped on every render.
A running order held as rows. Move a moment and only what moved is re-cut.
Six clips out of three episodes under a single review URL. Add one and everybody holding the link sees it.
The guest's surname, spelled right in every caption and every title. The CLI keeps this list per machine; here it is per workspace.
Scoring and copy run on our model access, metered into your plan.
Claude Code, Codex, or Cursor speaks MCP with an ordinary session token.
Where the two differ
| Podcli CLI | Podcli Cloud | |
|---|---|---|
| Rendering | Your machine | Ours |
| Setup | Install a local toolchain | Sign in |
| AI scoring | Bring your own key | Included and metered |
| People | You | Your team, with roles |
| Review | Send files around | Share link, no account |
| Thumbnails | Baked into the video | A separate image you can edit |
| Brand kit | Per machine | One per workspace, shared |
| Corrections | corrections.json on your disk | One list your team shares |
| Performance | Check Studio yourself | Synced per clip and ranked |
| Your files | Only on your disk | Your workspace, our storage |
| Cost | Free, AGPL-3.0 | Paid, priced at launch |
If your material is under NDA, or you work alone on a fast machine, stay on the CLI. Read the docs.
Questions people ask first
Does Cloud replace the CLI?+
No. Cloud is for shows that outgrew one machine and one person; the CLI keeps shipping free under AGPL-3.0.
What does it cost?+
Not announced yet. Everyone on the waitlist hears the numbers before anything is charged.
Do my files leave my machine?+
For Cloud, yes. Your episode is uploaded so it can render without your laptop. If it cannot leave, stay on the CLI.
When does it open?+
Seats open in small groups so the first renders are fast. The waitlist is the order they go out in.
Get in early
You'll hear the numbers before anyone else does.