Separate Enterprise environment
Make states that the Enterprise platform runs in a separately managed AWS environment, apart from its self-service cloud.
Source make.com/security
MakeOS Enterprise by Consultants in a Box
See the logic. Trust the solution. Scale without limits.
We implement Make Enterprise around the systems your teams already run: CRM, finance, IT, HR, data and support. Every build is scoped against the security and compliance controls Make publishes, so your security team can check each claim at its source.
GDPRSOC 2 Type IISOC 3As listed by Make at make.com/security. Consultants in a Box is a Make partner and holds none of these attestations itself.
The platform underneath
What Make Enterprise gives your security team to review
These are Make's own published statements, taken from its security page. We design around them and never add to them.
Uptime and support terms
Enterprise Plan customers get 99.5% cloud service uptime and Enterprise customer support services with defined support SLAs.
Source make.com/security
Single sign-on and roles
Sign-in with Google, Facebook or GitHub is supported, and Enterprise customers can use their own SSO implementation. Roles and teams are managed inside the organization.
Source make.com/security
Encryption in transit and at rest
Network traffic uses TLS 1.2 and 1.3 with AES-256. Data at rest uses AES-256, with AWS Key Management Service.
Source make.com/security
Private, redundant hosting
Infrastructure runs on AWS EC2 private instances in a VPC, with the cluster deployed over two zones to keep it available.
Source make.com/security
Testing and logging
Regular penetration testing by independent third parties. Log data is kept for 30 days by default, and the Enterprise Plan offers longer storage.
Source make.com/security
Offerings by system
One Enterprise rollout per system family
Pick the system your team lives in. Each offering covers the scenarios, the connections and the guardrails around them. Scope and price are set on a call.
CRM and sales systems
Salesforce, HubSpot, Zoho CRM and similar
What we build
- Lead routing, enrichment and follow-up scenarios
- Two-way sync between CRM, billing and support
- Ownership rules for every CRM connection
Controls we map to
Roles and teams control who can edit CRM scenarios. Connections to the CRM use the strongest authentication the CRM supports.
Finance and accounting
QuickBooks, Xero, Stripe, ERP and similar
What we build
- Invoice, payment and reconciliation workflows
- Approval steps before money-moving actions run
- Month-end reporting feeds
Controls we map to
Builders and approvers are kept in separate roles. The Enterprise Plan's longer log storage helps when audit questions come.
IT, identity and service desk
Freshservice, Intercom, Slack and similar
What we build
- Joiner, mover and leaver request flows
- Ticket triage and escalation scenarios
- SSO rollout for your Make organization
Controls we map to
Your own SSO implementation on the Enterprise Plan, and a role and team structure that mirrors your org chart.
HR and people operations
HRIS, payroll, recruiting and similar
What we build
- Onboarding and offboarding checklists across systems
- Candidate and employee data handoffs
- Access-removal steps tied to exit processes
Controls we map to
Scenarios that carry personal data are limited to the people who need them. GDPR adherence as stated by Make.
Data warehouse and reporting
Snowflake, BigQuery, Google Sheets and similar
What we build
- Scheduled loads and refresh scenarios
- Alerts when a feed is late or malformed
- Reporting hand-offs to the tools your teams read
Controls we map to
Where a connector offers a choice of connection security, we choose the stronger option.
Customer support and communication
Helpdesk, chat, email and messaging platforms
What we build
- Inbox triage with drafted replies
- Hand-off rules for anything sensitive
- Support-to-CRM and support-to-billing links
Controls we map to
Make's defined Enterprise support SLAs for the platform, and our own runbook for each scenario we hand over.
How a rollout runs
Four phases, in this order
Governance is settled before the first production scenario is built, so teams can start building without waiting on a security review.
Inventory the systems
List the systems each team wants connected, what data moves between them and who owns each connection. Mark anything that carries personal or financial data.
Set the guardrails
Decide teams, roles, SSO and how long you need logs. Check each against what Make's Enterprise Plan offers and write down any gap before building.
Build and test
Build the scenarios for your first system family, test them against real edge cases, and document what each one does in plain language.
Hand over and extend
Train your builders, transfer ownership and add the next system family when you are ready. Ongoing support is available month to month.
Tell us which systems you want on Make Enterprise
Book a call with Consultants in a Box. We will map your systems to an offering above and give you a written scope and price afterwards. No contract is needed to talk.
Book a call
Make and the Make logo belong to Make. Consultants in a Box is a Make partner. This page is written by us and is not published by Make or Celonis. Security and compliance statements on this page are quoted from make.com/security and may change; confirm current terms with Make before relying on them.