Supergood vs Microsoft Power Automate in 2026: Bundled Desktop Flows Against Generated API Calls

Overview

For a buyer already inside the Microsoft estate this comparison opens awkwardly: Power Automate can automate a no-API system for nothing. Its Free licence covers "authoring and running desktop flows locally (attended)" on a work or school account (learn.microsoft.com, read 21 September 2026). Supergood publishes no price at all. If cost were the whole question the page would end here.

It is not, because the two put different things into production. A desktop flow replays a recorded sequence against the vendor's screen on every run; Supergood records once, during authoring, and ships generated HTTP calls on a fixed contract. What you license follows from that, and so does what breaks.

Supergood's side comes from synthetic AutomationAtlas tests run in September 2026; Microsoft's rests on its own documentation and pricing pages, read 21 September 2026.

Company Snapshot

The Core Trade-Off: The Cheap Entry Does Not Survive Production

Power Automate's free desktop automation is real, and it is attended. Microsoft's licensing page says the Free licence covers "authoring and running desktop flows locally (attended)" with "standard connectors only", while Premium, at "$15.00 user/month, paid yearly", adds premium connectors and "an attended bot borne by the license" on a registered workstation (learn.microsoft.com, read 21 September 2026). Attended means a machine someone signed into.

Unattended is where the bill starts, and it starts twice. A Process licence, "$150.00 bot/month, paid yearly", "becomes an unattended bot that can run one desktop flow at a time", and Microsoft adds that "allocation of a Process license to a machine (required by the unattended mode) still prerequires the machine was registered by a Power Automate Premium user". So unattended RPA costs a capacity licence and a user licence. Parallelism is then bought one bot at a time: "to run multiple unattended desktop flows in parallel, purchase Process licenses for the maximum number of runs that are needed to execute in parallel".

Supergood's unit is the request instead: ten concurrent calls are ten HTTP requests, not ten licensed bots. It is a poor match for a team that buys on documented, installable tooling, because its homepage tells you to run npx supergood-mcp init, and on 21 September 2026 both supergood-mcp and the scoped @supergood/mcp returned HTTP 404 from the public npm registry. Power Automate is the wrong shape wherever every parallel run has to be licensed as its own bot.

In a Microsoft Tenant, Supergood Replaces the Machine, Not the Flow

What Supergood actually displaces in a Microsoft shop is the unattended machine, and Microsoft's own licence terms show why. A Process licence has two lives: allocated to a machine it "becomes an unattended bot that can run one desktop flow at a time", and assigned to a cloud flow it carries 250,000 actions a day and "lets it use premium and custom connectors, no matter what license the owning or triggering user has" (learn.microsoft.com, read 23 September 2026). Replace the screen-driving leg with an HTTP call to a generated endpoint, and the same $150 a month stops buying one run at a time on a machine you keep patched and signed in, and starts buying a daily action budget with no machine behind it.

Everything else stays put. The Teams approval, the SharePoint list and the Outlook notice remain Power Automate's, and the flow, which has to sit in a solution to take the licence, makes one call out for the system that has no API. Because the licence is on the flow, colleagues who trigger it from Teams need no Premium seat of their own; an instant flow otherwise runs in the invoking user's licence context, and each of them would.

What bites is organisational. A custom connector pointing outside the tenant is exactly what Power Platform data policies let admins classify, down to its host URL, so this decision belongs to whoever owns your tenant's data policy, not to the maker who recorded the desktop flow. You are also swapping a price Microsoft publishes for one Supergood does not. Anything that still has to click a Windows application stays a desktop flow.

What Runs in Production, and What the Recording Is For

Power Automate

A desktop flow interacts with the machine "by using application UI elements, images, or coordinates" (Introduction to desktop flows, learn.microsoft.com, last updated 24 August 2026). That is the mechanism and also the dependency: whatever the vendor does to those elements is done to your automation. In exchange you get reach Supergood does not offer — the whole Windows desktop, legacy applications and terminal emulators included, plus premium connectors on the same licence. The recorder produces the steps the robot repeats, so a path nobody recorded is a path somebody has to record.

Supergood

Supergood's recorder produces evidence an agent reasons over rather than steps to replay. It reads the captured network calls alongside the site's compiled JavaScript bundles, then writes an integration covering more than it watched. In our September 2026 synthetic test the agent recovered a portal's full taxonomy, 8 real-estate and 17 movable sub-category codes and 16 provinces, from two recorded searches in one province.

That is the whole trade, and it belongs on the cost side of the ledger rather than the feature side. A recording demonstrates intent; it does not specify behaviour. Most of that taxonomy was never demonstrated to the recorder that built the integration, and what is inferred stays inference until somebody checks it. A path nobody recorded in Power Automate does not exist, because there are no steps to run. A path nobody recorded in Supergood may already be in the integration, carrying no marker that says so. The method is set out in how to turn a no-API portal into a REST endpoint.

Pricing (as of September 2026)

Microsoft prices four tiers down to the cent, and a buyer can model every one of them without speaking to anybody.

Power Automate (from the Microsoft pricing page)

Read 21 September 2026: Premium at "$15.00 user/month, paid yearly"; Process at "$150.00 bot/month, paid yearly"; Hosted Process at "$215.00 bot/month, paid yearly"; and a Process Mining add-on at "$5,000.00 tenant/month, paid yearly". Microsoft's licensing documentation adds the entitlements: 40,000 actions a day per Premium user and 250,000 per Process licence.

Supergood

Supergood publishes no price at all. On 21 September 2026 supergood.ai/pricing returned HTTP 404 on both the bare and www hosts, no pricing link appeared in the homepage nav or footer, and a scan of the homepage source found no dollar figure on it. The only commercial wording is a call to action: "Pay when you close".

Cost Comparison (Estimated Annual)

What a buyer here is really buying is a working integration against one specific vendor system, and neither product has a price for that. Microsoft sells seats and capacity and leaves the build to you. Supergood publishes nothing you could cost. The per-call economics of browser-driven against direct execution are covered in our answer on recorded workflow APIs and hosted browser sessions.

Editor's Note: Two recorded searches in one province yielded a portal's whole taxonomy: 8 real-estate and 17 movable sub-category codes and 16 provinces. Sit with that number for a moment. It means most of what the integration can do was inferred rather than recorded in the build we watched. A desktop-flow recorder cannot generalise like that. The reason it cannot is the same reason its coverage is knowable, because a path nobody recorded is a path that does not exist. What generalisation costs is the ability to say where your automation stops, and a catalogue gives that away free; you find out where a generated integration ends by calling it. In return, generalisation buys you the systems no connector catalogue lists. — Rafal Fila, ShadowGen

Governance, Admin Controls, and Compliance

Power Automate

Governance here is licence-shaped. Microsoft's licensing documentation states that "multiple monitoring pages in the Power Automate portal (for example, workqueue page, machine list page, desktop flow list page, and more) are displayed only to Power Automate Premium users" (read 21 September 2026). Whoever watches the estate needs the paid seat, whatever the flows are licensed as. Against that, a Microsoft-estate buyer inherits Entra identity, managed environments and Dataverse entitlements without a separate procurement.

Supergood

The identity that runs a generated integration is created for the purpose, and it is the first thing a security reviewer will stop on. Ours ran on a service account with a generated email address and phone number, created so it could absorb MFA challenges on its own. It depends on credentials and a schema the source system can change without telling anybody. Public documentation covers none of this: the MCP endpoints the dashboard describes appear nowhere on supergood.ai, and the package the homepage tells you to install does not resolve on npm (both checked 21 September 2026). A control an auditor can only read about from inside the product is a control they meet for the first time during the audit.

Selection Framework

Start from whether volume means concurrent machines or concurrent calls.