Skip to content

Demo

Vidra v0.5.0, running.

There is no public instance to click around yet. There is a running one: these are captures of v0.5.0 on a local machine.

Watch

The watch page.

Every image on this page is a screenshot of the real frontend talking to the real backend, all four repositories checked out at the v0.5.0 release tags. The 47-second clip was uploaded through the studio, transcoded by the instance's own pipeline to a four-rendition H.264 HLS ladder, and is what the player is playing.

The quality menu shows the result: Auto plus 1080p, 720p, 480p and 360p — the ladder the instance produced from a single 1080p upload, selectable mid-playback.

The Vidra watch page mid-playback with the quality menu open, listing Auto, 1080p, 720p, 480p and 360p, with Auto currently playing 1080p.
Captured 2026-08-29 from Vidra v0.5.0 running locally via docker compose — all four repositories at the v0.5.0 release tags. The video shown was uploaded through the studio and transcoded by the instance itself.

Publish

The upload sheet.

Upload starts on file pick and processing runs in the background while the metadata gets filled in — title, category, language, license and tags.

The studio upload sheet: vidra-demo.mp4 at 100 percent and processing, with title, description, category, language, license and tags fields filled in and an ActivityPub badge in the corner.
Same instance: Vidra v0.5.0, running locally, 2026-08-29.

Operate

The jobs view.

The operator's view of the pipeline: every queue's health on one screen, and the transcode job that built the ladder above, finished with nothing failed.

The admin console's jobs view: queue cards each reporting ok, and a transcode jobs card showing its job done with none failed.
Same instance: Vidra v0.5.0, running locally, 2026-08-29.

Configure

The admin console.

Instance configuration: this instance's name and description were changed here at runtime, no restart of the API.

The admin console's instance configuration page: general settings with the instance name and short description overridden from their defaults, sections for VOD, live, federation and customization, and a save changes button.
Same instance: Vidra v0.5.0, running locally, 2026-08-29.

In your pocket

The same instance, at phone width.

The watch page again at 390 pixels wide: the player with its controls, then the title, actions, tags and description — the frontend reflows rather than shrinks.

The Vidra watch page at phone width: the player with controls, then the title, view count, follow button, like and save actions, category, tags and description.
Same instance: Vidra v0.5.0, running locally, 2026-08-29.

What this page is not.

A public demo instance still does not exist. When there is one to try, it will be here: a real instance on the current release, sign-in credentials published on this page, reset on a schedule — not a sandbox with the interesting parts switched off. Until then, the fastest way to click around a Vidra instance is to run one.

One command. 4 vCPU. About $63 a month.

Install