Repo to video

Turn your repo into a product video people understand.

Pick the local project folder. Poko finds the product message, screenshots, logo, colors, and useful features. Then it builds an editable first cut.

No blank timeline. No long creative brief. Start with the product your team already built.

Turn my repo into a video

Select a project folder

poko-dashboard/

▾ src/

▾ app/

dashboard.tsx

pricing.tsx

▾ public/

logo.svg ✓

dashboard.png ✓

README.md ✓

Reading source6 useful files

Product: team analytics dashboard

Promise: spot changes before reports

Brand: emerald, black, warm white

Draft scene

See the numbers that need your attention.

Source check

Logo and screenshot found

Why this helps

Skip the blank timeline. Start with the product you already built.

Your repo already holds the story. The README explains the promise. The code names the features. Screenshots show the product. Brand files keep the video looking familiar.

Poko connects those pieces into simple scenes. A pricing component and a dashboard screenshot can become one clear message: “Know before usage becomes a surprise.”

You spend less time hunting for assets and explaining the basics. You spend more time checking the hook, improving the message, and deciding what ships.

pricing.tsx
usage alerts before limit

README.md
avoid surprise overages

→

Scene 03 · 4.2 sec

Know before usage becomes a surprise.

Detailed workflow

From folder to MP4, with a review at every step.

Poko does the heavy setup, but it does not lock you into the first answer. You can see the source, story, scenes, and preview as the project takes shape.

01
Choose the local folder
Open Poko Motion and select the project you want to explain. You stay in control of the source. Start with the repo that has the clearest copy and current assets.
02
Review the useful context
Poko looks for the README, package details, page copy, components, logos, colors, screenshots, and other product assets. It uses these files to identify the audience, promise, and important workflows.
03
Let the agent draft the story
The agent chooses a simple narrative, writes concise scene copy, and connects claims to evidence from the project. It then builds the video project instead of giving you a loose script to assemble elsewhere.
04
Watch and edit in Studio
The live preview shows timing, layout, motion, and transitions. Ask for changes in chat or make direct project edits. Check each pass while the context is still fresh.
05
Render the final MP4 locally
Choose the format you need and render on your Mac or Windows computer. The finished file lands on your machine, ready for a launch post, product page, or update.

Have a launch coming up? Start the first draft from the repo while the product details are still accurate.

Download Poko Motion

Studio · launch-videoPreview 00:18 / 00:36

Usage alerts

Fix the spike before the invoice.

01020304

Chat edit

“Move the pricing scene after the dashboard. Change the headline to ‘Fix the spike before the invoice.’ Keep the total under 40 seconds.”

Updating scenes 3–5 and shortening transitions…

Editable Studio and chat

The first draft is a working project, not a dead-end export.

Use chat when the change is easy to describe. You can ask Poko to shorten the opening, reorder two scenes, replace a weak headline, use a different screenshot, or keep the full video under a set length.

Studio gives you the live preview and project structure. This makes feedback concrete. Instead of saying “the middle feels wrong,” you can point to scene three and ask for a faster transition or a clearer product benefit.

You keep the useful automation without giving up judgment. Review product claims, remove anything that is not accurate, and make the final cut sound like your team.

What Poko reads

Useful product context, with clear limits.

Poko can use README text, package metadata, page copy, UI components, public logos, screenshots, icons, color tokens, and other files that explain what the product does. Better source material leads to a more grounded first draft.

It does not need dependency folders, build output, cache files, or Git history. It does not treat every line of code as video material. Large technical details are reduced to the product facts a viewer needs.

Poko also does not replace fact checking. If a plan, metric, or workflow changed, update the source or correct the scene before rendering.

Useful inputs

✓ README and product copy
✓ UI source and routes
✓ Logos and brand tokens
✓ Screenshots and icons

Skipped or limited

— node_modules
— build and cache output
— .git history
— unsupported binaries

Privacy and local rendering

Your repo and render stay on your computer.

Poko works from the project folder you select. It does not upload the full repository as a video job. Small excerpts needed for an AI response may go to the selected model. Supported plans let you use your own provider key, and Pro options include local-model connections.

The generated project stays local. Final frames and the MP4 are rendered by your machine, so there is no cloud render queue and no need to send the finished source project to a remote renderer.

Always follow your company rules for sensitive code. Choose a folder you are allowed to process, and avoid placing secrets in product copy or assets.

Specific use cases

Useful whenever the product changed faster than the video.

The repo gives Poko current language and assets. That makes it a practical starting point for four common jobs.

SaaS launches

Turn the launch branch, new UI, and current positioning into a short release video.

Feature updates

Explain one workflow with the component copy and screenshots that shipped with it.

Developer tools

Translate technical capability into a clear outcome without hiding the real product.

Open-source projects

Create a project overview that helps new users understand why the repo matters.

A better starting point

Start from evidence instead of a blank timeline.

Manual production can work well, but the setup is real. Someone must inspect the product, collect assets, write the first script, plan scenes, match the brand, and create a render project before useful review begins.

Poko starts that work from the repository. Your team can spend its review time on accuracy, pacing, and taste rather than rebuilding context that already exists.

Starting from blankStarting from the repo

Collect copy and assetsPoko finds useful files

Write a first scriptPoko drafts from source

Build every scenePoko creates an editable project

Wait to see the resultReview in the live preview

Transparent pricing

Choose a subscription or one-time app access.

Subscriptions start at $25 per month and include monthly AI dollars that roll over. One-time Starter access begins at $49 and includes $10 in AI dollars.

Repo, website, PDF, and PowerPoint sources are included. Higher plans add more active projects, narration time, agent capacity, and bring-your-own-key options. AI top-ups are available when included usage runs out.

Compare every plan and limit

Subscription Starter

For personal projects

$25/mo

✓ $10 AI dollars each month
✓ 5 active projects
✓ 50 minutes of AI narration per month
✓ All video formats and source types

Prefer one payment? Starter app access is $49 once.

Current prices and plan details are shown on the main pricing section.

Questions

Repo to video FAQ

What does repo to video mean?+

It means turning a local software project into an editable product video. Poko uses useful files in the folder to understand the product, draft a story, build scenes, and open the result in Studio.

Which repositories work best?+

SaaS apps, websites, developer tools, open-source projects, and design-heavy product folders work well. A clear README, product copy, logos, screenshots, and organized source files give Poko better context.

Does Poko read every file?+

No. Poko looks for useful product context and avoids folders such as node_modules, build output, caches, and version-control data. You choose the project folder and can review what the video says.

Is my full repository uploaded?+

No. Your repo and generated video project stay on your machine. Small, relevant excerpts may be sent to your selected AI model so it can answer. Supported plans also let you bring your own AI key or use local models.

Can I edit the generated video?+

Yes. The first draft is fully editable. Use chat for broad changes, adjust the project in Studio, watch the live preview, and render when the pacing and message feel right.

Can Poko show a working app automatically?+

Poko reads the folder for context and assets. It does not promise to run every app or invent a reliable screen recording. Add screenshots or product captures when an exact workflow needs to appear.

Do I need a video editor or developer setup?+

No. Poko Motion includes its own Studio, renderer, and FFmpeg workflow. You do not need to build a video timeline from scratch or install a separate rendering stack.

Which computers are supported?+

Poko Motion supports macOS and Windows, including Apple Silicon and Intel Macs. Final MP4 rendering happens on your computer.

Build the first draft from the product you already made.

Download Poko Motion for Mac or Windows. Choose a local repo, review the story, edit the scenes, and render the final video on your machine.