Set up your first film.

Open Repositories in the app and start the GitHub App installation. Pick your repositories on GitHub, and you return to the app with them connected. You never paste IDs or tokens.

Your default branch is selected for you. Open Set up demo to choose the audience. Branch and brand settings are available when you need them.

Open Repositories, then Set up demo. Keep Choose for me selected, choose a film format and save. You can add one sentence about what viewers should understand. The next run reads the app, selects useful scenes and writes the narration. You do not need to write a script or add configuration files for a supported app.

Thespis chooses from pages it can actually open and results the running app can return. It reads the product README for context. For an API product, a checked-in OpenAPI file can identify simple GET requests to show as clear result panels. A sign-in wall needs a demo workspace with sample data before it can be recorded.

For a precise interaction or a request with input, choose Write my own. Add the words you want spoken and the steps to show:

API scenes show real responses in a readable result panel, with narration and component framing. For example, POST /invoices with sample line items can show the new invoice number, total and status. An unexpected status or missing field stops the run. Timing is an observation from that capture, not a performance benchmark.

API capture runs against the local app started from your repository. It supports JSON responses up to 128 KiB, a 15-second request limit and selected scalar fields. It does not follow redirects or send authentication headers. Use a seeded demo environment with sample data. It does not yet record command-line tools or arbitrary external services.

Managed films use native 4K at 60 fps. Your brand kit selects the voice and styling. Review the completed master before approving it.

Open Runs, choose your product and click Make film in cloud. Marketing film and Team guide ask Thespis to choose a fresh story for that audience. Use saved story keeps your existing walkthrough. The exact release and setup are saved with the run.

Discovery, recording, narration and rendering all happen in the cloud. Keep working or close your laptop while the film is made. Longer films take more processing time. Runs shows the actual elapsed time and queue state. If capacity is busy, your run waits and starts when a slot opens.

Push to your demo branch. That starts a run automatically, using the exact commit you pushed. You can also queue one from the Runs view.

Thespis then starts your app, waits for it to answer, performs the walkthrough, and produces the complete film.

A finished run waits for a person. Watch it, then approve it. Approved films appear in Demos, where your team can play them or download the 4K file.

The Demos catalog stays private. Owners and admins can publish one approved release through a separate external link. The stable link follows the current shared version, while a version link continues to open the release it was created for.

This file tells Thespis how to start your application and which voice to narrate with. Put it at the root of your demo branch.

version: 1
name: your-product
run: npm run dev
port: 3000
ready:
  path: /
  timeoutMs: 120000
env:
  DATABASE_URL: postgres://demo:demo@localhost:5432/demo
narration:
  mode: programme
  takes: 2
  voice:
    gender: female
    age: middle-aged
    accent: american
    tone: warm professional
    language: en
  delivery:
    pace: 0.96
script: demo/product.script.json

Use fake values in env. Never put real secrets in this file.

The walkthrough is a JSON file listing the scenes you want in the film. Each scene has a title, the words to narrate, and the steps to perform.

{
  "version": 1,
  "viewport": { "width": 1920, "height": 1080 },
  "captureScale": 2,
  "delivery": { "profile": "studio" },
  "quality": {
    "narration": "required",
    "minimumCameraShots": 1,
    "minimumNarrationTailMs": 900,
    "minimumDetailScale": 1,
    "maximumEyeTraceShift": 0.75
  },
  "scenes": [
    {
      "id": "overview",
      "title": "The dashboard",
      "narrate": "Every invoice and payment, in one place.",
      "minMs": 6000,
      "steps": [
        { "action": "goto", "url": "/", "ready": { "selector": "[data-testid=invoice-list]" }, "dwellMs": 1200 },
        { "action": "click", "target": { "selector": "[data-testid=invoice-row]" }, "ready": { "selector": "[data-testid=invoice-detail]" } },
        { "action": "assert", "target": { "selector": "[data-testid=invoice-detail]" } }
      ]
    }
  ]
}

Owners and admins can open Operations to see the selected organization's queue depth, stalled work, recent failures, success rate, delivery time, latest successful output, and account activity. The view polls while it is open and never combines data from different organizations.

Production costs USD $500 per month. Scale costs USD $1,500 per month. Enterprise starts at USD $25,000 per year. Request Production or Scale access from the website. Contact us for Enterprise or a capacity change while direct online checkout remains closed.

Existing online subscriptions can open the billing portal from Billing. Your current plan, repository allowance, render usage, concurrency, API-key allowance, and retention appear in the app.

thespis.yml fields

Team roles

Retention

Run history is kept for 90 days. The newest approved film for each repository is kept until you replace it, so your current private film never expires. The current external version is also kept. A superseded external version remains available through its version link for 90 days. Revoke or expire the external demo to stop new access sooner.

Run states

Everything in the app is also available over the API at https://api.thespis.dev. Create a key in the app under API keys. The token is shown once, so copy it straight into your secret manager.

export THESPIS_API_KEY="your-token"

curl --fail-with-body \
  --header "Authorization: Bearer $THESPIS_API_KEY" \
  https://api.thespis.dev/v1/organizations/YOUR_ORG_ID/repositories

Common endpoints

Key scopes