What Was the Konix Multisystem and What Happened to It?

The Konix Multisystem was a British games console project from the late 1980s that was designed to be a flexible, upgradeable multi-purpose system — and it never reached the market. If you want to understand what it was meant to be, why it collapsed, and what physical evidence survives today, the short answer is: it was an ambitious British attempt at a modular console, it failed commercially before launch, and the main things you can still engage with are a single known development kit on public display and an online archive documenting the project. The rest of this article covers the intended design, the failure, the StarFox connection, and where to see or read about the surviving material.

What the Konix Multisystem was meant to be

The Konix Multisystem (often shortened to KMS) was conceived as more than a straight games console. The archive's own framing describes it as "the failed British games console that could have taken on the world and possibly beaten it" — a machine positioned against the dominant home systems of its era.

Its defining idea was modularity and expandability. Rather than a fixed box, the Multi-system was intended to accept different peripherals and configurations, which is where the "multi-system" name comes from. That flexibility is also why the project attracted attention well beyond what a typical unreleased console would: it promised a platform rather than a single product.

Because the system never shipped, most of what is known about its capabilities comes from development hardware, trade-show demonstrations, and documentation rather than from consumer units. Treat any specific performance claim you see about the KMS as something to check against the archive's primary material, since the project changed over time and much of the record is reconstructed.

Why it failed and was never released

The Konix Multisystem is a case study in a console that got close enough to be shown publicly but never made it to shelves. The archive's own description is blunt about the outcome: it is "the failed British games console."

What the available material supports is the shape of the failure rather than a single cause:

• It never became a shipping product. There are no consumer units, which is why surviving hardware is described in terms of development equipment rather than retail consoles.
• The surviving record is fragmentary. The archive exists precisely because the information is scattered and partly lost — its stated purpose is "providing an archive of all information worth knowing" about the system.
• Even the hardware that survives is uncertain. The one known development kit is noted as having no guarantee that its custom ASIC still works, while the rest is described as off-the-shelf electronics that would be relatively easy to repair.

If you are researching the failure specifically, the honest position is that the archive is the place to look, and that some questions may not have a fully documented answer. Avoid treating any single retrospective explanation as settled.

The StarFox connection

One of the more surprising threads in the KMS story is its link to StarFox. According to the archive's news section, "if it weren't for the Konix Multisystem, StarFox might never have happened at all," and it points readers to a fuller account of the system's role in StarFox's origin.

This is the kind of claim worth reading in full rather than repeating second-hand. The archive treats it as a documented connection and links to its own write-up, so if the StarFox angle is what brought you here, follow that link on the site rather than relying on a summary. The broader point is that the KMS had a footprint in game-development history that outlasted the console itself.

Surviving hardware: the KMS Devkit

The most concrete surviving artifact is a KMS development kit, and its current situation is unusually well documented.

Where it is now: The devkit is on display at the Retro Collective Museum in Stroud. It was carried from Amsterdam to Brighton on the Eurostar and then left with a friend of the museum, where it now sits alongside a PowerChair 3D model and a few accessories.

Why it matters: It is described as "the only known KMS Devkit still in existence." It was designed to work with the PDS development system, and at the museum it sits in the same room as a working implementation of the PDS system.

Its condition and prospects: There is no guarantee the ASIC still works. The rest of the unit is standard electronics and relatively easy to fix. The museum's Neil has suggested the team from Herber may examine it with the aim of fully documenting the unit's electronics — potentially producing a circuit diagram — and safely powering it up. The museum's in-house developer Jason, who has some history with the KMS PDS Devkit, might get the chance to run code on it.

Ownership: The unit is on loan to the Retro Collective and remains the property of Brian Pollock, the programmer of StarRay on the KMS.

The archive notes this is closer to a real KMS than most people have been able to get for about 30 years, since it was shown at trade shows. If you want to see KMS hardware in person, the Retro Collective in Stroud is the place the record points to — but check ahead, since the hardware's working status is not guaranteed and any power-up attempt is a project in progress rather than a finished exhibit.

Other archive material worth knowing about

The archive also documents related hardware and preservation work beyond the KMS itself. One example: a Flare One Technical Reference Manual was found, connected to research into Bell Fruit pub quiz machines based on the Flare One chipset. That research involved a former Bell Fruit programmer, Paul Arnold, and led to improved emulation of one of the Bell Fruit games and a better ROM dump for it.

This matters for KMS research because it shows the archive is actively recovering primary documentation and improving emulation of related hardware — the kind of material that fills gaps when a system's own record is incomplete.

How to use the archive

If you want to go further, the practical route is:

1. Start with the news section for dated updates, since it records finds and hardware movements as they happen (for example, the devkit's move to Stroud in October 2025, and the StarFox connection piece in May 2026).
2. Follow the linked write-ups rather than summaries — the StarFox origin article and the Flare One manual find are both referenced with pointers to fuller accounts.
3. Treat hardware claims as provisional. The single known devkit's ASIC status is unknown, and documentation is still being created.
4. Use the archive's stated scope as your filter. It aims to cover "all information worth knowing" about the KMS, so it is the natural first stop before chasing scattered forum posts.

The Konix Multisystem is best understood as an ambitious British console that got as far as trade shows and development hardware but never shipped — and whose history is still being pieced together, with one surviving devkit on display in Stroud and an archive working to document what remains.