Videos defined as code
Describe a product flow once in a Playwright-based .screenci.ts script, then let ScreenCI drive the app and render the finished video from that code.
ScreenCI
ScreenCI is a developer-focused tool for creating product videos from Playwright-based scripts, with recording available locally or in CI. It helps teams generate narrated tutorials and demos that can be rerun when the UI changes.
Overview
ScreenCI is a developer-focused product video tool that treats tutorial videos as code. You describe a flow in a Playwright-based .screenci.ts script, ScreenCI drives the app, records the interaction, and renders a polished video with narration, camera motion, and overlays.
The workflow is designed so videos can be regenerated when the UI changes. The docs say you can record locally or in CI, keep the service away from your source code and browser session, and deliver the result as a download or through a CDN-backed static URL.
Features
Local and CI recording
Run the CLI on your machine or in CI, with only raw recording data and timing information leaving your environment during capture.
Cloud rendering and delivery
ScreenCI renders narration, zooms, and animations in the cloud and can publish the latest approved version to a CDN-backed static URL.
Auto-zoom camera motion
Use auto-zoom to follow interactions across the screen without placing manual zoom points for every movement.
Timeline assets and overlays
Add images, SVGs, and MP4 clips as timed assets on the timeline, alongside programmatic React or HTML overlays.
Narration and language control
Choose narration from 79 supported languages, with plan-based support for multiple languages, voice options, and style-directed narration.
Use Cases
Keep tutorials current after product changes
Document a product walkthrough as code, then rerun the same script when the interface changes so the tutorial stays aligned with the current UI.
Automate video generation in CI
Set up recordings in a repository workflow so releases or main-branch pushes can produce updated videos without a manual recording session.
Produce narrated demos and feature explainers
Add narration, overlays, and timed media to create a polished product demo for customer-facing documentation or marketing pages.
Start with an agent-assisted setup
Work with a coding agent to scaffold ScreenCI and generate a first video when you want a guided setup rather than writing everything by hand.
Pros and Cons
Pros
- The source code remains local; the service only receives raw recording data and timing information during capture.
- The same script can be rerun when the UI changes, which helps keep videos aligned with the product.
- The CLI supports both local use and CI workflows, including a generated GitHub Actions setup.
- The product includes a web editor for narration, languages, assets, and render options on every plan.
- There is a free trial with no sign-up or credit card required, which lets users evaluate the workflow before paying.
Cons
- The docs do not provide a full end-to-end walkthrough in the captured text, so setup details are only partially visible here.
- Some capabilities are plan-gated, such as multiple narration languages, 4K output, and certain voice options on the Business plan.
FAQ
How does ScreenCI work?
ScreenCI uses a Playwright-based script to describe a product flow, then records and renders the video through its service. The docs say you can set it up either with a coding agent or manually by writing the script yourself.
Can ScreenCI run in CI as well as locally?
The overview says the CLI can run on your machine or in CI. The CI setup page explains that the generated workflow records with GitHub Actions and is designed to mirror Playwright CI.
Is there a free trial or watermark?
The pricing page says the Free trial includes up to three recordings and is watermarked for evaluation only. Paid plans remove the trial limits and are cleared for commercial use.
Which plan is meant for teams?
The pricing page lists Starter for solo use and Business for teamwork. It also says every plan includes the web editor for narration, languages, assets, and render options.
Quick Facts
- Category
- Developer Tool / Video Editing
- Primary workflow
- Playwright-based scripts record product flows and render videos
- Recording modes
- Local machine or CI
- Output delivery
- Download or CDN-backed static URL
- Supported narration languages
- 79
- Website
- screenci.com
Alternativas ao ScreenCI
ByteAsk
ByteAsk is a terminal-first AI coding agent for C and C++ that edits repositories and verifies changes with the real compiler, debugger, sanitizers, and tests before showing a diff. It offers a free tier plus paid plans, with editor connectors and zero-retention handling described in the source.
CreateOS Sandbox
CreateOS Sandbox is an isolated compute environment for running code and agent workloads inside Firecracker micro-VMs. It is designed for workflows that need machine-level isolation, private networking between sandboxes, and programmatic control through SDK, CLI, or MCP.
hob
hob is an independent workspace for coding agents that keeps agent sessions, terminals, history, and follow-up work organized around the tools and providers you already use. It is aimed at developers who want local control over routing, history, and workspace structure rather than a bundled model stack.
Ably Chat
Ably Chat is a chat API platform for building custom realtime chat applications. It supports room-based messaging, typing indicators, presence, reactions, and message updates, with usage-based pricing options for different deployment stages.
Tavus
Tavus is an AI video platform for building real-time, face-to-face agents, digital twins, and AI companions. It combines APIs, custom replicas, and multilingual conversational workflows for developers and teams.
Manta AI
Manta AI is an autonomous web app testing tool for teams that want to map application behavior, catch regressions, and generate tests without writing scripts or maintaining selectors. It works from a URL and supports plain-English test flows, run results with screenshots, and scheduled or deployment-triggered checks.