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.
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.
From brief to handover in four steps.
- 01
Build it
Drag nodes on the canvas, describe it in plain English, or let your coding agent write it over MCP.
- 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.
- 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.
- 04
Hand it over
It is already running in their account. Export it as a Wrangler project for their own repository.
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
What agencies ask us first.
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.