# Ora Browser: a WebKit browser for macOS built with SwiftUI and AppKit

> An open source macOS browser that wraps WebKit rather than shipping its own engine, with content blocking, a spatial sidebar and a repository that is explicit about not being ready for daily use.

**the-ora/browser** — Less noise, more browsing.

- Repository: https://github.com/the-ora/browser
- Website: https://orabrowser.com/
- Stars: 2,235 · Forks: 94
- Language: Swift
- License: GPL-3.0
- Published: 2026-10-07 · Updated: 2026-10-07 · Language: en
- Canonical page: https://hysenlabs.com/projects/the-ora-browser

## The README leads with a warning, not a feature list

The first substantive thing the README says is a note, not a pitch: Ora is still in active development and is not ready for daily use yet. That framing matters more than the tagline. The project describes itself as a fast, native WebKit browser for macOS, and the badges pin the floor at macOS 15, Xcode 15 and Swift 5.9, with a Homebrew badge suggesting at least some familiarity with package distribution. The one line description in the repository metadata is less about features and more about philosophy, reading simply as less noise, more browsing, which lines up with the stated aim of a native, low friction experience without layering on unnecessary product surface area.

The highlight list is short and specific rather than exhaustive: native macOS UI, WebKit based browsing, built-in content blocking and privacy protections, search engine customization, URL suggestions with a quick launcher, and a developer focused features bullet that the README does not expand on. There are no topics set on the repository, which is consistent with a project early enough that categorisation has not happened yet. The star and fork counts sit close together, which usually reads as a following that is actively poking at the code rather than one that only reads about it.

## Clone, run a setup script, build in Xcode

The quick start is four lines and the third one does the work:

```bash
git clone https://github.com/the-ora/browser.git
cd browser
./scripts/setup.sh
open Ora.xcodeproj
```

The README explains that the setup script installs required tooling, installs git hooks, and regenerates the Xcode project. That last clause is the important one, because it tells you the Xcode project is a build artifact rather than the source of truth. Project configuration is managed with XcodeGen through a top level `project.yml`, and the development section says to regenerate after config changes with `xcodegen`. There is no package manager manifest driving the app build, no `Package.swift` at the root, and dependencies appear to arrive through a `Vendor/` directory alongside a `THIRD_PARTY_NOTICES.md` file.

The linting and formatting setup is visible in the tree as well, with `.swiftlint.yml` and `.swiftformat` at the root and `lefthook.yml` for git hook management. Tests are split into `oraTests/` and `oraUITests/`, and the README gives both routes: run them in Xcode with Product > Test, or from the command line with `xcodebuild`. That single line is the most complete piece of build documentation in the repository, which tells you how much of this is still tribal knowledge inside the project.

## Signing credentials and an appcast mean releases ship signed

The repository carries `appcast.xml` and `ora_public_key.pem` at the root, which together indicate a Sparkle style update feed with its own key pair for verifying update payloads. The published `.env.example` is where that story becomes concrete, and it is short enough to read in full:

```bash
ORA_PRIVATE_KEY="<your_private_key>"

# Apple Developer credentials
APPLE_ID="<your_apple_id_address>"
TEAM_ID="<your_team_id>"                                             # eg. 2STEST4IHD   
DEVELOPMENT_TEAM="<your_development_team>"                           # eg. 2STEST4IHD
APP_SPECIFIC_PASSWORD_KEYCHAIN="<app_specific_password_keychain>" 
SIGNING_IDENTITY="<your_signing_identity>"                          # eg. Developer ID Application: The Ora (2STEST4IHD)
```

So releases are notarised Apple Developer ID builds, distributed outside the Mac App Store, which matches a GPL-3.0 licence and a self hosted update channel. A developer reproducing this needs their own Apple Developer membership and team, and the app specific password is required to publish to the appcast. This is all ordinary for a distributed macOS app, but it is a meaningful constraint for anyone hoping to run Ora without an Apple account of their own.

## The release notes describe a browser taking shape

The three most recent tags read like a changelog written for people who actually use the app. Version 0.2.14 from 2026-04-07 leads with space scoped privacy protections that keep work, personal and other spaces separate, lightweight toast notifications for unobtrusive feedback, and downloads history moved into the spatial sidebar. The spaces concept is the more interesting one: it implies a browsing model organised into separate contexts with their own privacy rules, which is a different bet from ordinary tab grouping.

Version 0.2.13 in March 2026 covers a redesigned settings screen with a sidebar, a refined password UI, updated window traffic lights and sidebar toggle icon on macOS, and one fix worth calling out because it is a good sign for anyone testing on a Mac daily: Cmd+Z was restored to use native macOS Undo. Version 0.2.12 just before it is the raw pull request list, and it is where the architecture shows through: a design system with components and a dialog system, a refactor that reorganised the app source tree, a password manager with autofill backed by keychains, and InjectionIII hot reloading for debug builds. Individual contributors appear there too, with atpugvaraa handling the macOS window chrome and enzoarpentier credited on the native undo work, so this is not a single author project.

## Tags stop in April while commits continue into September

Here is the discrepancy worth flagging before you plan around this repository. The newest release tag is v0.2.14, published 2026-04-07. The repository itself was last pushed on 2026-09-17, and it is not archived. That is roughly five and a half months of development that no tagged release accounts for, and there is no nightly channel described in the README to cover the gap.

Both facts are worth having at once rather than picking one. The commit activity says the project is alive and being worked on, and the release cadence says the last thing you can download was built in April. If you want current behaviour you are in the clone and build path, which brings back the Apple signing requirement for anything you distribute yourself. If you just want to try it, 0.2.14 is a reasonable place to start, but expect the UI to have moved since. The README's own warning that it is not ready for daily use, paired with the ROADMAP.md file in the tree, suggests the maintainer would rather you read the roadmap than assume version numbers tell you where the project is heading.

## Conclusion

Ora is worth a look if what you want from a browser is the macOS system engine with someone else's opinionated layer on top, because everything here runs on WebKit rather than a bundled Chromium. Content blocking, a spatial sidebar with downloads history and a password manager that talks to keychains are all real in tagged releases. The catch is stated plainly in the README, which says the browser is still in active development and not ready for daily use, and the release tags stop at 0.2.14 in April 2026 while the repository kept receiving commits through September. For most people that means cloning it, running the setup script and building in Xcode rather than installing a binary, and the GPL-3.0 licence matters if you ever wanted to ship it inside something else.

## FAQ

### Is Ora Browser ready to use as my main browser?

The README states that Ora is still in active development and is not ready for daily use yet. The newest release is 0.2.14 from April 2026, while the repository itself has seen commits since then.

### What browser engine does Ora use?

Ora is built on WebKit, the system engine on macOS, with SwiftUI and AppKit for the interface. It does not bundle Chromium, so it follows whatever engine Apple ships with the operating system.

### How do I build Ora from source?

Clone the repository, run ./scripts/setup.sh to install tooling and git hooks and regenerate the Xcode project, then open Ora.xcodeproj. Tests run through Product > Test or via xcodebuild.

### What licence is Ora released under?

Ora Browser is licensed under GPL-3.0, and the README notes that third-party libraries used by the project carry their own open source licences. Vendor dependencies are listed separately in THIRD_PARTY_NOTICES.md.

## Sources

- [License: GPL-3.0](https://github.com/the-ora/browser/blob/main/LICENSE)
- [Project website](https://orabrowser.com/)
- [README](https://github.com/the-ora/browser/blob/main/README.md)
- [Releases](https://github.com/the-ora/browser/releases)
- [the-ora/browser on GitHub](https://github.com/the-ora/browser)

---

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