Yours to run, read and change
Open source under the AGPL-3.0. Run it on your machine or your own server, read it, change it. If you run a changed version for other people over a network, you offer them its complete source under the same licence.
Contributors sign a CLA (Harmony, “any licence” option). It lets us also offer a commercial licence to companies that can't use the AGPL. Every contribution stays available under the AGPL too. The name and logo are trademarks: forks pick their own name.
The source is on GitHub. On your machine there's no sign-up and no telemetry. Two models download once: the speech model, and footage search's (213 MB, when the first video is indexed; LAMPO_FOOTAGE=off or lampo footage off keeps it off). Anything else that goes out, from notifications to public links, is yours to switch on.
Run it as a server
A server is for a team, or for sharing reviews with clients without a tunnel. This repository is the whole app: self-hosted, it is complete and has no limits, except that hiding the Powered by Lampo badge on review links is a feature of Lampo Cloud's paid plans. The maintainers also run it as a hosted service, Lampo Cloud (lampo.video), for those who'd rather not run their own; its plans and billing come from a separate module that is not part of this repository and that a self-hosted server doesn't need (docs/server-mode.md):
cp .env.example .env # set LAMPO_DOMAIN and LAMPO_PUBLIC_URL (LAMPO_TRUST_PROXY=uniquelocal
# is already set), and storage for Bunny or S3 (.env is gitignored)
docker compose up -d # the app behind Caddy, with automatic HTTPS
docker compose logs # the first start prints a one-time setup token
Open your URL, enter the token and create the owner account. Then invite people, upload renders (drop them on the
library, or lampo push), keep each project's material in its Files tab, and connect agents: through Settings →
Connect an agent (a chat app by its connector address, signing in once), or lampo login, which signs in through the
browser and gives lampo and the stdio MCP server an API token:
lampo login https://review.example.com
lampo push render.mp4 --folder "Acme/Reels" # the same name again becomes V2, V3, …
lampo render --to render.mp4 --out out/v3.mp4 -- \
npx remotion render src/index.ts Main out/v3.mp4 # the progress shows in Lampo, then V3
docs/docker.md covers the image, volumes, upgrades and backups.
docs/server-mode.md covers configuration, the reverse proxy, accounts and workspaces, storage
(Bunny, S3) and the security model. Going live for real: docs/go-live.md, the runbook for one server
(DNS, TLS, backups with a restore drill, monitoring, updates), with node scripts/smoke.ts https://review.example.com
to check a running instance.