VeydrisOne

Console updates

What the console software is today, how updates reach a Veydris One, and what we still have to prove on real hardware.

Current software

Veydris One is in development, so there are two versions to know about.

Validation build

Veydris OS 0.7.1

The newest system build, made on 20 November 2026. It's a manufacturing-validation build, not a commercial release: it has to pass tests on the real board before it can become 1.0.

Development install

On the development console

The console on our bench still runs the development install (version 0.1.0, development) on its original system layout. It moves to 0.7.1 when the installer has been tested on the board.

What's in Veydris OS 0.7.1

Console system

The Veydris dashboard at 60 frames per second at 1080p, boot branding, first-time setup with a controller, Settings and display-mode switching.

Marketplace

Signed game packages only, a download manager that resumes and checks free space, the Library, free claims, checkout by QR code on your phone, and 30-day offline licences.

Game sandbox

Games run without system privileges in their own namespaces, with no access to account tokens, keys or other games' saves.

Two system slots

A signed update installs to the slot that isn't running. If the new system fails to start, the console goes back to the one that worked.

Recovery

A separate recovery system can restart, roll back, factory-reset, install an update from USB and run network diagnostics.

Locked down

No developer accounts or keys in the image, remote login disabled, and a firewall that blocks all inbound connections. Each console creates its own identity on first start.

New since 0.7.0

  • A firewall on the console that refuses all inbound connections by default.
  • The dashboard removes licences for games you no longer own and renews a licence before launch when online.
  • A "not in library" badge, and a controller keyboard over the payment page.

How a system update works

Nothing unsigned gets in. An update that fails a check is discarded and the console carries on with the system it has.

  1. The console asks for its release

    While online, the console asks the update service whether a newer version exists on its channel: stable, or developer for early builds.

  2. The update is downloaded and checked

    The console verifies the Veydris signature and the contents before anything is written. Updates are signed for this board and refused on any other.

  3. It installs to the other slot

    The running system is never overwritten. The update goes to the second slot, and the console starts it on a trial.

  4. It keeps the update only if it starts

    If the new system doesn't come up, the console rolls back by itself. After three failed starts it opens recovery.

Still to be tested on the real board

The update, rollback and recovery path has passed its tests in simulation only. Before 1.0 it has to pass on the hardware:

  • The bootloader test on the board.
  • A first installation from microSD to the NVMe drive.
  • A system update with rollback, and recovery, on the two-slot layout.

Also not validated yet: 4K output and HDMI audio.

Game updates

Games update separately from the system, through Downloads on the console. A game's patch notes are shown on its Marketplace page.