v0.1.1 — verified on real hardware
Launchloom turns one product brief and a real recording of your product into a
film, a vertical cut, a landing page and reviewable social drafts.
Watch what it makes → — that film was
cut by Launchloom, from a screen recording of Launchloom.
Run it
git clone https://github.com/FORIFOR/Launchloom.git && cd Launchloom
python3 -m venv .venv && source .venv/bin/activate
python -m pip install -e . && python -m playwright install chromium
python -m launchloom doctor
python -m launchloom serveNo account, no API key, nothing leaves your machine.
In this release
Verified by running it, not by reading it. macOS and Docker end to end, a real
staging capture over the network, a live browser UI check, and 113 tests. Running
it for real exposed seven defects, all fixed here — including a .dockerignore
that baked the access token into the image, a Chromium sandbox that could not
start in Docker, and a schema change that could not open an existing database.
docs/VERIFICATION.md lists every one, and what is still unverified.
Read it before it renders. A build can stop after capture. Nothing has been
encoded and no provider contacted; you edit each scene's headline, supporting
line and caption as a typed diff, then approve. A finished campaign re-renders
from material it already has, so one CTA can change without re-recording or
paying again.
Distribution that admits what it does not know. Releasing a campaign is a
separate act from finishing it. Remote state is read back from Postiz rather than
inferred from acceptance, and an uncertain send is resolved by a person
identifying the real post — never by a retry button.
Also: three visual directions, capture trimming, imported cursor-event tracks,
music and narration mixing, landing-page deployment behind a fingerprinted
preview, signed and deduplicated conversions, and Japanese line breaking that
follows kinsoku shori.
Apache-2.0. Single-operator alpha — do not expose it to the internet as a
multi-user service.