Make.com vs Oz (2026)

Make.com

by Celonis (Make)

Oz

by Anyreach

Pros

• ✓Visual scenario builder handles complex branching, iteration, parallel execution, and data transformation on one canvas. Scenario Inputs and Outputs enable structured data passing between chained workflows.
• ✓Credit-based pricing bills per module action rather than per task, and the price per scenario drops as credit tiers scale. On Pro and above, annual billing lets credits pool across 12 months rather than expiring each month. File size limits rise from 5 MB on Free to 1 GB on Enterprise.
• ✓Connects 3,000+ apps with detailed control over data mapping and error handling at each step. Native MCP server and client app, Make AI Agents, Library of Agents, AI Content Extractor, and AI Web Search embed intelligence at any automation step.

Limitations

• ⚠API rate limits and log retention rise by tier: Core allows 60 API calls per minute and keeps execution logs for 30 days, Pro 120 and Teams 240 calls per minute, and Enterprise 1,000 calls per minute with 60-day logs.
• ⚠The native library covers 3,000+ apps, and tools without a native connector need the HTTP module or the Custom Apps builder.
• ⚠No self-hosting option: data passes through Make's AWS infrastructure in EU or North America, limiting use for strict compliance environments that require on-premise data processing outside the Enterprise on-prem agent.
• ⚠Running out of credits pauses automations on Free through Teams: scenarios stop until credits are added, with vendor notifications at 75 and 90 percent of the allowance. Credits overage protection is an Enterprise feature.

Pros

• ✓Oz delivers finished work rather than chat replies: ask it in plain language from Slack, Teams, Gmail, Outlook, a call, or the web, and it returns research briefs, slide decks, spreadsheets, and pipeline updates across your connected tools in a single run. Pricing is outcome-metered rather than token-based, so a credit maps to a unit of work done and costs stay legible.
• ✓Human control is built into every consequential action: reads run silently, while every send, payment, merge, or delete posts a one-tap Approve or Reject card. Teams can set which lower-risk actions auto-approve, which makes Oz a strong fit for security-conscious teams that want autonomy without handing over unattended write access.
• ✓Unusually deep integration and security posture for an early-stage product. It offers 3,000+ integrations with named bidirectional connectors like Salesforce, HubSpot, Stripe, GitHub, and Notion, plus an API-first design and a first-party MCP server that external clients such as Claude or Cursor can query. It is backed by an independently audited SOC 2 Type II report, HIPAA, and AIUC-1, and customer content is never used to train foundation models.

Limitations

• ⚠Credit-metered pricing means the $33 Solo seat is a floor, not a ceiling: the 800 included credits are a soft budget and heavy users pay per-credit overage on top of the seat fee.
• ⚠No independent track record yet: Oz is an early-access product from a 2024 company with no third-party reviews on G2, Trustpilot, or Product Hunt, so buyers cannot yet triangulate quality.
• ⚠Several controls are gated or pending: shared memory, SSO, and pipeline access require higher tiers, and GDPR, ISO 27001, and PCI DSS are still in progress on the trust center, not certified.