Price Make Enterprise before security approves Make, because audit logs, SSO, and custom roles come only with that plan. Each organization runs in a US or EU data zone, and Make keeps execution logs for 7 to 60 days depending on the plan. Make states it does not train Maia's model on customer data.
When you need this
- Security or IT reviews Make before more teams adopt it.
- Scenarios handle customer or employee data, or must keep data in the EU.
- AI steps or agents will act on company systems.
Evaluation criteria
Identity
Do people sign in through your identity provider, and is two-factor authentication enforced?
Look forEnable two-factor authentication on any plan. Enterprise adds company SSO through OAuth2 or SAML2 and 2FA enforcement. Its domain claim routes new users under your domain through SSO.
Roles and access
Can you limit who builds, runs, and changes what?
Look forUse the Teams plan so members see only their team's scenarios and data. Enterprise adds custom organization and team roles, except on private instances. Every member has a private space on every plan. Moving scenarios between organizations requires blueprint export and import, as one freelancer billing by usage found.
Audit and visibility
Can IT see who changed which scenario, connection, or key?
Look forBudget for Enterprise if IT needs audit logs. They cover scenarios, connections, webhooks, keys, data stores, SSO, and use of another person's connection, and Make keeps them 12 months. From Core, Make Grid maps scenarios and apps with their dependencies.
Data location
Is the data zone right, and which AI features leave it?
Look forChoose US1, US2, EU1, or EU2 on AWS per organization. Maia, Make AI Web Search, and Make's OpenAI models always process in the US. On EU zones, Make says Claude Sonnet 4.6 and Opus 4.6 are served from a UK Bedrock region rather than the EU. Custom connections follow provider routing unless you set the endpoint or Azure region. One builder moved a Zapier flow to Make to keep it with a non-US provider.
Retention
How long are run data and logs kept, and can sensitive payloads stay out of them?
Look forCheck log retention against your data rules. Free keeps 7 days. Core, Pro, and Teams keep 30. Enterprise keeps 60. Enable Keep data confidential to exclude run payloads from logs. Saved scenario versions last 60 days.
Local systems and Enterprise hosting
Do scenarios need systems behind your firewall?
Look forUse the Enterprise on-premise agent for local applications and databases. Enterprise runs in a separate AWS environment with a 99.5% cloud uptime commitment. Make's migration tool moves scenarios into it.
Certifications and AI training
What will procurement ask for?
Look forRequest the SOC 2 report. Make lists GDPR, SOC 2 Type II, and SOC 3, with an ISO 27001 certified security program. Make states that prompts, scenario structures, and outputs do not train Maia's model. Maia cannot see connections or keys.
Questions to ask vendors
- Which scenarios carry personal data, and should Keep data confidential be on for them?
- Do any AI features we plan to use process outside our data zone?
- Which connections belong to individual people, and what happens when they leave?
- Do we need audit logs and SSO now, which means Enterprise?
Red flags
- Assuming the Teams plan includes audit logs, SSO, or custom roles.
- Promising EU-only processing while using Maia or OpenAI models through Make's AI Provider.
- Personal connections to company systems inside shared scenarios.
- Sensitive payloads kept in execution logs with Keep data confidential off.
Products in this piece
Sources
- Official documentation
- 15
- Public source
- 4
- Make pricing
- Make: Security and compliance
- Make Enterprise
- Make Help Center: AI providers and data zones in Make
- Make Help Center: Audit logs
- Make Help Center: Teams
- Make Help Center: Custom roles
- Make Help Center: Private spaces
- Make Help Center: Two-factor authentication enforcement
- Make Help Center: Domain claim
- Make Help Center: On-premise agent
- Make Help Center: Upgrade to the Enterprise plan
- Make Help Center: Scenario settings
- Make Help Center: Introduction to Make Grid
- Make Help Center: Maia by Make system card
- Make Community: How can I bill clients based on Make usage? (Feb 16, 2025)
- Make Community: Trying to use Make with Asana instead of Zapier (Nov 11, 2025)
- FINN: No-code isn't scalable, our learnings going toward 100,000 car subscriptions (Jul 19, 2022)
- Hacker News: replacing about 15 Make scenarios that broke silently (Mar 10, 2026)