Your audience wants to know one thing before a launch: will it actually go? Rocket Assessor scores every active pad on Earth and shows the reasons. Drop it into a live blog, broadcast graphic or stream overlay in one line of HTML.
This is the live widget, updating right now — the next launch with a scored verdict:
<iframe
src="https://rocket-assessor-engine.zeronoisereport.workers.dev/embed/next"
width="100%" height="330" frameborder="0" loading="lazy"
title="Launch weather verdict — Rocket Assessor"></iframe>
That is the whole integration. It self-refreshes every five minutes, so a live blog stays current with nobody touching it.
| Parameter | Values | Effect |
|---|---|---|
theme | dark · light | match your site |
compact | 1 | slimmer card for sidebars |
reasons | 0 | hide the reason chips |
/embed/next?theme=light&compact=1
/embed/verdict/<launchId> <!-- pin to one specific launch -->
/embed/card/next.svg <!-- static SVG for graphics packages -->
| Rocket Assessor | Generic forecast | |
|---|---|---|
| Scope | Every active pad, globally | Cities |
| Output | GO / CAUTION / NO-GO + score | Raw conditions |
| Reasoning | Shown — wind, gusts, cloud, precip, storm energy | None |
| Independence | Not affiliated with any launch provider or range | — |
| Integration | One iframe, no JS, no tracker | — |
The branded embed, free.
or $1,499/yr — two months free.
White-label & annual available.
Sign-in takes 20 seconds · Stripe checkout · cancel anytime
No. The widget is a single self-contained iframe with no external fonts, no analytics and no third-party requests. It cannot leak your readers to anyone, and it works under a strict CSP.
Yes — /embed/card/<id>.svg gives you a clean static card. Broadcast and video use
is covered from Launch Desk upward; attribution is required unless you're white-label.
The engine rebuilds every 10 minutes from Launch Library 2 (schedule) and Open-Meteo (forecast). The widget refreshes itself every 5 minutes.
We log it. Every verdict is frozen at T-24h and scored against the actual outcome, and the
record is public at /api/accuracy. We would rather be checkable than impressive.