
Forget AmigaOS 3.3 for a moment. The bigger story sits a little further ahead. On 1 January 2028, Hyperion Entertainment’s transitional role with 68K AmigaOS reaches its endpoint, leaving Amiga Corporation with far more control over where classic AmigaOS goes next. Hyperion, meanwhile, keeps AmigaOS 4. Commodore now sits close enough to the story to make the next phase far less predictable. AmigaOS has never been easy to explain, and the version numbers don’t help. This is why 2028 matters more than another point release. Under the agreement between Amiga Corporation and Hyperion Entertainment, Hyperion’s present role in the 68K branch runs through a transition period ending no later than 31 December 2027. From 1 January 2028, Amiga Corporation gets a much clearer hand in deciding how classic AmigaOS develops, how it’s licensed and how future releases are presented.
Hyperion leaves 68K, but keeps AmigaOS 4
Here’s where the picture becomes more unusual. Hyperion isn’t leaving AmigaOS. It retains its independently developed AmigaOS 4 technology and can continue developing the system under its licensing arrangement. AmigaOS 4 is no longer tied exclusively to PowerPC either, opening the door to another processor architecture, with 68K excluded from Hyperion’s area.
So 2028 could bring two current AmigaOS families at once. Amiga Corporation could develop the direct 68K continuation of classic AmigaOS, with Hyperion pushing AmigaOS 4 on PowerPC or another architecture. From a legal point of view, the split is cleaner. From a customer point of view, it could become harder to explain.
A future Amiga Corporation release might be aimed at classic machines, FPGA hardware or a new compatible system. Hyperion could be working on AmigaOS 4 for a completely different class of hardware. Both products could carry the AmigaOS name. Both could be actively developed. Yet they would come from different companies and follow separate technical paths.
One name, two AmigaOS families
The awkward part is easy to see. Suppose Amiga Corporation releases AmigaOS 3.4, 3.5 or a product with a completely new name, with Hyperion releasing another AmigaOS 4 version around the same period. Which one is current? Both could be. Which one is newer? The version number might not give a useful answer.
Mike Battilana has raised concerns around this naming problem before. His criticism isn’t aimed at dismissing the development work in AmigaOS 3.2 or 3.3. The issue is how difficult the sequence has become to read from the outside. AmigaOS 3.9 sounds newer than AmigaOS 3.2. AmigaOS 3.1.4 sounds older again. Yet those numbers don’t describe one clean chronological line.
Experienced Amiga users can work it out. A new buyer shouldn’t need a history lesson before choosing an operating system. Once Amiga Corporation controls its own 68K direction, naming could become almost as significant as coding.
Amiga Corporation gets room to choose
The most straightforward route would be continued development of classic AmigaOS. Amiga Corporation could focus on storage, networking, graphics, drivers, compatibility and support for newer expansion hardware, building on the existing 68K line without trying to reshape the whole product at once.
A more ambitious route would involve licensing. Amiga Corporation could build future releases around new hardware instead of treating AmigaOS mainly as an upgrade for machines already carrying a licensed operating system. This is where the 2028 change starts to matter commercially.
A newly manufactured Amiga-compatible computer needs a legal operating system. The same applies to an FPGA system or a commercial emulation product sold as a complete machine. With more direct control over future 68K releases, Amiga Corporation can decide how such licences work, who can use them and what kind of hardware can ship with an official AmigaOS package. No new machine has been announced. The difference is simple: the route to such a product becomes much easier to see.
Commodore enters the picture
Commodore makes the story harder to predict. The current Commodore company controls the Commodore and C= brands, with Amiga Corporation holding the Amiga identity and relevant Amiga intellectual property. They remain separate companies, yet a licensing relationship now exists between them.
This matters for one practical reason. A future Commodore-Amiga product wouldn’t require a corporate reunion. Commodore could handle hardware, manufacturing, retail and distribution, with Amiga Corporation licensing the Amiga name, operating system and related software rights.
Such a machine could use FPGA hardware, emulation or a newly engineered 68K-compatible design. No Commodore Amiga product has been announced, so this remains a scenario rather than a roadmap. Still, the structure needed to create one is far easier to understand than it was a few years ago.
Commodore could become a hardware partner without owning AmigaOS. Amiga Corporation could remain focused on software and licensing without building every machine itself. If the commercial terms made sense, both companies could meet in the middle.
The strange part of 2028
After years of legal uncertainty, AmigaOS may enter a period with clearer ownership but a more complicated product identity. Amiga Corporation can take classic 68K AmigaOS in one direction, Hyperion can take AmigaOS 4 somewhere else, and Commodore could join the picture as a hardware or branding partner if a suitable deal appears.
This could produce a cleaner market, with each product given a clear role. It could produce the opposite, with several Amiga-branded systems using similar names and serving different machines. Much will come down to branding, licensing and how clearly each company explains its product.
So 1 January 2028 won’t bring a dramatic switch or a new desktop overnight. It marks a quieter change, but a significant one. For years, discussion around AmigaOS kept circling around rights, agreements and ownership. From 2028, the question gets far more interesting. What do they actually build next?














