Research checked 27 August 2026 against the providers’ official public pages. This is educational comparison, not personal testing, a universal winner or a promise of savings or results. Features, limits and prices can change.
Short answer
Albato presents a step-oriented automation builder, more than 1,000 apps and transaction packages based on successful post-trigger steps. Make presents a canvas-first visual builder, more than 3,000 standard apps and a credit system in which most ordinary module operations use one credit, while some AI and advanced features use credits differently.
That makes Albato worth examining for a team that prefers a relatively guided trigger-and-action structure and can model successful step usage. Make may suit a team that values a broad catalogue and wants to see branching, filters and transformations across a visual scenario. Neither description proves that a particular workflow will be easier, cheaper or safer. Build the same representative process in both before choosing.
At-a-glance comparison
- Builder: Albato organises an automation around a trigger followed by actions and tools; its documentation also covers filters, routers and an error-handler tool. Make arranges app modules, routers, filters and error routes on a visual canvas.
- Published catalogue: Albato says 1,000+ apps; Make says 3,000+ standard apps. These are provider counts, not evidence that every required action, field or regional variant exists.
- Core usage unit: Albato counts each successfully executed automation step after the trigger as a transaction; the trigger itself does not consume one. Make bills in credits: by default, most fixed-rate app operations use one credit, but some modules and AI features consume more or use dynamic rates.
- Free allowance: Albato’s pricing page displayed 100 transactions, five active automations, two steps per automation and seven-day logs. Make displayed 1,000 credits per month, two active scenarios and a 15-minute minimum scheduled interval.
- Error controls: both provide logs and recovery options, but their mechanisms and plan limits differ. Configure and test them; do not treat “automatic” as “unattended”.
Builder approach and learning curve
Albato’s model starts with a trigger, then adds actions and built-in tools. Its help material shows incoming filters, a router and an error handler that can stop a flow, continue it or direct it to a later step. This structure may feel approachable when the process is mainly “when this happens, do these things”, although branching, mappings, API behaviour and duplicate handling still require care. See Albato’s first-automation guide and error-handler guide.
Make calls workflows “scenarios” and their steps “modules”. Its visual canvas makes routes and dependencies visible, and its official plan comparison includes routers and filters on the Free tier. This can help with multi-branch processes, but a large canvas can also expose more concepts at once: bundles, mappings, iterators, filters, scheduling, credit consumption and error routes. See Make’s product overview and router documentation.
Do not infer learning time from the interface alone. Ask the person who will maintain the workflow to reproduce a real exception, find the relevant execution and recover it without help.
Apps, triggers and actions
Albato’s app catalogue and pricing page advertise more than 1,000 apps. Its Pro comparison also lists custom webhooks/API access and an Apps Integrator for custom apps. Make’s integration catalogue and pricing page advertise more than 3,000 standard apps, alongside custom apps and enterprise-app availability that may depend on plan.
The larger number is useful for discovery, but it should not decide the purchase. For each service, verify the exact trigger and action, searchable fields, pagination, attachments, custom fields, authentication method, API rate limits, UK account compatibility and whether the connector is maintained by the platform or another party. If a native action is missing, compare the HTTP/API route and the skills needed to support it.
Transactions versus credits
Albato’s pricing FAQ defines a transaction as a successfully executed automation step after the trigger; triggers do not consume transactions. A trigger followed by three successful actions can therefore use three transactions. The page says that, after an included package runs out, automations continue with additional transactions priced 50% above the included package rate, with notifications as the limit approaches. Treat this as potential overage, not a hard stop, and check current billing controls.
Make’s credits guide says most apps use a fixed rate that defaults to one credit per operation. One scenario run can create many operations when modules process multiple bundles. Some advanced modules have a higher fixed rate, while some AI features vary with tokens, file size, page count or processing time. A custom third-party AI connection can also mean paying Make for operations and the AI provider separately for tokens.
Neither unit maps neatly to “one completed customer job”. Model a normal month and a busy month, including polling, multiple returned records, branches, loops, retries, code or AI steps, and overage. Compare successful business outcomes as well as platform units.
Plan snapshot, not a quote
At the time checked, Albato showed Free at $0 with 100 transactions; Pro at $22 per month on the monthly view or $15 per month on the annual view for 1,000 transactions; Teams marked “Coming soon” from $93 monthly or $65 on the annual view with 5,000 transactions; and Custom by quotation. Pro listed unlimited active automations and steps, five-minute updates, 30-day logs and one seat. Albato’s page displayed inconsistent trial wording in different sections, so confirm the trial duration during registration.
Make showed Free at $0 with 1,000 credits per month; Core at $12 per month, Pro at $21 and Teams at $38 at the displayed 10,000-credit monthly level; Enterprise was contact sales. Core added unlimited active scenarios and scheduling down to one minute; Pro added priority execution, custom variables and full-text log search; Teams added team roles and shared templates.
UK pricing caveat: these are dated US-dollar values served during research, not checkout quotes. Annual prices involve a longer commitment, and exchange rates, VAT or other taxes, included usage, overage and plan features may change. Re-select the required billing frequency and volume on each current pricing page.
Error handling and operational recovery
Albato’s error-handling documentation describes email notifications, manual resending, automatic retries for timeout errors and a penalty-point system that can slow or stop an automation after repeated connection or timeout failures. Its newer error-handler tool can continue, stop or move to a selected later step. These controls still need a named owner: resending after an earlier action succeeded can create duplicates unless the workflow is designed to be safely repeatable.
Make documents five error-handler types—Skip, Retry, Resume, Commit and Rollback—and incomplete executions that can be stored for inspection and recovery. Some rollback behaviour applies only to modules that support transactions; other external actions may already have happened. Read Make’s error-handling overview and test partial completion, rate limits, expired credentials and a downstream outage.
For either platform, define alerts, duplicate prevention, safe retry rules, reconciliation and a manual fallback. A successful retry mechanism is not a substitute for checking whether an earlier side effect already occurred.
Data protection and security questions
Albato’s security page states SOC 2 Type 2 certification, GDPR-aligned operations, AES-256 encryption at rest, TLS 1.2/1.3 in transit, AWS hosting across two zones and automatic deletion of accumulated log data after 60 days, with an option to opt out of log recording. It says ISO 27001 certification is in progress, not completed.
Make’s security page states ISO 27001 certification, SOC 2 Type II and SOC 3 audits, AES-256 encryption at rest and TLS 1.2/1.3 in transit. Its plan comparison lists features such as team roles, SSO and enterprise controls at particular tiers rather than universally.
These are provider statements, not a UK GDPR assessment of your workflow. Review the current data-processing agreement, privacy notice, subprocessors, international-transfer basis, data location and retention settings. Map what enters logs and incomplete executions; minimise connected-account scopes; use dedicated business connections where possible; remove leavers; and obtain appropriate review before processing special-category, payment, legal-decision or safety-critical data.
Which may fit?
- Investigate Albato when: the required apps and actions are present; a trigger-and-steps workflow matches how the team thinks; successful post-trigger transaction accounting is understandable for the workload; and the available collaboration and recovery controls meet the need.
- Investigate Make when: broader catalogue coverage matters; the workflow benefits from visible multi-route logic and transformations; the team can learn Make’s scenario concepts; and it can monitor bundle-driven and dynamic credit usage.
- Pause on both when: an exact action or permission is missing, a hosted intermediary is unacceptable, nobody will own failures, or the process is low-volume but high-consequence and safer with human review.
There is no universal winner. Prototype the same workflow with safe sample data, include at least one failure route, record real usage, inspect the resulting logs and have the future owner maintain it. The better fit is the one that meets the documented requirements with acceptable cost, risk and support burden.
Affiliate disclosure
Both buttons below are affiliate links. If you register or buy through one, UK Digital Tools Research may receive a commission under that provider’s current programme terms, with no extra charge added because of the link. Albato may apply a first-payment referral discount; confirm that it appears at checkout and do not assume it combines with another promotion. This does not make either platform suitable for your business or support a universal ranking. See the site’s full affiliate disclosure.
Check the current plan, usage allowance, billing frequency, taxes, renewal and cancellation terms before paying. No saving or business result is guaranteed.
Official sources checked
- Albato pricing and plan comparison
- Albato app catalogue
- Albato first-automation guide
- Albato error-handler tool
- Albato error handling and retries
- Albato security and compliance
- Make product overview
- Make pricing and plan comparison
- Make integration catalogue
- Make credits guide
- Make router documentation
- Make error-handling overview
- Make security and compliance
Read the Albato evaluation guide, Albato pricing guide, Make pricing guide or use the platform-neutral automation checklist.