A Make alternative you own

Visual workflow automation on n8n, running next to your systems, with credentials under your key and no metered usage.

Starter from CHF 449EUR 479USD 559 a month for one app in Pilae Cloud; Business from CHF 1,590EUR 1,690USD 1,990 for up to three on your own servers.

Replace MakeStep-by-step guide

FromMakeCelonis

  1. Inventory
  2. Parallel run
  3. Cutover
To

n8n, operated by Pilae

The step-by-step guide

Why teams leave Make

Credentials to everything

A scenario holds the keys to your CRM, ERP and mailbox. With n8n, they sit in your own database, encrypted with a key you hold.

No metered usage

Most module runs draw credits from a Make plan. On your own machines, a scenario that runs every minute costs the same as one that runs once a day.

Internal systems stay internal

n8n runs inside your private network, so it reaches the ERP, the database and the file share directly, without publishing them to the internet.

Make vs n8n operated by Pilae

Checked against make.com.

What is being comparedMakePilae
Where scenarios runIn the Make cloud, with EU and US hosting regions.On your premises or on dedicated machines in any of 10+ Pilae Cloud regions, six of them in Switzerland and the EU.
Building workflowsA visual canvas with routers, iterators, aggregators and error handlers.A visual canvas in n8n with branches, loops, sub-workflows and error workflows.
IntegrationsA large library of ready-made app modules, plus HTTP and webhooks.Hundreds of n8n nodes, any HTTP API, and JavaScript or Python for the step that does not fit.
Reaching internal systemsConnects to apps and APIs reachable from the Make cloud, and on the Enterprise plan to systems behind an on-premises agent installed in your network.Runs inside your private network, next to the systems it automates.
CredentialsStored and encrypted by Make.Stored in your Postgres, encrypted with a key you hold and back up separately.
Pricing modelMonthly or annual plans metered in credits, most module runs costing one credit each.A monthly price per app, published for Starter and Business. No charge per operation or per execution.
OperationFully run by Make as a SaaS product.Queue mode, verified backups, planned upgrades by the Pilae Agent, 60-second probes and alerts that reach Pilae engineers around the clock.

Self-hosted visual automation

Make has one of the most capable visual builders on the market, and many teams outgrow Zapier into it. It also means every scenario runs outside your network, every run is metered, and the credentials to your systems sit on someone else’s servers.

n8n is the closest self-hosted equivalent: a visual canvas with branches, loops, error handling and code steps. Pilae deploys it inside your network or on dedicated machines in any of 10+ Pilae Cloud regions, six of them in Switzerland and the EU, on your private network. Credentials are held as described on our security page.

Automation that holds up in production

A self-hosted n8n needs work to be reliable: Postgres instead of SQLite, queue mode so one slow scenario cannot stall the rest, an encryption key kept apart from the database, and restores that are tested, every month on the Enterprise plan. We set all of it up during onboarding. The Pilae Agent then plans each upgrade, tests it against a copy of your workflows and applies it in your window after your approval.

Coming from Zapier instead? See the Zapier alternative. Pricing is per app, published for Starter and Business, with no per-operation component. Start with an inventory of what you run on Make today.

Moving from Make to n8n

  1. Count what actually runs

    The run history your Make plan keeps, and the schedules of the monthly jobs, not the list in the organisation. Scenarios that are switched off or never fire are left behind.

  2. Rebuild the live scenarios

    Make blueprints do not import into n8n, so each live scenario is rebuilt. The same inputs are sent to both systems and the outputs compared.

  3. Re-authorise the connections

    Every connected service gets new credentials against the new host, encrypted with a key held in your vault. Webhook URLs are repointed at the sender.

  4. Run in parallel, then stop paying

    Both systems stay live until a full cycle has run without error, including the monthly jobs. Then the subscription ends.

Migration guide

How to migrate from Make to n8n

Export Make blueprints and run history, rebuild each live scenario as an n8n workflow, map routers and error handlers, move webhooks and cut over.

Questions

Can Make scenarios be imported into n8n?

No. A Make blueprint is a JSON file, but its modules do not map one to one onto n8n nodes, and there is no reliable converter. Routers, iterators and aggregators all have equivalents in n8n, so each live scenario is rebuilt by our engineers as part of the fixed-price onboarding.

Is n8n open source?

No. n8n uses the Sustainable Use Licence: source-available, free for your own internal business use, restricted for offering it to others as a service. Pilae runs a dedicated instance for your organisation, which fits the internal-use terms, and we confirm the licence position with the licensor before deployment.

What if an app we use has no n8n node?

If it has an API, n8n calls it with the HTTP node, as Make does with its HTTP module. We build and maintain that step and include it in the upgrade tests.

What happens to our workflows if we leave Pilae?

They are in your Postgres, and the compose files and runbook are in your repository. The key that protects the credentials is already yours.

Leave Make with a plan, not a weekend.

An inventory of what you actually use, the app that replaces it, and a fixed price for the move.

Replace Make