NixOS · x86_64 · self-installing

ARCADEOS

An arcade cabinet is an appliance. This one installs itself from a USB stick, pulls its own configuration, and stays exactly as configured — because the whole machine is written down, not set up by hand.

What it is

Written down, not set up

A cabinet is a Nix flake in its own private repository. Emulators, frontend, storage layout, light-gun drivers — all of it declared. Nothing is configured by hand on the machine, so nothing is lost when the disk is.

One ISO, one question

The installer asks which disk to use. After that there is no keyboard work: it fetches the cabinet's configuration, installs it, and reboots into the frontend.

Every change is reversible

Configuration is versioned. Added an emulator that broke the frontend, or took an update that went badly? Pick the version from before and put it back.

Supported hardware

One emulator per generation, chosen on merit

No single emulator is best at everything, so each kind of hardware gets the one that actually plays it. Where a loader would just wrap somebody else's emulator, the cabinet goes to that emulator directly — which leaves TeknoParrot doing the job only it can, the boards that really are PCs.

Hardware Runs on — select to see its games Why this one
Arcade, generally mame-no-nag MAME with the startup warning screen patched out — a cabinet has nobody to press OK.
Sega Model 2 mame-no-nag MAME's Model 2 drivers are good enough; Virtua Cop 1 and 2 have worked since 0.196.
Sega Model 3 supermodel MAME's Model 3 drivers are not playable. Supermodel is the only real option.
NAOMI, NAOMI 2, Atomiswave, Dreamcast flycast Far ahead of MAME on this hardware, and where most of the light-gun catalogue lives.
Sega Triforce dolphin-emu GameCube silicon in an arcade cabinet — Mario Kart Arcade GP, F-Zero AX, the Virtua Striker games. Triforce support reached mainline Dolphin in 2026, so no fork is needed.
Namco System 246 / 256 pcsx2x6 PlayStation 2 silicon in an arcade cabinet — Time Crisis 3 and 4, Taiko no Tatsujin. Mainline PCSX2 will not run them; this fork adds the coin inputs, service buttons and I/O the boards need.
Laserdisc hypseus-singe Dragon's Lair, Space Ace and the rest of the Daphne catalogue.
PC-based arcade (Lindbergh, and the rest) teknoparrot Where the board really is a PC. It loads Windows binaries, so each title is still its own Wine work.

See what runs on each board →

Frontend

Attract-Mode Plus

A display and a config written per installed emulator, so nothing installed is invisible.

Light guns

Sinden · OpenFIRE

A Sinden enumerates as two devices, mouse and keyboard, mapped separately.

How a cabinet comes up

From bare disk to attract mode

  1. 01

    Name the cabinet

    Add it in the portal. It gets a private repository, seeded with a working configuration, before any hardware is involved.

  2. 02

    Boot the installer

    Write the ISO to a USB stick. It asks which disk to install to. That is the only question.

  3. 03

    Link the machine

    The cabinet shows four letters and two words. Type the letters into the portal on your phone; the portal shows you the two words back. If they match the screen, confirm.

  4. 04

    It builds itself

    The cabinet clones its configuration with a key it generated on itself, installs, and reboots into the frontend. Nobody types a password or a token on an arcade cabinet.

What it handles for you

No compiling on the cabinet

CI publishes one binary cache per application, so a cabinet that only runs MAME downloads only MAME. An arcade machine should not spend a night building an emulator.

Your settings survive rebuilds

Attract-Mode layouts, per-game input remaps, TeknoParrot profiles — none of it is reproducible from the flake, and all of it is what makes the machine feel like yours. It gets pushed back to the cabinet's own repository.

ROMs, managed from the cabinet

A web interface for finding, fetching and placing ROMs, with the collection area as the source and the ROM area as the destination.

It boots like an appliance

No wall of systemd output on a 32-inch monitor. A machine that works perfectly should not look broken while it starts.

Big things live on a share

ROMs and artwork can sit on a NAS without reconfiguring anything else. The cabinet does not care where they are.

Rebuilds without a shell

The on-screen configuration writes a file; a separate privileged unit does the rebuild. Nothing listening on the network runs as root.

The portal

You manage cabinets. Not git.

Cabinet owners get an account on the portal and nothing else. Add a cabinet, link a machine, look through its configuration history, put an old version back, or revoke a machine you no longer own.

The cabinet generates its own SSH key and sends only the public half. Nothing that could clone a repository is ever stored, and taking a machine's access away is deleting one key.

Open the portal