Skip to main content

Make vs Raycast AI

A feature-by-feature comparison of Make and Raycast AI across 7 capability categories.

Try Make (opens in a new tab)
Try Raycast AI (opens in a new tab)

Modalities — Tie

Modalities: Make compared with Raycast AI
FeatureMakeRaycast AI
Text Input
Yes, requires free plan. Scenario modules and AI/app steps take text and mapped fields. Directory lists Freemium.Yes, requires pro plan. AI chat in the Raycast launcher accepts text prompts.
Image Upload / Vision
Unknown. Homepage timed out this round. File modules likely exist; vision was not confirmed.Partial. Screen capture and file context. General image upload was not separately documented.
Image Generation
No. You can call an image API as a module. Make itself is not an image model.Unknown. Whether image gen models are in the 32+ model list was not checked.
Voice Mode
No. Not a conversational voice product.Unknown. Voice input was not confirmed on the AI page.
Video Understanding
No. Not a video-analysis product.No. Not a video analysis product.
Video Generation
No. Automation platform; it does not generate video itself.No. Not a video generation product.
File Upload (PDF, DOCX)
Unknown. Homepage timed out. File/HTTP modules are typical; not confirmed this round.Yes, requires pro plan. PDF, CSV, and file context in AI chat.
Code Execution
Unknown. A custom-code module was not confirmed this round.Unknown. Whether AI runs code locally was not confirmed.
Audio Input
No. Not a speech product.Unknown. Speech input was not checked.
Canvas / Artifact Editor
Yes, requires free plan. Visual scenario canvas.Unknown. Overlapping columns disagreed (no vs partial); left unverified rather than copying a no.
Screen Sharing / Computer Use
No. No computer-use takeover.Partial. Screen context for AI queries. Not live screen sharing to others.

Memory & Context — Make Wins

Memory & Context: Make compared with Raycast AI
FeatureMakeRaycast AI
Persistent Memory
Partial. Scenarios and data stores persist. That is automation state, not chat memory.Partial. Chat history in Raycast. No cross-device cloud memory advertised.
Large Context Window
No. Operations quota, not an LLM token window.Unknown. Depends on the selected model (32+ providers).
Custom Instructions
Yes, requires free plan. Scenario logic, filters, and routers are the instructions.Partial. Extensions and prompts customize behavior. No global system profile documented.
Conversation History
Yes, requires free plan. Execution history of scenarios.Yes, requires pro plan. AI chat history persists in Raycast.

Integrations — Tie

Integrations: Make compared with Raycast AI
FeatureMakeRaycast AI
Web Search / Browsing
Unknown. HTTP modules can call search APIs. Not a built-in cited search.Yes, requires pro plan. Web search with inline references in AI chat.
Plugins / Extensions
Yes, requires free plan. Thousands of app modules (directory heritage). Count was not re-fetched.Yes, requires pro plan. Raycast extensions and AI Extensions ecosystem.
API Access
Yes, requires plus plan. Webhooks and an API to manage scenarios are the usual Make surface. Details not re-fetched.No. Consumer launcher, not a public inference API.
Zapier Integration
No. Make is a Zapier alternative, not a native Zapier app.Unknown. Zapier was not checked.
Custom GPTs / Bots
No. You build scenarios, not a GPT store.Partial. Custom AI Extensions act like specialized bots.
Real-time Collaboration
Unknown. Team editing was not confirmed this round.No. Single-user launcher.
Live Social Data Integration
No. You can connect social apps. That is not a live sentiment firehose.No. No social firehose.
Live Citation Mapping
No. Not a cited-search product.Partial. Web search shows inline reference links.

Developer — Raycast AI Wins

Developer: Make compared with Raycast AI
FeatureMakeRaycast AI
Function Calling
Partial. Modules are tools. An LLM function-calling product was not confirmed.Yes, requires pro plan. AI Extensions invoke app actions and tools.
Streaming Responses
No. Scenario runs are jobs, not token streams.Yes, requires pro plan. AI responses stream in the launcher.
Fine-Tuning
No. Make does not train foundation weights.No. Routes to third-party models; does not fine-tune.
Embeddings API
No. Not an embeddings API.No. Not an embeddings product.
Structured Output (JSON)
Yes, requires free plan. Mapped JSON between modules.Unknown. JSON mode depends on the selected model.
Reasoning / Thinking Mode
No. Not an LLM reasoning-mode product.Unknown. Overlapping columns disagreed (yes vs partial); left unverified rather than copying a no.
Local Execution
No. Cloud SaaS, unlike self-hosted n8n.Yes, requires pro plan. Ollama local models run on-device.
Open Weights
No. Closed cloud product.Partial. Ollama routes to open-weight local models.
Multi-Agent Orchestration
Unknown. AI/agent modules were not confirmed on a live homepage this round.No. Single chat session, not multi-agent.

Platforms — Tie

Platforms: Make compared with Raycast AI
FeatureMakeRaycast AI
Web App
Yes, requires free plan. make.com visual editor (cloud).No. Native macOS app, not a web chat.
iOS App
Unknown. Not confirmed this round.No. No iOS app for Raycast AI.
Android App
Unknown. Not confirmed this round.No. No Android app.
Desktop App
No. Cloud editor, not a native desktop app.Yes, requires pro plan. Raycast is a macOS desktop launcher with built-in AI.
Chrome Extension
Unknown. Not confirmed this round.No. No Chrome extension.

Privacy — Raycast AI Wins

Privacy: Make compared with Raycast AI
FeatureMakeRaycast AI
GDPR Compliant
Unknown. Needs a current DPA read. Homepage timed out.Unknown. Privacy policy was not re-read.
Opt Out of Data Training
Unknown. Not checked.Yes, requires pro plan. Raycast states it does not train on your data.
Enterprise Privacy Mode
Unknown. Enterprise plans exist in market; not confirmed this round.Partial. Team plans exist. Enterprise DPA not read.

Workspaces — Make Wins

Workspaces: Make compared with Raycast AI
FeatureMakeRaycast AI
Projects / Folders
Yes, requires free plan. Scenarios persist in the cloud.Partial. Extensions and snippets organize workflows, not chat project folders.