Phone, tablet, or computer
Viewers open the local address. There is no separate control app to install.
Current feature record
Every feature, with its current status.
Review live viewing, recording, clip requests, production outputs, Flight Log, networking, and field operation. Each section states what works and what remains to be checked.
Available
Validation
Planned
Research
Evidence baseline: product commit 28605da · 1 August 2026
$29.99 USD one-time · pre-release
Cosmik’s own USB capture receives the DJI Goggles 3 picture on a Raspberry Pi 4. The ordinary live path passes the H.264 stream through without a video transcode, then serves it to browsers on the local network.
Watching is separate from control
The visitor screen does not expose the password-protected owner console.
No internet needed on set
The Streamer provides its own field network. Internet is only required for an internet destination.
Fit, fill, fullscreen, snapshot
The Flight View keeps the picture dominant while exposing the live controls around it.
Live viewing and flight data are separate permissions. Leave either one closed, open it to everyone on the local network, or require a code handed to a specific client or crew group. Changing access does not restart the feed or recording.
Off, Open, Invited
Four things are handed out separately — watching the picture, seeing flight data, reviewing past flights, and letting a viewer request a clip. Each is set on its own, and each can be changed while you are flying.
Issue and revoke locally
Name a code for the client or crew, copy it once, then take the whole code away when the job ends.
Remove one guest
The Streamer records only a local guest-device identity—no guest email, phone number, or profile.
Carry on or start fresh
After a restart the owner decides whether earlier codes and invited access reopen.
Exact boundary: live viewing and flight-data permissions are built and test-covered. All four permissions are built and enforced on the device; the console shows only the permissions it actually enforces.
Recording is managed independently from the live output, so starting or stopping a file does not restart the picture. Auto-record can follow the feed, or the owner can control it manually from Flight View.
Browse and play
Each completed session shows a thumbnail, local date and time, file size, and playback control.
Download the original file
Every recording has a direct download action for off-device storage or editing.
No scheduled deletion
The device does not discard footage by age or count. Deletion is per file and confirmed.
Fast browser playback
Completed crash-safe fragmented MP4 files are finalized in the background for fast start and seeking.
The last ten minutes, off by default
The writer and controls are built. Saving a permanent clip from that buffer is the remaining part and is still marked Coming soon.
Validation still named: the 20%, 10%, 5%, and full-disk guard is
implemented and host-tested, but the complete physical fill-disk exercise is still
outstanding. The website does not call that check complete.
Open a recording, move the In and Out marks around the exact section, identify the requester, and explain the cut. The queue remains attached to the recording rather than living in texts or notes somebody has to interpret later.
Visual In and Out handles
The selected band, playhead, start, end, and duration remain visible together.
Requester and edit note
Record who wants the shot and what the editor is meant to take from it.
Requests on the same timeline
See earlier requests in their own lane and select one to load its range without confusing it with a new selection.
Pending, approved, done
Move a request through a simple production state without deleting its context.
Outstanding shot list
Export the active requests. Once the card has been read, each row also names the aircraft's own file and the in and out points on it.
One GyroFlow project per request
The ranges, the shot list, and the instructions travel together — written onto the card by a single button, so there is no folder to find and nothing to copy by hand.
Where this stops: the whole chain — mark a shot, write the card,
open the free Exporter, get stabilized clips — has been run end to end on real
hardware with a real aircraft card. The match lands within about five seconds, which
finds the shot rather than cutting it frame-exact, and the step where the pilot
nudges it to the exact frame is not built. A client can mark their own moments
without your console password: if you turn it on, viewers browse past flights and send
you a clip request with their name and a note attached.
WebRTC, HLS, and RTSP are available from the device. The owner can also create independent RTMP or RTMPS, SRT, and MPEG-TS targets for a platform, production truck, decoder, or another server.
WebRTC, HLS, RTSP
The Destinations page shows copyable live addresses for the clean and broadcast outputs.
YouTube, Facebook, Twitch
Presets seed the correct destination type while the stream key remains owner-supplied.
SRT and MPEG-TS
Add a custom transport address rather than being limited to consumer-platform presets.
Independent reconnects
A target can reconnect without stopping local viewing, recording, or a different target.
Branded or Pilot feed
The newer per-destination source choice is implemented and host-tested. Its end-to-end branded destination remains in Validation.
Current boundary: clean destinations are established. Automatic
start of the shared broadcast branch for a Branded destination has not yet been
watched at a real destination from the current device build.
An optional Raspberry Pi hardware-encoded branch can frame the incoming picture for production and burn in a logo, lower-third, or timecode. The ordinary live view and goggles feed remain clean.
Fit, Fill, Crop
Choose whether to preserve every edge, fill the frame, or crop deliberately.
1080p or 720p output
Bitrate remains adjustable, with defaults tied to the selected output size.
Logo and lower-third
Choose corner, opacity, size, display name, and pilot identifier.
See the real broadcast snapshot
The Branding page displays the actual output rather than asking the owner to trust saved settings.
Current limitation: DJI’s Camera View Recording mode produces a
1920×1080 at 60 fps HUD feed. The current software decoder cannot keep the broadcast
branch real-time in that mode. The clean HUD capture works; HUD plus the re-encoded
broadcast branch does not yet.
When there is no live picture, the guest page can show an owner-supplied image or short looping video, a chosen message, its position, and how long it has been since the last picture. The same uploaded photo or video is used on the HDMI monitor, and looping video playback there has been physically verified. Live video always takes priority.
Cosmik identifies a connected display from its hardware data, reports the native resolution, and stores a Fit, Fill, or Crop preference for that exact monitor. Between feeds, the display shows the uploaded standby photo or looping video rather than a Linux login. The HDMI video-splash path has been verified on the physical monitor.
Verified on hardware: the player, the standby photo or looping video,
connected-screen detection and the per-monitor presets have all been driven on a real
monitor with the live picture — including a live pipeline swap when the framing is
changed. What is not written yet is the customer page in the manual for this screen.
The Streamer writes down every flight on its own, once a second, without being asked. Afterwards there are four ways to read it: the route flown back in three dimensions, one shared timeline, the link in detail, and what the aircraft itself was doing. GPS is optional — the time-based review works on an aircraft that has none, which is most freestyle quads and all indoor flying.
The route, in three dimensions
Orbit and zoom the line you actually flew, coloured by height, signal, speed, or battery. Scrub it, and open the footage from any point on it.
One shared timeline
Link quality, picture state, battery telemetry, and notable moments stay aligned.
Watch this moment
When a recording exists, open it at the flagged point instead of searching the whole flight.
Uplink and downlink stay separate
Review controls reaching the aircraft separately from the readings coming back, including changing transmitter power.
Pitch, roll, and yaw
Recorded from the flight controller itself. Flights before 31 July 2026 predate this and say so rather than drawing a flat line.
Owner console only
Flight history and location stay behind the owner sign-in rather than appearing in the guest viewer.
Why this is still “Validation”: the data and every view are built, and
the flight log is trusted enough that the Streamer uses it to work out which of the
aircraft's own recordings a marked shot belongs to — which it has done on real
hardware. What is still owed is a measurement, not a feature: how smoothly the
three-dimensional view runs on a real phone over the Streamer's own Wi-Fi, an owner
review of it on hardware, and a check of the flat-map fallback with 3D switched off.
Until those are done, no claim is made about how it performs on your phone.
Separately, there is never a map behind the route: the Streamer makes its own Wi-Fi so
you can fly where there is no internet, and map tiles have to be downloaded. Height is
the aircraft's own estimate, not a survey — it cannot report flying below where it took
off, and the view marks those moments instead of drawing them.
The Streamer keeps its own field Wi-Fi and can also join a compatible 2.4 GHz home, venue, or portable-router network. The Console scans, joins, leaves, and shows every address where the device can be reached.
The Streamer's Wi-Fi stays available
Viewer access does not depend on the venue router or an internet connection.
One saved join
Use a venue or home network for console access, clock sync, updates, or internet destinations.
Never move while viewers are connected
If the shared radio must change channel, the product waits and explains why instead of dropping people.
Wi-Fi join or ELRS listening
The Pi has one Wi-Fi radio. While it is joined to another network, it cannot listen to the ELRS backpack.
Why “Validation”: the screen, the network manager, the safety rules and the failure states are built and test-covered, but joining someone else's network has never been done on a real Streamer. Until it has, it is not claimed as working. Naming the Streamer's own field Wi-Fi during first-time setup is a different thing, and that has been done on hardware from a freshly written card.
The appliance UI, owner account, licence check, video paths, recordings, and configuration live on the Raspberry Pi. The customer creates the owner account; there is no shipped admin login.
Self-locking first account
The setup route works once. Passwords are stored with Argon2id.
Open or invited, capability by capability
The owner can control live viewing and flight data separately, issue a code, revoke it, or remove a guest device.
Owner-chosen network
The setup wizard requires a network name, password, and the country where the radio will be used.
Offline and board-locked
A valid key starts video immediately and remains tied to the compatible Raspberry Pi board.
Launch gate: the first customer image now builds and boots on a second
Raspberry Pi 4, with port 80, MediaMTX, mDNS, no SSH, and guest redaction verified.
A rebuilt image must still prove the Wi-Fi package fixes, expand storage, explain AP
failures, and resolve first-run region settings before sale.
Cosmik Batch Exporter is a separate desktop utility. It can load ordinary folders or import the shot list bundle produced by Streamer, then run the selected jobs through an installed copy of Gyroflow.
No purchase or activation
The Exporter is free and MIT-licensed. A Cosmik Streamer licence is not required.
Four versions in one run
Choose horizontal, horizontal locked, vertical, and vertical locked outputs independently.
Open the shot list bundle
The current integration is a downloaded ZIP, not a live network connection.
No pre-trim or pre-encode
The source remains unchanged before Gyroflow reads its video and motion data.
Current boundary: the automatic match to the aircraft's own recording is built and has been proven on a real DJI air-unit card. Action-camera cards have not been tested, and Cosmik cannot yet tell from the card whether the aircraft already stabilized the footage itself. The Exporter is available to download now.
Documentation
Read the complete operating guide.
The searchable guide covers hardware, setup, live view, clips, Batch Exporter, Flight Log, outputs, OBS, networking, power, and troubleshooting.