Viktor vs Make.com (2026)

Viktor

by Zeta Labs

Make.com

by Celonis (Make)

Pros

• ✓Executes tasks end-to-end in a persistent cloud environment: Viktor queries Salesforce, Stripe, Google Ads, and GitHub in one run and delivers a finished PDF or dashboard, not text to copy-paste
• ✓Lives natively in Slack: teams interact with Viktor like any colleague via @mention, with no separate interface or workflow to adopt, and scheduled tasks deliver outputs autonomously without human prompting
• ✓Backed by the Slack co-founders and $75M in funding as of May 2026: Stewart Butterfield and Cal Henderson wrote personal checks into an AI coworker that runs inside the product they built

Limitations

• ⚠Early-stage enterprise security features: SOC 2 Type 2 and ISO 27001 are in progress but not yet certified, creating a procurement barrier for enterprise teams with strict security requirements
• ⚠Credit-based pricing creates uncertainty for heavy users: teams running many scheduled tasks or complex multi-tool queries need to monitor credit consumption carefully, with real-world spend ranging from $150 to $400 per month above the $50 headline rate
• ⚠Slack only for now: Microsoft Teams support is on the roadmap but not yet live, Slack Marketplace approval is pending requiring manual OAuth installation, and no standalone web interface exists for teams not on Slack

Pros

• ✓Visual scenario builder handles complex branching, iteration, and data transformation that Zapier's linear editor cannot match
• ✓Credit-based pricing is significantly more cost-effective than Zapier at high volume. Same workflows cost substantially less per month at equivalent automation volume
• ✓Connects 3,000+ apps with detailed control over data mapping and error handling at each step, plus a native MCP server for direct AI client integration

Limitations

• ⚠Steeper learning curve than Zapier: building first scenarios takes meaningful time investment for non-technical users unfamiliar with visual workflow logic
• ⚠Smaller app library than Zapier at 3,000+ vs 8,000+: some niche tools lack native Make connectors and require custom HTTP module workarounds
• ⚠No self-hosting option: data passes through Make infrastructure, limiting use for strict compliance environments that require on-premise data processing