# ravynOS: a Darwin and FreeBSD based attempt at macOS compatibility

> ravynOS is an open source operating system that aims for source compatibility with macOS applications on x86-64, built on Darwin and FreeBSD foundations. It is pre-alpha software with a demo VM image and a Linux cross toolchain, so the practical question is what you can actually build and run today.

**ravynsoft/ravynos** — An open-source OS project that aims to provide source and binary compatibility with macOS® and a similar user experience.

- Repository: https://github.com/ravynsoft/ravynos
- Website: https://www.ravynos.com
- Stars: 7,046 · Forks: 243
- Language: C
- License: not declared
- Published: 2026-09-22 · Updated: 2026-09-22 · Language: en
- Canonical page: https://hysenlabs.com/projects/ravynsoft-ravynos

## What ravynOS is trying to solve, and for whom

The README states the goal plainly: ravynOS aims to provide a similar experience and some compatibility with macOS on x86-64 systems, with arm64 and arm64e described as eventual targets. The project builds on Darwin and FreeBSD rather than starting from a Linux kernel, and it fills the gaps with new code. The stated design goals include source compatibility with macOS applications, meaning you could compile a Mac application on ravynOS and run it, with binary compatibility listed as a later objective.

The audience follows from that. This is for developers who want to port or compile Cocoa-era applications without owning Apple hardware, and for people interested in the Darwin and FreeBSD lineage as a desktop base. The compatibility targets are specific: macOS folder layouts such as /Library, /System, /Users and /Volumes, filesystems including HFS+ and APFS alongside FAT, NTFS and ZFS, and self-contained App Bundles with support for DMG files. That is a concrete list rather than a vague promise of looking like macOS, and it is the part of the README worth reading closely.

## How the build tree is organised, and what the Makefile reveals

The top-level Makefile is the clearest signal of how the system is assembled. It defines a version and a family, and the family is not flattering: PROD_VERSION is 0.7.1 and PROD_FAMILY is Pre Alpha. The world target chains the major pieces in order: version, Developer, Kernel, Libraries/libfirehose_kernel, Libraries, then BSD. That ordering matters because it tells you the kernel and the library layer are built before the BSD userland that sits on top.

Architecture selection is explicit. ARCH_CONFIGS is set to X86_64 and KERNEL_CONFIGS to RELEASE, and the Makefile branches on MACHINE to decide between BuildArch X86 with CpuArch x86_64 and BuildArch AArch64 with CpuArch aarch64. The repository layout mirrors the macOS naming conventions the project is chasing: CoreServices, Frameworks, PrivateFrameworks, SysApps, SystemLibrary and Developer directories sit next to BSD, Kernel and Libraries. There is also an ISO directory and an installravynos directory, which is where installation media is produced.

One detail is worth flagging for anyone building from source. The Makefile sets CFLAGS to -Wno-incompatible-sysroot with a comment about not warning on ravynOS.sdk versus MacOSX.sdk naming, and it branches on the host OS: if the make OS is Darwin it uses the host CC, CXX and AR, otherwise it falls back to /usr/bin/cc, /usr/bin/c++. That fallback is the reason the project ships a separate Xcode toolchain for Linux instead of assuming a Linux host can build everything with its default compiler.

## Installing ravynOS and getting to a first build

The README does not contain step-by-step installation instructions. It points to the project homepage at ravynos.com and to CONTRIBUTING.md for current projects and needs, and the repository publishes release artifacts rather than an install walkthrough. The releases list includes a demo VM image named demo-vm from 2026-07-25, an SDK and KDK release named SDK_0.7.0.1 for x86_64 from 2026-02-07, and a Linux toolchain release named linux_tc_0.2 for Linux x86-64 from 2025-12-24. If you want to see the system without building it, the demo VM image is the artifact the project provides for that purpose.

For building from the tree, the Makefile is the entry point. It expects one architecture and one kernel configuration to be selected, and the defaults are already set to the x86-64 release path:

```makefile
ARCH_CONFIGS = X86_64
KERNEL_CONFIGS = RELEASE
```

The top-level target that assembles the system is world, and the Makefile defines it as a dependency chain. Running the build means invoking that target with make, with the object directory resolved relative to the source tree:

```bash
make world
```

The Makefile sets ROOT_BINARY_DIR to a build directory alongside the source root and sets MAKEOBJDIRPREFIX to the same location, so output does not land inside the source tree. If your host is not Darwin and you do not supply a toolchain bundle, the build falls back to the system compiler paths:

```makefile
HOST_CC ?= /usr/bin/cc
HOST_CXX ?= /usr/bin/c++
HOST_AR ?= /usr/bin/ar
```

That fallback is where the Linux toolchain release becomes relevant. The README does not document what a successful build produces beyond the world target's component list, and it does not describe flashing the ISO directory output to a disk or booting it on real hardware.

## Where ravynOS will disappoint you

The project calls itself Pre Alpha in its own Makefile, and that label should be taken at face value. The README lists binary compatibility as an eventual goal rather than a current one, which means the practical ceiling today is compiling source against the provided SDK and KDK, not dropping in a downloaded Mac application and expecting it to launch. Anyone reading the compatibility goals as a shipping promise will be misled by their own optimism, not by the README, which is careful to separate source compatibility from binary compatibility.

Architecture support is the second constraint. The stated target is x86-64 with arm64 and arm64e described as eventual, and the SDK release is explicitly labelled x86_64. The Makefile can select an AArch64 build path, but the published artifacts are x86-64, so an Apple Silicon user has no documented route from the releases list to a running system.

The documentation gap is the third. The README does not document rollback, recovery, upgrade procedure or hardware support requirements. There is no installation section, no list of supported GPUs or Wi-Fi chipsets, and no statement about what happens when a build fails partway through the world target. For an operating system, those omissions are not minor. If you need a machine that boots reliably every morning, ravynOS is the wrong tool and the project's own version string says so.

## How ravynOS differs from helloSystem and Airyx

The related searches around this project include helloSystem and airyxOS, and the comparison is fair because all three occupy the same niche from different angles. helloSystem is a FreeBSD-based desktop that aims for a macOS-like experience through its own application and desktop conventions, which means it borrows the look and the workflow without claiming source compatibility with Mac applications. ravynOS takes a different route: it keeps Darwin and FreeBSD as foundations and builds compatibility layers for macOS folder layouts, App Bundles, DMG files and the Apple APIs that applications expect. The README's phrase about providing the expected Apple APIs to applications is the dividing line.

Airyx is the earlier name associated with this same lineage, and the related searches still carry it. The practical difference between the three is what you are trying to accomplish. If you want a FreeBSD desktop that feels familiar and runs FreeBSD packages, helloSystem is the closer fit. If you want to compile Objective-C and Cocoa code against an SDK that mirrors Apple's, ravynOS is the one making that specific claim. Neither approach is a substitute for the other, and neither gives you a supported Mac.

## Licence, maintenance and what upgrading costs you

The repository metadata does not list a licence, and the README does not state one. That is a real gap rather than a technicality. ravynOS incorporates Darwin and FreeBSD code, which carry their own licence terms, and the project adds new code on top. If you plan to redistribute anything you build, or to ship a product that links against the SDK, the absence of a stated project licence is the first thing to resolve, and resolving it means asking the project rather than assuming. Nothing here is legal advice, but a missing licence field is a concrete blocker for commercial use.

Maintenance is easier to judge. The last push to the default darwin branch was on 2026-09-06, and the repository is not archived. The most recent release is the demo VM image from 2026-07-25, followed by the SDK and KDK at 2026-02-07 and the Linux toolchain at 2025-12-24. That is roughly a release every few months across different artifact types, which suggests the project is moving but not on a schedule you can plan a product around. The Makefile pins PROD_VERSION to 0.7.1, and the related searches still include ravynos 0.6, so version drift between what people search for and what the tree contains is normal here.

Upgrade cost is undocumented. The README says nothing about upgrading an installed system, and there is no migration note attached to the SDK release. Treat each release as a fresh start until the project says otherwise.

## Conclusion

ravynOS is for developers who want to compile and run Mac-style applications on non-Apple hardware and are willing to work inside a pre-alpha tree, using the demo VM image or the SDK and KDK release to get started. It is not for anyone who needs a daily driver, since the project itself labels the version Pre Alpha and the README does not document rollback or recovery paths. Before committing time, verify that the SDK_0.7.0.1 and demo-vm artifacts match your architecture, and check whether the Xcode toolchain for Linux release covers your host, because the build system expects either a Darwin host or a toolchain bundle.

## FAQ

### Is macOS just FreeBSD?

No. The ravynOS README describes Darwin and FreeBSD as separate foundations that the project builds on together, with new code filling the gaps, and it lists Darwin lineage topics such as mach and xnu alongside freebsd. ravynOS itself is not macOS and does not claim to be.

### Which Linux OS is closest to macOS?

The available documentation does not compare Linux distributions on macOS similarity, and ravynOS is not a Linux OS: the README states it builds on Darwin and FreeBSD. The project does publish linux_tc_0.2, an Xcode toolchain for Linux x86-64, but that is a build tool for Linux hosts, not a Linux desktop.

### Does Apple still use Darwin?

The README does not answer this. What it does say is that ravynOS builds on the foundations of Darwin and FreeBSD, and the repository carries darwin as its default branch name, which is a statement about ravynOS rather than about Apple's current practices.

### Is macOS basically Linux?

The README does not address macOS internals. It describes ravynOS as building on Darwin and FreeBSD, with a repository layout containing BSD, Kernel, Frameworks and Libraries directories, which is a different lineage from Linux.

### How do I install ravynOS?

The README does not include installation steps. It points to the project homepage at ravynos.com and to CONTRIBUTING.md, and the releases list provides a demo VM image named demo-vm plus an SDK and KDK release for x86_64, which are the artifacts the project publishes for getting started.

## Sources

- [Issues](https://github.com/ravynsoft/ravynos/issues)
- [Project website](https://www.ravynos.com)
- [ravynsoft/ravynos on GitHub](https://github.com/ravynsoft/ravynos)
- [README](https://github.com/ravynsoft/ravynos/blob/darwin/README.md)
- [Releases](https://github.com/ravynsoft/ravynos/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/ravynsoft-ravynos