Hyperion and Amiga reach settlement over AmigaOS rights and development

Hyperion Entertainment and Amiga Corporation have settled their ongoing legal disputes, bringing a long period of uncertainty to an end. The deal does more than stop the court battles. It also sets out who can develop and sell different versions of AmigaOS, what happens to the 68K branch after 2027, and how Hyperion can continue working on AmigaOS 4.x. That gives both companies a clearer path forward.

Hyperion can continue developing AmigaOS 4

Under the new agreement, Hyperion will keep developing and distributing AmigaOS 4 under licence from Amiga Corporation. That matters because AmigaOS 4.2 remains one of Hyperion’s main development goals. The company hasn’t announced a release date, a final feature list or confirmed hardware support, so there’s still plenty we don’t know. Still, the settlement removes a major legal distraction from the project.

Hyperion’s own AmigaOS 4 code remains separate from the Amiga technology it uses under licence. The agreement draws a clearer line between the two, giving Hyperion a defined basis for continuing its work on the PowerPC-based operating system. For AmigaOS 4 users, the message is fairly simple. Development can continue.

That doesn’t mean AmigaOS 4.2 is suddenly around the corner. Legal clarity can help a software project, but it can’t replace coding, testing or hardware support. Hyperion will now have to show progress through technical updates and actual releases.

AmigaOS 3.3 can go ahead, but there’s a deadline

The situation around the 68K version of AmigaOS is different. Hyperion can continue selling AmigaOS 3.2 and the planned AmigaOS 3.3 during a transition period. These releases are treated as upgrades for existing licensed Amiga systems. That permission ends on 31 December 2027.

After that date, Amiga Corporation will take charge of the future development of AmigaOS for 68K machines. Hyperion therefore has a limited window to finish, release and sell AmigaOS 3.3. The deadline gives the classic operating system branch a much clearer direction. It also raises some obvious questions. Hyperion hasn’t announced when AmigaOS 3.3 will arrive, what it will include or how updates and support will work after the end of 2027.

Those details will matter. For now, the agreement allows Hyperion to complete its planned release while giving Amiga Corporation control of what comes next.

Hyperion will hand over source code and documentation

The settlement also covers technical material from AmigaOS 3.1.4. Hyperion will provide Amiga Corporation with the source code, revision history and documentation for that release, including its fixes and updates. Code taken from AmigaOS 4 and later added to AmigaOS 3.2 or 3.3 won’t be part of the transfer.

That distinction keeps Hyperion’s AmigaOS 4 work separate while giving Amiga Corporation access to the material needed to continue development of the 68K operating system. The agreement will also free developers and contractors from restrictions that might stop them from working directly with Amiga Corporation. In practical terms, Amiga could hire people who already understand the code instead of building a new development team from scratch. That could make the handover easier, although no future team or development plan has been announced.

Amiga and Commodore have also clarified their rights

A separate agreement between Amiga Corporation and Commodore International Corporation deals with the names, trademarks and historical software linked to the two brands. Amiga recognises Commodore’s ownership of the Commodore name and the familiar C= trademarks. Amiga Corporation keeps the Amiga trademarks and says it holds the copyrights to historical Amiga and Commodore software, firmware, documentation and hardware designs.

The arrangement allows Commodore to use licensed 8-bit software and documentation in its products. Amiga can still reproduce Commodore marks when they appear inside original software, manuals, keyboard layouts and other historical material. This separate deal doesn’t directly decide the release plans for AmigaOS 3.3 or 4.2. What it does is reduce another area of uncertainty around who controls which names and assets.

Now the attention turns back to the software

The legal disputes are over. The responsibilities are clearer. There’s even a firm date for the 68K transition. But the settlement is only a starting point. Hyperion now needs to finish AmigaOS 3.3 and show meaningful progress on AmigaOS 4.2. Amiga Corporation, meanwhile, has to explain what it plans to do with 68K AmigaOS after it takes control.

Release dates, prices, supported hardware and upgrade options remain unknown. So do the long-term plans for developers and users. For the first time in a while, though, the next major AmigaOS story doesn’t have to come from a courtroom. It can come from the development team.

Spread the love