For freelancers and automation agencies

Build automations your clients own.

Each workflow compiles to a Cloudflare Worker and deploys into your client's own Cloudflare account. They pay Cloudflare for the runs, and the automation keeps running after your engagement ends.

The call opens an email to the founders · Multi-client accounts are in early access
Today

Where client automations usually end up.

On your Zapier bill

Per-task pricing grows with your client's volume. You either mark it up and explain it every month, or you absorb it.

On an n8n server you run

One instance per client means you own the updates, the backups and the outage at 2am.

Behind a password they shared

To deploy anything, the client sends you their login or pastes an API token into a chat.

How it works

From brief to handover in four steps.

  1. 01

    Build it

    Drag nodes on the canvas, describe it in plain English, or let your coding agent write it over MCP.

  2. 02

    Send the client a link

    They sign in to Cloudflare and approve the connection. No Nodes2Cloud account, and no password handed to you. The link works once and expires in seven days.

  3. 03

    Deploy to their account

    Each workflow is pinned to one client's Cloudflare account at its first deploy, and a live workflow can't be repointed to another.

  4. 04

    Hand it over

    It is already running in their account. Export it as a Wrangler project for their own repository.

Ownership

What your client keeps if you part ways.

Agencies get replaced. Their automations shouldn't break when it happens. Clients notice that before they sign.

The running workflow
in their Cloudflare account
The run bill
paid to Cloudflare directly
The code
a Wrangler project export
What they need from us
nothing, to keep it running
Agency questions

What agencies ask us first.

Your client, directly to Cloudflare. The workflows run in their account under their Cloudflare plan, and Cloudflare's free plan includes 100,000 Worker requests a day. We never charge per run, so there is no usage bill for you to mark up or absorb.

Connecting more than one client account is part of Team, which is in early access and has no public price yet. Tell us how many clients you build for and we will set you up. Pro is $18/month flat and covers one Cloudflare account, if you are starting with a single client.

No. You send them a link. They sign in to Cloudflare and approve the connection, and their account appears in your workspace under their name. The link works once and expires after seven days.

Not in production. Deployed workflows run in your client's Cloudflare account, so their data goes straight between that Worker and the services it calls. Test runs, live debug sessions and agent tool calls through our MCP server pass through us in transit, and we store none of it. Credentials are encrypted under a key derived for your account.

Their workflows keep running, because they already live in the client's Cloudflare account. Export each one as a Wrangler project and hand it over with the account. They can redeploy or change it without you, and without us.

Every deployed workflow keeps running in the Cloudflare account it was deployed to. You lose the editor. Export your workflows as Wrangler projects any time and you keep a copy that deploys without us.
Moving clients off Zapier or n8n?

Bring one client workflow to the call.

Twenty minutes with the founders. We'll look at a workflow you run for a client today and tell you plainly whether it fits.

early access

Join the waitlist

We’re opening Nodes2Cloudin batches. Leave your details and we’ll email you when it’s your turn.

We’ll only use this to contact you about access. See our privacy policy.