On smaller screens, scroll sideways to compare both tools.

Features and pricing of selected tools
Compare featuresWindmillActivepieces
Best forA script and workflow execution platform; distinguish hosting, builder roles and compute costs.An automation builder with hosted and self-hosted options, evaluated here through operating responsibility and access requirements.
CategoryAutomation & websitesAutomation & websites
Paid entry priceCheck official pricingUsage-based or variable · Cloud / self-hosted options

No universal paid starting price is asserted across hosting, seat and compute configurations. Community software does not remove infrastructure costs.

US$20 / mo+Billed monthly · Plus

Monthly Plus base fee. Check usage charges, external AI/API bills and self-hosted infrastructure separately.

Free planSupportedSupported
Japanese supportUnverifiedUnverified
DeploymentCloud / self-hostedCloud / self-hosted
Reasons to choose
  • Evaluate maintained code together with execution procedures
  • A free self-hosted Community edition is documented
  • Hosted evaluation can precede an operating-model decision
  • A free self-hosted Community edition is documented
Before you subscribe
  • Check builder, operator and compute entitlements separately
  • An execution allowance is not infinite processing capacity
  • Do not assume Cloud and Community have identical entitlements
  • Japanese interface and support coverage remain unverified
Pricing checkedUnverified2026-10-27
Official pricingCheck pricingCheck pricing

Prices exclude tax, currency conversion and introductory discounts. Different currencies and billing periods are not directly comparable. Japanese support can apply to input, output or the interface; check each tool’s scope.

In this guide
  1. Map standard and custom operations
  2. Distinguish builders and business operators
  3. Evaluate edition scope, not licence headlines
  4. Normalize the full month of work
  5. A hypothetical reviewed-request workflow
  6. Preserve a portable operating specification
  7. Compare a change, not only the first build

Map standard and custom operations

Map lookup, calculation, write and notification and mark custom logic. A connector name does not establish that every required operation exists. A code requirement is not automatically a disadvantage; assess it alongside the availability of a maintainer and a clear rule specification.

Distinguish builders and business operators

Consider whether someone inspecting results needs permission to change the logic. Verify actual role separation in the applicable offers. A useful handoff test asks whether an operator can identify unfinished or failed work without the original builder narrating every step.

Evaluate edition scope, not licence headlines

Separate a free self-hosted start from paid administrative entitlements on both sides. Map placement, identity, audit and external-user requirements to the appropriate edition. Running on a private server alone is not evidence that every required access or historical control is available.

Normalize the full month of work

Apply role, compute and credit descriptions to the same inputs and outputs for a month. Separate base charges, extra consumption, upstream APIs and maintenance. A replay assumption should be labelled as a sensitivity scenario until observed, rather than presented as a measured reliability result.

A hypothetical reviewed-request workflow

Consider a hypothetical request reviewed by a person before a register update. Distinguish waiting, returned and changed-after-approval states. In either candidate, separate review from execution authority and test that unapproved input cannot proceed to a live record change.

Preserve a portable operating specification

Retain logic, action mapping, stored state and connection ownership. Identify what a future move must rebuild, and separate saved configuration from legitimate secret-access transfer. If staffing changes, review the operating model rather than continuing solely because an installed edition has no licence fee.

Compare a change, not only the first build

Simulate an upstream field-name change and locate affected input, transformation, register and notification logic. Check whether one maintained component fixes it or repeated rules are embedded across several flows. Record locating and validating the change, not only initial build effort. A configuration with an understandable specification may fit continuing ownership better than one that was quicker for its original author.

Estimate costs for your workload

Enter monthly jobs, billable steps and retries to see how different billing units affect your estimate.

Open cost calculator

Official sources

Pricing, availability and feature limits can change. Check the linked official pages before subscribing.

How we compareAdvertising disclosure