Project and task management decision
Raycast Pro
A capable developer can realistically replace Raycast's core launcher, extension host, and BYO-API AI chat in a multi-week project using existing open-source launchers as references; you'll lose the curated store, enterprise/cloud features, and Raycast's polish unless you invest more time.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
Code Raycast Pro publishes itself
Not a way out of the subscription — these are the vendor’s own repositories. Worth a look for how they build, and for anything you would have to integrate with.
- raycast/extensions★7,665 GitHub starsMITEverything you need to extend Raycast.↗
- raycast/script-commands★6,784 GitHub starsMITScript Commands let you tailor Raycast to your needs. Think of them as little productivity boosts throughout your day.↗
- raycast/ray-so★2,346 GitHub starsMITCreate code snippets, browse AI prompts, create extension icons and more.↗
What a replacement has to do
- Provide a keyboard-triggered launcher that lists apps/commands, runs small extensions, and offers an AI chat pane backed by a hosted LLM provider.
What it still won’t have
- Raycast Store (curated marketplace and thousands of extensions)
- Polished native UI and cross-platform packaging (macOS + Windows)
- Organization features (SAML/SCIM, admin controls) and cloud sync
- Advanced AI provider catalog and built-in advanced model add-on
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 6 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a macOS-native keyboard-first launcher using Swift (SwiftUI/AppKit) for the frontend and a Node/TypeScript extension runner for third-party extensions. In scope: global hotkey and floating fuzzy-search launcher UI, run local commands/scripts with captured stdout/stderr, a minimal extension API (JS/TS) that can register commands and return results, an AI chat pane that sends messages to an external LLM API (configurable API key), and a simple local storage for message history and installed extensions. Out of scope: multi-user enterprise admin, SSO/SAML, cloud-sync, curated extension store UI. Require: robust error handling, rate-limiting/timeouts for LLM calls, unit and integration tests for launcher search, command execution, extension API, and AI chat integration, and a README with setup and developer extension guide.
How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 5 cited sources+3
- Price verified on pricing page+3
- Evidence score89
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.
How scoring works →Cited sources · 5
Every page the run actually retrieved.
- official productRaycast - Your shortcut to everything
- official pricingRaycast Pricing: Free Forever or Pro with AI for $8/month
- official docsAI that works with your OS - Raycast AI
- open sourceBlinkLauncher (candidate prior art)
- open sourcePeppy (candidate prior art)
Integrity checks
What held up, and what did not.
