Is Raycast Open Source? 2026 Transparency Guide

Published April 23, 2026 • 7 min read

If you've looked at Raycast and wondered whether you're installing open-source software or a closed binary, the answer matters. It affects trust, auditability, long-term risk, and whether you can fork the project if the company ever changes direction. The short version is that Raycast sits in a hybrid zone that a lot of modern developer tools occupy, and the distinction is worth understanding before you commit a daily workflow to it.

This guide lays out exactly what's open, what's closed, why, and what you should do if full open-source licensing is a hard requirement for you.

Short Answer: Partially

Raycast is best described as a proprietary application with an open-source extensions ecosystem. That's a common shape for modern tools — VS Code uses a similar model, where the core editor is proprietary (the open MIT "Code - OSS" build is a separate thing) and extensions live on a public marketplace.

For day-to-day users this distinction rarely matters. For teams running security reviews, building on top of the API, or choosing tools under an open-source-only policy, it's the first thing to check. Raycast is transparent about the split, and the company's extensions repository is one of the more active public codebases in the macOS productivity category.

What IS Open Source

Three specific pieces of the Raycast ecosystem are fully open source and publicly auditable:

• The extensions repository (raycast/extensions): Every extension you install from the Raycast Store, including first-party extensions built by Raycast's own team, lives in a public GitHub monorepo. You can read the source, fork it, and submit pull requests.
• The extension API template and CLI: The TypeScript API definitions, the ray CLI for scaffolding and publishing, and the build tooling are all open. Developers have full visibility into the surface they're coding against.
• Documentation: The developer docs site and extension guides are public and community-contributable. Bugs in documentation can be fixed through standard pull requests.

This matters because extensions are where most of Raycast's day-to-day value lives for power users. A GitHub, Linear, Notion, Jira, or 1Password integration you rely on is fully auditable. If you want to understand what an extension does before installing it, the source is one click away. For a curated list of the most-used extensions, see our roundup of the best Raycast extensions.

What's NOT Open Source

The parts of Raycast that remain closed source are the ones that define it as a product rather than a platform:

• The core Raycast app binary: The launcher itself — the window that appears when you hit your hotkey, the root search UI, the window management engine, the extension runtime — is proprietary. You cannot read its source or rebuild it from scratch.
• Raycast Pro features: The AI commands layer, AI Presets, Theme Studio backend, unlimited Notes storage, and Pro-specific window management commands are closed.
• Cloud sync infrastructure: The sync service that ships your extensions, snippets, quicklinks, and hotkeys between Macs via iCloud is a proprietary backend. You can't self-host it.
• The AI routing layer: The system that brokers requests to GPT-4o, Claude 3.7 Sonnet, Gemini, Perplexity, Mistral, DeepSeek, and others is closed source. You see the models you can pick; you don't see the orchestration code.

If your team has a policy that every piece of software in the stack must be open source — including the binary — Raycast will not pass that bar. If your policy is "extensions and integrations must be auditable," it does.

Why the Core Is Closed Source

Raycast is a venture-backed company with full-time engineers, designers, and support staff. The monetization model is Raycast Pro and the Teams plan — both subscription products layered on top of a generous free tier. Keeping the core app proprietary is what allows the business to fund development at the pace the community has come to expect.

The open-extensions model is the trade-off. Users get an auditable, extensible ecosystem where the code they install into their launcher is public. The company retains control over the core binary that users subscribe to. This is the same arrangement GitHub, Figma, Notion, Linear, and most modern developer tools use. It's not ideal if you're philosophically committed to 100% free software, but it's a pragmatic middle ground most teams accept.

Fully Open-Source Alternatives

If open source is a hard requirement, none of the truly comparable options run natively on macOS — that's the honest read. The closest equivalents are Linux-first:

• Ulauncher (Linux, GPLv3): Python-based launcher for GNOME and other desktops. Extensible via a Python extension API, actively maintained, and the closest-in-spirit open-source equivalent of Raycast on Linux.
• Albert (Linux, MIT): C++ launcher modeled on Alfred. Fast, keyboard-driven, and fully MIT-licensed. Plugin system supports Python and native modules.
• Flow Launcher (Windows, MIT): The Windows counterpart. Broad plugin ecosystem, active community, and the most Raycast-like experience available on Windows.
• Rofi (Linux/X11, MIT): Minimalist window switcher and launcher. Not as feature-rich as Raycast but extremely lightweight and scriptable.

For a broader comparison of Raycast substitutes across platforms, see our guide to Raycast alternatives. Linux users specifically should also read our dedicated breakdown of the best Raycast alternative on Linux, which goes deeper on Ulauncher, Albert, and how they compare feature-by-feature.

Contributing to Raycast Extensions

If the open-extensions ecosystem is what you want to participate in, the contribution flow is straightforward:

1. Fork raycast/extensions. Clone the repo locally. The monorepo contains every public extension, each in its own directory with a package.json and TypeScript source.
2. Build locally with the ray CLI. Run npm install inside an extension folder, then ray develop. Your extension hot-reloads inside Raycast so you can iterate immediately.
3. Submit a pull request. Raycast's review team checks new extensions and changes against contribution guidelines. Approved PRs ship to every Raycast user through the in-app Store within the next release cycle.

You can build entirely new extensions, improve existing ones, or fix shared utilities. Either way, your work ships publicly under an open license — that's the open-source surface Raycast maintains.

License Details

The raycast/extensions repository is published under the MIT license. You can read the full terms in the repository's LICENSE file on GitHub. In practical terms, MIT allows:

• Free commercial and non-commercial use
• Modification and redistribution
• Incorporation into larger works, including closed-source ones
• Sublicensing

The only requirement is that the MIT copyright notice ships with any distribution. Individual extensions may set their own permissive license, but the repo-level default is MIT. The core Raycast macOS app is covered by a separate end-user license agreement available on the Raycast website.

FAQ

Is Raycast open source in 2026?

Partially. Extensions are MIT-licensed on GitHub; the core app is proprietary.

What license covers the Raycast extensions repo?

MIT. Commercial use, modification, and redistribution are all permitted with attribution.

Why isn't the Raycast app itself open source?

Raycast monetizes through the Pro subscription; keeping the launcher proprietary funds continued development and the full-time team behind it.

What are the best open-source alternatives to Raycast?

On Linux, Ulauncher (GPLv3) and Albert (MIT). On Windows, Flow Launcher (MIT). Rofi is a lightweight X11 option.

Can I contribute code to Raycast?

Yes, via the public raycast/extensions repo. You can add new extensions or improve existing ones. The core app is not open to external contributions.

Is the Raycast extension API open?

Yes — the TypeScript API, CLI tooling, and documentation are all public. Only the runtime that executes extensions inside the core app is closed.

The bottom line

Raycast's hybrid model gives you an auditable, community-driven extensions ecosystem on top of a polished, well-funded proprietary core. It's not a fit if you require every piece of software you run to be open source, but it's a common and defensible middle ground. For most developers, the key question isn't "is it open source?" — it's "are the parts I extend and depend on auditable?" The answer to that, for Raycast's extensions layer, is yes.

If you've decided the trade-off works for you and you want to try the full Pro feature set, the lowest-risk path is the 80% discount and free 14-day trial. Claim the discounted trial here, or head back to the main discount page for the current offer summary.