Ceylon isn't rebuilding an old Amiga. It's exploring what some of the strongest ideas behind personal and workstation computing might have become if they had kept evolving — and trying to build that computer.
The newest entry in the Development Journal.
Project Ceylon is under a hard hold on new development: no new features until the current qualification and repair pass proves the platform is a trustworthy baseline to build on.
The long-term direction is a reasonably priced, general-purpose professional workstation.
Not a gaming machine. Not a music machine, a video machine, a development machine or a business machine. One computer that does all of those things well, with business productivity and creative work treated as equal first-class concerns.
The practical test we keep coming back to is simple enough to say and hard enough to build: could somebody sit down at Ceylon on Monday morning and reasonably leave their other workstation turned off?
That's an engineering goal, not a product claim. We're not there. The status page says how far along things actually are.
Ceylon studies older systems to recover principles, not implementations. Historical inspiration is a source of questions. It isn't the source of final answers.
A workstation should stay useful because its owner owns it. Local work should remain viable. Online services can extend the computer; they shouldn't decide whether it works.
A dated snapshot of what the public Development Journal had reported by September 25, 2026 — what was working, what was still in development, and what hasn’t been claimed. Not a roadmap or a promise.
As reported in the journal on September 23, 2026.
Work in progress and published plans as of September 23–25, 2026 — not commitments.
The rules we're using to decide what to build — and what not to.
A workstation should remain useful because its owner owns it. Local work should remain viable. Online services may extend the computer; they should not determine whether the computer works.
Buying a legitimate physical product or software copy should mean the buyer owns that item or copy. Vendors may keep their copyright, trademarks, patents and other intellectual property in the underlying work — but continued use of an owned product shouldn't depend forever on a vendor keeping a licensing server alive.
A customer shouldn't need continuing vendor permission merely to use something they legitimately bought.
If a product needs a remote service in order to function, the vendor has a responsibility to provide a reasonable exit path if that service goes away.
Real screenshots, recordings and bench photos — when they exist.
46 entries since September 6, 2026, in the order they were written.