Raycast for Teams in 2026: What It Includes, Costs and Limits

Raycast for Teams lets a company share Quicklinks, Snippets, AI Commands and private extensions inside the Raycast launcher. Raycast's pricing page puts Teams Free at $0, with caps of 30 shared Quicklinks, 30 shared Snippets and 5 shared Commands. Teams Pro costs $15 per person a month, or $144 a year. SAML single sign-on requires Enterprise.

The question usually arrives from below: a few people on your team already use Raycast on their Macs, love it, and ask whether the company should pay. My short answer is to start free, because the free plan doesn't expire and shows you quickly whether anyone will maintain a shared library. Below you'll find what each plan includes, a seat-cost example, the Mac requirements that can stall a rollout, and how I'd decide.

What is Raycast for Teams?

Raycast for Teams is the organization layer of Raycast, the keyboard launcher for Mac. Each person still opens Raycast with their own hotkey, but an organization's links, text and tools appear beside their personal ones. It isn't a separate app, and it isn't a chat or calendar product like Microsoft Teams, though the names are easy to mix up. If you're choosing a place for your team to talk, Microsoft Teams vs. Slack is the comparison you want.

Raycast's shared features guide lists what an organization can share today:

• Quicklinks: a keyword that opens a dashboard, doc or internal tool.
• Snippets: text that expands from a keyword, such as a support reply or a code review format.
• AI Commands: saved prompts, such as summarizing a thread or drafting a reply.
• Agents: shared agents that keep the same instructions, model and tools each time.
• Dictation Styles: shared formats for email, messages or meeting notes.
• Private extensions: tools your team builds, installed from your organization's own store and never listed in the public Raycast Store.

Skills are the exception. The same guide says sharing them across an organization isn't available yet, so they stay personal. It also notes that some Teams features are available in Raycast for Mac v2 and Windows with full support still planned, while Raycast v1 and iOS are unchanged. Check the feature you're buying for against the version your Macs will actually run.

How much does Raycast for Teams cost?

Raycast for Teams costs $0 on Teams Free and $15, $25 or $65 per person a month on the paid plans, with lower yearly prices of $144, $240 and $624. Raycast's billing guide says there's no minimum or maximum number of seats, so you can add people when you need them. Enterprise has custom pricing, is billed annually and isn't sold on the website.

Raycast's own pages name the middle plan two ways, Plus on the pricing page and Pro+ in the billing guide. They're the same $25 tier. To show what the prices come to, I priced a 12-person team, which is my usual test for any per-seat tool because it's big enough for the bill to need a line in somebody's budget.

Credits are the part to read twice. The billing guide says credits are per member and aren't pooled, so on Teams Pro the person who lives in AI chat can't borrow from the colleague who never opens it. Unused monthly credits roll over for one extra billing cycle and expire 60 days after they were granted, according to the pricing page FAQ. Models burn credits at different rates, and Raycast's pricing table lists top-tier models under Plus and Max only.

Plan changes are simple enough. Upgrades apply immediately and downgrades wait for the next renewal date, per the billing guide. Anyone with billing permission finds Manage Team Plan under Settings → Account.

Is Teams Free enough for a small team?

Teams Free is enough for a small team whose goal is shared links and text. Raycast states that it doesn't expire and isn't a trial, it allows unlimited members, and it can be used inside a company. The limits are 30 shared Quicklinks, 30 shared Snippets and 5 shared Commands, with no AI. Since AI Commands are saved prompts, try one on the free plan before you count on those five.

Thirty goes further than it sounds. The week a new hire joined my team, I pasted the same handful of links into Slack over and over: the roadmap, the project board, the brand folder, the expenses form. A dozen shared Quicklinks would have ended that. Most teams I've worked with have a short list of things everyone looks for and a long tail nobody can remember, and that short list fits comfortably under the free caps.

When is Teams Pro worth paying for?

Teams Pro is worth paying for once a team outgrows the shared-item caps, depends on private extensions or wants Raycast AI for everyone. On the pricing page it removes the limits on shared Commands, Quicklinks and Snippets, adds the Private Store, and gives each person Pro features such as 500 AI credits a month, Cloud Sync and unlimited Clipboard History.

The strongest case is private extensions, if you have someone to build them. Raycast's developer docs say extensions are built with TypeScript, React and Node, so this means engineering time. The Teams page gives examples such as brand asset access, feedback logging, time-off booking and an employee index. A marketing or sales team with no developer on hand will get far less from this line of the price list.

Weigh AI separately. If people already have an AI assistant through work, Raycast credits may be a second bill for much the same job, and that overlap is the first thing I'd bring up with whoever signs the invoice. The argument for paying is convenience: AI sits in the same window as everything else, and shared AI Commands give everyone the same prompt.

When do you need Raycast for Enterprise?

You need Raycast for Enterprise when your company requires SAML single sign-on (people log in through your company's identity system), SCIM provisioning (accounts are created and removed from that system) or central control over AI and data. The Enterprise page puts all of these on that plan, which makes the jump from Teams Pro more about IT policy than about features people will notice day to day.

• Identity: SAML SSO, SCIM provisioning, domain enforcement and MDM sign-in enforcement.
• Data controls: company-wide switches for Cloud Sync and Dictation, governed Clipboard History settings, enforced two-factor authentication and an IP allow-list.
• AI controls: a company-wide AI toggle, a provider allow-list, your own API keys, your own AI gateway and organization-managed MCP servers.
• Extensions: an allow-list and automated vulnerability scanning.

The catch for security-minded buyers sits lower down the price list. Raycast's FAQ says each person can turn AI off in Settings, but the company-wide switch is an Enterprise control. So on Teams Pro, "we've disabled AI" means "we've asked everyone to." Clipboard History governance and the extensions allow-list also sit on Enterprise, so below that plan you can't centrally limit either one.

When I'm asked to approve a tool that keeps clipboard history, I bring the security lead in before the pilot, because passwords and customer details pass through that clipboard. Raycast's material gives them a starting point: the Enterprise page cites yearly third-party penetration testing and a SOC 2 Type II report, and its AI privacy guide says models don't train on your data. That guide also says Raycast-provided models keep no prompts or outputs after a request, with 30-day exceptions it lists for a few specific models.

What Macs does Raycast for Teams need?

The current Raycast for Mac, version 2, needs macOS Tahoe and Apple silicon. Raycast's v2 page says Macs on Sequoia or earlier must upgrade macOS first, and describes v2 as a major update with "occasional rough edges." Installing it replaces v1. Count your older Macs before you commit, since those colleagues may end up on a different version from everyone else. I couldn't establish exactly what shared features v1 users get, so ask Raycast support whether they can see shared Quicklinks and Snippets.

1. On each Mac, choose Apple menu → About This Mac and note the chip and the macOS version.
2. List anyone on an Intel Mac, or anyone whose IT policy holds them on Sequoia or earlier.
3. Have people who built custom extensions update to the latest v1 before moving. Raycast's page asks for at least v1.104.16 so those extensions import correctly.
4. If IT manages your fleet, read the MDM deployment guide. It covers a signed package for Jamf, Iru and Microsoft Intune, though it doesn't say whether Teams plans can use it.

How to set up Raycast for Teams on a Mac

To set up Raycast for Teams, create an organization, send the invite link, then add your first shared items. None of this needs a paid plan. These steps follow Raycast's account guide, Quicklinks guide and Snippets guide.

1. Sign in on the Raycast website, open your account settings and select Create an Organization. Settings in the app offers the same option.
2. Enter the organization's name and handle. The handle appears in your store links, so keep it short.
3. Open Raycast, run Manage Organization to check the details, then run Copy Organization Invite Link and send the link to your team.
4. Run Create Quicklink, pick your organization under Organization, fill in Link and Name, then choose Save Quicklink (Command-Return).
5. Run Create Snippet, enter the Snippet Text and Name, add a Keyword, and pick your organization under Organization.
6. Ask a teammate to find both items through Search Quicklinks and Search Snippets, where the shared ones sit beside personal ones.

Publishing a private extension takes more setup. Raycast's guide has you put the organization handle in the owner field of the extension's package.json file, then run npm run publish. Only members of that organization can see the result.

One setting deserves a decision on day one, and it's who gets to edit. Raycast's roles guide has three roles (Manager, Billing and Member), and members of any role can create, edit and delete shared features. I once watched a support reply go out quoting an old refund policy because several people kept their own version of the wording, and a shared library only cures that if someone looks after it. Give each set of shared Snippets a named owner, and tell the team to ask that person before changing a customer-facing line.

Does Raycast for Teams help with calendars and meetings?

Raycast for Teams adds little to calendars, because Raycast's calendar features are personal. The Calendar guide describes My Schedule, built on the macOS Calendar, so accounts already in Apple's Calendar app (Google, iCloud, Microsoft Exchange) appear automatically. It says nothing about shared team calendars. Each person's Raycast shows their own schedule.

Those personal features are still handy on a heavy meeting day. Your next event sits at the top of Raycast's search, and pressing Return opens the call, in the Zoom or Microsoft Teams desktop app if you have it. Inside My Schedule, Shift-Command-B blocks time and Control-Option-A copies your availability. Grant access first under System Settings → Privacy & Security → Calendars. If your events are split across services, how Google Calendar and Apple Calendar work together is worth sorting out, since Raycast only sees what Apple's app sees.

Where the team layer does touch meetings is shared text. Before a recurring client call I want everyone starting from the same notes skeleton, because notes that share a shape are far easier to skim later. Raycast's Snippets support placeholders such as {date} and {cursor}, so a shared template can fill in the day and drop your cursor in the right place:

Meeting notes, {date}
Attendees:
Decision needed: {cursor}

What we decided:
Who does what, by when:
Next meeting:

What are the alternatives to Raycast for Teams?

The right alternative depends on which part of Raycast for Teams you actually wanted. If it's shared text, a dedicated snippet tool such as TextExpander offers Google sign-in at a listed price, with other providers and SCIM on its Enterprise plan. If it's a launcher, you may not need a team plan at all.

For email specifically, you may not need any of this. Apple Mail templates on a Mac covers the built-in routes, including text replacements.

Should your team adopt Raycast for Teams?

Your team should adopt Raycast for Teams if several people already use a launcher and someone will own the shared library. Rolling out a launcher to people who don't reach for the keyboard rarely sticks, however good the tool is. Whenever I've brought a new tool into a team, I've started with its most eager users and let the rest ask for it. For Raycast, that looks like this:

1. Check the Macs first, using the list above, so you know who can run v2.
2. Create a Teams Free organization and invite the people already using Raycast.
3. Add the links people ask for most, plus the replies that must stay word-for-word consistent. Stop there.
4. Name an owner for those items and agree who may change customer-facing text.
5. After a month, ask what got used. Delete what didn't.
6. Pay for Teams Pro when you hit a cap, need private extensions or can name who needs AI. Go to Enterprise when your security review requires SSO or central controls.

Skip it for now if your people work mostly on a phone or in the browser, if your IT policy needs SSO but the Enterprise quote doesn't fit the budget, or if nobody can name three links everyone looks for each week. That last one tells you the problem isn't big enough yet.