Lantern's dark launch film, 8 scenes at 88 BPM

What happens in this clip

Lantern is an observability product, and its film opens on a title scene: the kicker “Introducing”, the name “Lantern” and the line “Observability for the 3 a.m. page”. The problem scene reads “It’s 3:12 am.” and “Checkout is slow, and nobody knows why.”, with six chips, including “Paged: checkout p95 > 800 ms”, “17 dashboards open” and “Logs: 2.3M lines”.

Four product scenes follow. Traces, “Find the slow part in one look”, calls out “76% in one query”. Incidents, “From page to cause in a click”, moves from an alerts list to an incident screen and calls out “Traced to deploy #4127”. Service map, “See where it hurts”, sits on the left and calls out “orders-db: p95 1.8 s”. On call, “Answer the page from bed”, uses a phone frame and calls out “Acknowledged at 03:16”.

A features scene, “Built for the night shift”, lists six items, from “Search every log” to “Fair on-call”. The film ends on “Now generally available” and “Free for three hosts. No card needed.”, with lantern.example as the call to action.

Compared with Nightly

Nightly, the other film from this skill, shares its tempo, 88, but tells a note-taking story. Lantern’s brief sets a ground of #0d0f1c, ink #f3f1ea and an amber accent, #f5b84a, and Nightly’s sets no colours. Lantern has four product scenes (traces, incidents, service map, on call) where Nightly has three (dark mode, schedule, mobile). Lantern’s problem scene has six chips and Nightly’s has five. Lantern’s features scene lists six items and Nightly’s lists four. Lantern’s end card says it is generally available, while Nightly’s says it is out now at version 3.0.

How the film is built

In order, the film is a title scene, a problem scene, four product scenes that each carry a callout, a six-item features scene and an end card with a web address. The Incidents scene uses an after screen and the On call scene uses a phone frame, both set in the brief.