What is Project Ceylon?
An independent operating-system and workstation project asking what the Amiga’s best ideas would have become after thirty more years — and building a modern computer to find out.
The question that started it
What if Commodore had survived and Amiga development had kept evolving for another thirty years?
Project Ceylon is an independent attempt to build one plausible answer: a modern x86-64 microkernel workstation carrying forward the Amiga's emphasis on responsiveness, multimedia, specialized subsystems, and a coherent relationship between the machine and its operating system.
The real question underneath it is narrower and more useful: which ideas from that generation of personal computing were genuinely good ideas, and what would they look like if they had kept evolving into a modern professional workstation?
What Ceylon is
An independent modern operating-system and workstation engineering project. An alternate-history engineering experiment. A computer being built in public, one dated journal entry at a time.
What Ceylon is not
Ceylon is not:
- an Amiga emulator
- an Amiga 500 or Amiga 1200 recreation
- a Workbench clone
- a Linux distribution with a retro skin
- a museum reconstruction
- an attempt to reproduce 1985 hardware
- nostalgia cosplay
It isn't a preservation project. A preservation project asks how to keep the old thing running. Ceylon asks what the old thing might have grown into — and those point in almost opposite directions once you start working.
Principles versus historical limitations
Some things about those machines were durable principles: responsiveness, asynchronous operation, efficient use of resources, modularity, specialized subsystems doing specialized work, multimedia as a first-class workload, programmability, understandable behavior, local ownership, and applications that cooperate.
Other things were just the constraints of the time: old CPU families and chipsets, small address spaces, period graphics and memory limits, old peripheral assumptions, and security models built for a very different world.
Ceylon keeps the useful ideas, modernizes how they're implemented, and drops the old limitations.
Why a modern workstation
The goal isn't a single-purpose appliance. It's one general-purpose computer that is good at business work and creative work alike — documents and spreadsheets, but also graphics, music, video, programming and games.
Whether Ceylon can get there is exactly what the project is trying to find out.
Why QEMU first
Ceylon's A1 line is QEMU-first. Instead of chasing physical hardware from day one, the project defines a virtual reference machine — the same chipset, devices, CPU model, memory layout, firmware and PCI topology every time — and keeps asking that machine the same questions.
That makes results repeatable. It also turns out the whole configuration is part of the machine: change one virtual device and you can change the behavior you're measuring. The journal has several stories about learning that the hard way.
The release line is deliberately described in broad strokes:
- A1 — the QEMU-based development and public evaluation line.
- B1 — a later move from the virtual reference environment to validated physical hardware.
- B2 — a later platform generation beyond B1.
How the work happens in public
The Development Journal is the project's running record: what was tried, what worked, what didn't, and what turned out to be wrong. Entries stay as they were written. When something changes, a later entry says so.
A few rules shape that record. "Worked once" is not an engineering state. A test that passes isn't proof until the test itself has been checked. Component success isn't the same as system qualification. And when something can be shown, the project would rather show it than ask anyone to take its word for it.