Automation platforms
Automation platforms connect the apps you already use so routine work runs by itself: a new form entry becomes a CRM contact, a Slack alert and a spreadsheet row. They range from simple consumer tools and point-and-click business builders to open-source platforms you can host yourself and enterprise integration suites. The real trade-offs are how usage is counted and capped, which apps are supported, how failures are handled, and whether you can run it on your own servers.
Last updated
How to choose
Start with your apps and triggers
List the apps your workflows must touch and check each platform's directory for them. A connector existing is not enough: check it has the specific trigger (what starts the workflow) and actions you need, and whether the trigger is instant or polled. Generic HTTP and webhook steps can fill gaps, but only if the app has a usable API and you are comfortable with it.
Work out what your usage will really cost
- Know the billing unit. Some platforms count every action step (tasks or operations), others count each whole workflow run (executions). A 10-step workflow run 1,000 times a month is 10,000 units on per-step billing but 1,000 on per-run billing.
- Estimate volume honestly. Multiply runs per month by steps per run, add headroom, and compare against each plan's allowance. Check what happens at the cap: paused workflows, overage fees, or a forced upgrade.
- Count users and premium features. Team seats, premium connectors, faster polling and longer log retention are often only on higher tiers.
Plan for failure
Every automation eventually breaks: an app changes, a token expires, a service goes down. Look for error branches or handlers, automatic retries, the ability to replay failed runs, and alerts when something fails. For business-critical workflows, check how long run history is kept so you can investigate problems.
Decide where it should run
Cloud-only tools are easiest to start with. If data must stay in your own environment, or volumes would make per-step pricing expensive, look at platforms with a self-hosted edition, and check the license terms for commercial use. Self-hosting means you handle servers, upgrades, backups and security.
Match the builder to who maintains it
Linear step builders are fastest for simple automations. Visual canvases make branching and loops easier to follow. Code-first tools suit developers who want version control and full control. If non-technical staff will own the workflows, favor the simplest builder that handles your logic.
Check security and compliance
For company data, ask for the vendor's SOC 2 report, check data residency options if you serve EU customers, and look for single sign-on, role-based access and audit logs on the plan you would buy.
Before you commit
Build your most important workflow on a free plan or trial, run it with real data for a week, and deliberately break it to see how errors surface. Pricing and limits change often, so confirm current terms on the vendor's pricing page.
This market moves fast: Relay.app shut down in September 2026, and Pipedream has closed its workflow product to new customers ahead of a shutdown on March 31, 2027. Favor vendors with a clear track record, and keep exports or documentation of your workflows so you can move if you have to.
Answer
Browse the table. Filter to what matters.
Use the filters below, then sign in if you want to shortlist and decide with friends.
Sign in to vote, hide services and features, and reorder.
Verified: hover a cell and click its green dot for the source Estimate: no cited source Not stated: the company doesn't publish it
| Feature | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ |
|---|---|---|---|---|---|---|---|---|---|---|
|
⠿
Free plan
|
|
|
||||||||
|
⠿
Free plan usage
|
Unlimited (self-hosted Community Edition)
|
Doesn't apply
|
Doesn't apply
|
Doesn't apply
|
||||||
|
⠿
Starting price
|
$2.99/month, Starter plan, billed monthly
|
|||||||||
|
⠿
Entry plan usage
|
10,000 per month, credits
|
40,000 requests per user per day
|
||||||||
|
⠿
Billing unit
|
||||||||||
|
⠿
App integrations
|
||||||||||
|
⠿
Self hosting
|
Cloud only
|
Cloud only; on-premises data gateway reaches your servers
|
Cloud only
|
Cloud only
|
Cloud only
|
|||||
|
⠿
License
|
Proprietary
|
Proprietary
|
Proprietary (Microsoft commercial license)
|
Proprietary
|
Proprietary
|
Proprietary (SaaS)
|
Proprietary (SaaS)
|
Proprietary
|
||
|
⠿
Builder style
|
||||||||||
|
⠿
Error handling
|
||||||||||
|
⠿
Automatic retries
|
||||||||||
|
⠿
Custom code steps
|
None built in; Office Scripts or Azure Functions
|
None
|
||||||||
|
⠿
Polling interval
|
1 min, poll times set per trigger; schedules down to seconds
|
15 min, Starter plan; Free is hourly
|
||||||||
|
⠿
AI steps
|
||||||||||
|
⠿
SOC 2
|
|
|||||||||
|
⠿
EU data residency
|
Why these features matter
-
Free plan
A free tier lets you prove an automation works before paying, and covers light personal use. Usage caps on free tiers are usually low.
-
Free plan usage (per month)
Shows how much you can automate before paying. Units differ between vendors, so read the billing unit row too.
-
Starting price ($/month)
The entry price is what most small teams pay first. Usage overages and per-user fees can raise the real cost.
-
Entry plan usage (per month)
Usage allowances decide whether the entry plan covers your volume or whether you will be pushed to a higher tier.
-
Billing unit
A 10-step workflow can cost 10 units on per-step billing but 1 on per-run billing, so the same allowance can mean very different real capacity.
-
App integrations (apps)
More connectors means fewer apps you have to wire up by hand with API calls. Check that your specific apps are covered and support the triggers you need.
-
Self hosting
Self-hosting keeps data in your own environment and can cut usage costs, but you take on upkeep, upgrades and security.
-
License
Open or source-available code means you can inspect it, avoid lock-in and keep running it if the vendor changes course.
-
Builder style
Visual canvases suit branching logic; linear builders are quicker to learn; code-first suits developers.
-
Error handling
Automations break when apps change or go down. Good error handling stops silent failures and lost data.
-
Automatic retries
Automatic retries recover from brief outages without you noticing or re-running anything by hand.
-
Custom code steps
Code steps cover the gaps where no pre-built action does what you need.
-
Polling interval (min)
Slower polling means slower reactions for apps without instant triggers. Matters for time-sensitive work, less for daily reports.
-
AI steps
AI steps let workflows summarize, classify or draft text without a separate AI subscription or integration.
-
SOC 2
Business and enterprise buyers often need SOC 2 to approve a tool that touches company data.
-
EU data residency
Matters for companies with EU customers or GDPR data-location policies; less so for US-only use.
About the services
-
Zapier · Zapier
The biggest app catalog (9,000+ apps) and an easy step-by-step builder, so most teams can connect almost anything without code. Every action step counts as a task, so long or busy workflows get expensive; the free plan only runs two-step Zaps.
-
Make · Make
A visual canvas builder with routers, iterators and detailed error handlers, at a lower price per unit than most rivals. Every module action uses a credit, and the canvas takes longer to learn than a simple step list.
-
n8n · n8n
A developer-friendly visual node editor that you can self-host for free (Community Edition) or buy as a cloud service. Billing counts whole workflow runs, not steps, which suits long workflows. Cloud prices are shown in euros, and the source-available license restricts reselling it as a service.
-
Power Automate · Microsoft
Microsoft's automation tool, strongest for Microsoft 365, Dynamics and Azure, with desktop RPA available on higher plans. Premium is licensed per user ($15/month, paid yearly), and capacity is set as daily request limits rather than monthly runs. Many Microsoft 365 business plans already include basic cloud flows with standard connectors.
-
IFTTT · IFTTT
Simple consumer automations (Applets) for smart home devices, social media and personal apps, with the cheapest paid plan in this grid. Applets are one trigger with a few actions and limited filter code, so it is not built for complex business workflows.
-
Workato · Workato
An enterprise integration and automation platform with governance, on-premises agents and AI agents, sold only through custom quotes. Built for IT teams automating across many business systems, and overkill for small teams.
-
Activepieces · Activepieces
An open-source (MIT core) automation tool you can self-host or use in the cloud, billed per whole workflow run. A good low-cost Zapier alternative with TypeScript code steps; its app catalog is smaller and it does not yet hold a SOC 2 report.
-
Pabbly Connect · Pabbly
A low-cost, task-based automation tool with a generous 10,000-task entry plan and free internal steps (filters, routers, formatters). Pabbly also sells one-time lifetime deals. Its interface and documentation are less polished than the market leaders.
-
Integrately · Integrately
A task-based automation tool known for one-click ready-made automations, aimed at non-technical small businesses. The entry plan includes 2,000 tasks a month; it lacks code steps and published security certifications.
-
Tray.ai · Tray.ai
An enterprise integration and AI agent platform with a visual builder and an API-first (headless) option, priced by custom quote only. Suited to larger companies with integration engineers; there is a 30-day trial but no free plan.
Suggest a change
Related comparisons
-
AI coding toolsAI coding tools now range from autocomplete in your current editor to agents that work on tasks in the cloud while you do something else. This grid compares popular tools side by side on the practical things that decide a purchase: where they run, what a plan really costs, which models and agent features you get, and how your code is handled. The real trade-off is power against predictability and control: the most capable agents cost more, often bill by usage, and need more care over privacy and review.
-
AI search enginesAI search tools read the web for you and answer in a few paragraphs with links, instead of giving you ten blue links. This grid compares popular AI answer engines, search engines that now add AI answers, and the developer APIs that power AI apps, on what decides a choice: what is free, what paid plans cost, whether answers cite sources, how deep the research goes, who runs the search index, and what happens to your queries. The real trade-offs are convenience against privacy, and speed against how much you can trust and verify an answer.
-
Translation management softwareTranslation management systems (TMS) keep a team's UI strings, documents and translations in one place, with translation memory, glossaries, machine and human translation, and integrations with code and design tools. The decision is how you are charged (words, strings or keys), what a free plan covers, and how much automation and security you need.
-
Feature flag toolsFeature flag tools let engineers switch features on or off, roll them out to a slice of users, and roll them back without redeploying. This grid compares ten hosted and self-hosted tools, from open source servers to full experimentation platforms. The real trade-offs are how each one bills (per seat, per request, per user), whether you can run it yourself, and whether approvals, SSO, and A/B testing sit behind an enterprise plan.
-
Incident management softwareIncident management software wakes the right person when something breaks, gives the team one place to run the response, and records what happened so it doesn't happen again. This grid compares eight tools on what most buyers decide on: what the first paid plan really costs, whether on-call paging is included or sold separately, how well incidents run inside Slack or Teams, and how far AI goes.
-
Status page softwareStatus page software gives your customers one trusted place to see whether your service is up, read incident updates, and subscribe to alerts. Some tools are stand-alone status pages, while others bundle uptime monitoring, on-call paging, or full incident response. The trade-offs are price model (flat plan, per user, or per component), how many subscribers and team members each plan allows, and whether monitoring and paging come with it.