How is Make.com (formerly Integromat) built — and could you clone it?
Last analyzed 10/13/2026 · full report
https://make.com
You can clone the Webflow landing page in an afternoon; you cannot clone a decade-old, Celonis-funded workflow engine with 3,000 connectors in any number of prompts.
The landing page is a weekend Webflow clone; the moat is 350 employees, 13 years of connector engineering, 350,000+ customers, and a $107M Celonis-backed war chest.
Not worth cloning as a real business — this is a $107M-acquired, Celonis-backed category leader competing against Zapier/n8n/Workato with a decade of connector-building; the marketing page is trivial to copy but carries zero value without the automation backend, which is a multi-year, multi-million-dollar engineering effort.
iPaaS/workflow automation is a large, fast-growing category; Make reports over 350,000 organizations in 200+ countries and roughly more than 100,000 paying customers, roughly €100M ARR, and ~350 employees as a Celonis business unit.
$0–20 for a static landing clone; $5k-50k+/mo to run even a modest real automation engine (compute for scenario execution, connector maintenance, support, infra) at any scale
A landing-page clone earns nothing without the underlying automation engine; the real business monetizes via credit-based subscription tiers ($9-$34+/mo) plus enterprise deals, a model that only works once thousands of connectors and reliable execution infrastructure exist.
Zapier, n8n, Workato, Tray.io, Latenode, Pipedream
Freemium credit-based subscription — free tier ~1,000 ops/month, paid tiers (Core/Pro/Teams) scaling by operations/credits, plus custom Enterprise pricing.
Large and growing; serves 350,000+ organizations globally as a leading Zapier alternative, part of ~$13B Celonis.
- Trademark (Make/Celonis brand)
- Competing directly with well-funded incumbents (Zapier, n8n, Workato)
- Replicating 3,000+ third-party OAuth integrations raises per-vendor API ToS/partnership issues
Next.js + Webflow-style CMS or just static Tailwind for landing; for any real backend attempt: Node/Temporal for workflow execution, Postgres (Supabase) for state, Clerk/Auth0 for auth, Stripe for credit billing, and a connector SDK (OAuth2 per app) for integrations
Webflow template (e.g. 'Flowninja'-style marketing kit) for the landing page; Activepieces or n8n (open-source) as a starter if attempting the actual automation engine instead of building from scratch
- 1.Fork a Webflow/Next.js marketing template and replicate hero, product, pricing, and blog sections
- 2.Wire up OneTrust-style cookie consent and a CRM/marketing form backend (HubSpot/Marketo) for lead capture
- 3.If pursuing the real product, start from an OSS workflow engine (n8n/Activepieces) instead of building execution from scratch
- 4.Add Postgres-backed scenario storage, Temporal or BullMQ for scheduled/triggered execution
- 5.Build a credit-metering billing layer on Stripe tied to operations consumed
- 6.Implement OAuth connector framework and begin building individual app integrations one by one
- 7.Add AI agent/MCP layer only after core execution and connectors are stable
▸Technical evidencefacade · hidden · 6 signalsShowHide
A prompt can rebuild the Webflow-style marketing site: hero, product pages, pricing table, blog/"what's new" feed and animated sections with Webflow-grade polish.
Behind the marketing site sits a full visual workflow-automation engine: a scenario/flow execution runtime, a scheduler, 3,000+ app connectors/OAuth integrations, a credit-metering billing system, multi-tenant org/auth, webhook listeners, an AI agent/MCP orchestration layer, and enterprise security/compliance infrastructure built over 13+ years by a 350-person team now backed by Celonis.
You could build it — but that moat means you can't win. Find a better bet.
Analyze a different idea →