Make builds scenarios in the cloud. Cronable builds them on your machine.
Make (formerly Integromat) is a polished visual builder for cloud-to-cloud scenarios, priced in credits. Cronable is a visual builder for work that has to run on a real computer, priced by how many jobs you keep.
The short answer
Make is a polished editor for scenarios that live entirely in the cloud. Cronable covers the steps a cloud-only shape structurally cannot reach: touching a file on your disk, running a script, reaching a host inside your network, or driving an AI agent with the credentials you are already signed in to.
It also counts jobs rather than operations, so a pipeline does not get more expensive as it gets busier. And you describe what you want in plain English rather than assembling modules — the assistant builds the scenario, schedule and error handling, and you edit it on the canvas.
Cronable vs Make
Where Cronable and Make actually differ, capability by capability.
| Capability | Cronable | Make |
|---|---|---|
| Where scenarios run | Your own machine or server | Make’s cloud |
| Pricing meter | Number of jobs you define; runs unmetered | Metered in credits — one per operation, more for Make AI |
| Build a job by describing it in plain English | The assistant builds the whole job, on every plan | AI assistance for building scenarios |
| App catalogue | 123 connectors | Well over a thousand |
| Visual editor | Draggable DAG with live run state | Mature scenario canvas with routers and iterators |
| Local files, scripts and private hosts | Yes | No — cloud only |
| Job definitions stored as | One YAML file per job, in your git repo | Scenario blueprints in the vendor’s account |
| Inbound webhooks without opening a port | Yes — hosted relay forwards them, Basic and up | Yes |
| Manage it from anywhere | Yes — remote control in the browser, no port opened | Yes — it is a website |
| Data residency | Your machine; nothing to configure | Vendor-hosted, with regional options |
| Runs while your machine is off | Only if you run it on a server | Yes |
| Setup effort | A click to install; a wizard does the rest; updates are automatic | None — sign up and go |
| Maintenance burden | Signed updates roll out automatically; you keep the encryption key safe | None |
Where scenarios run
Cronable
Your own machine or serverMake
Make’s cloudPricing meter
Cronable
Number of jobs you define; runs unmeteredMake
Metered in credits — one per operation, more for Make AIBuild a job by describing it in plain English
Cronable
The assistant builds the whole job, on every planMake
AI assistance for building scenariosApp catalogue
Cronable
123 connectorsMake
Well over a thousandVisual editor
Cronable
Draggable DAG with live run stateMake
Mature scenario canvas with routers and iteratorsLocal files, scripts and private hosts
Cronable
YesMake
No — cloud onlyJob definitions stored as
Cronable
One YAML file per job, in your git repoMake
Scenario blueprints in the vendor’s accountInbound webhooks without opening a port
Cronable
Yes — hosted relay forwards them, Basic and upMake
YesManage it from anywhere
Cronable
Yes — remote control in the browser, no port openedMake
Yes — it is a websiteData residency
Cronable
Your machine; nothing to configureMake
Vendor-hosted, with regional optionsRuns while your machine is off
Cronable
Only if you run it on a serverMake
YesSetup effort
Cronable
A click to install; a wizard does the rest; updates are automaticMake
None — sign up and goMaintenance burden
Cronable
Signed updates roll out automatically; you keep the encryption key safeMake
NoneWhat you get by running it on your own machine
Say what you want; it builds the pipeline
Type “every morning, check yesterday’s Stripe refunds and post the total to Slack” and the built-in assistant builds the whole job — the steps, the schedule, the credentials it needs and what happens when one fails — wired and ready to run. You review it on the canvas and change anything. On every plan, including Free.
It runs where your work already is
Cronable installs on the machine you actually use — a Mac or Windows app, or a server you own. A job can open your files, use the CLIs you are already signed in to, and reach anything on your network, because it is running as you, on your box.
Runs are not metered
Plans are sized by how many jobs you define — 6 on Free, up to 1,000 on Business — not by how often they fire. A job that runs every minute costs the same as one that runs monthly. The one thing that is counted per use is the AI assistant, which has a daily message allowance per plan.
SaaS webhooks reach your machine
Give Stripe, GitHub or a form tool a URL and the hosted relay forwards the event to your install — again with no port opened and nothing exposed to the internet. Each install gets its own partition, and jobs fire the moment the event lands. Basic and up.
Reach it from anywhere — no open ports
Remote control lets you drive your install from a browser wherever you are. The machine dials out to the hosted relay; you never expose a port, forward anything on your router, or run your own tunnel. It is opt-in, off until you switch it on, and included from Basic up.
Installed and running in minutes
Install the Mac or Windows app in a click, or paste one line on a server — no Docker, no database to provision, no reverse proxy to configure. A first-run wizard sets you up, spots the tools you are missing and offers to install them, and updates roll out signed and staged in the background with automatic rollback.
Cronable and Make
Is there a free tier?
Yes — Free covers up to 6 jobs, 1 user, 1 machine and 5 AI assistant messages a day, with all built-in job types, git sync and encrypted secrets. Inbound webhooks and remote control start at Basic.
Does Cronable meter usage the way Make’s credits do?
No. Ordinary runs and the steps inside them are not counted, however often they fire. The caps that do exist are on jobs, inbound webhooks, machines, users, and the AI assistant’s daily messages — which a job calling the assistant does draw from. Every one of them is listed on the pricing page.
Can I import Make scenarios?
Not automatically. The usual route is to describe the scenario to the built-in assistant, which builds the equivalent pipeline for you to review and edit on the canvas.
Automate your operations.
Cronable is launching soon. Join the waitlist and we’ll email you the moment self-serve accounts — and the apps for Mac, Windows and Linux — go live.