Describe, Deploy, Own

Build automations using natural language or our visual canvas. We generate real, exportable TypeScript — no lock-in.

How it Works
drag to spin
How it works

From canvas to cloud in minutes.

↺ Agent Tool CallTriggerrefund_callMCP Agent inputReview Gatepolicy_checkAST & schemaWorkerstripe_refundCloudflare edge
  1. Step 01 (Author): You or your agent builds the workflow on canvas, in plain English, or over MCP.
  2. Step 02 (Review): It's checked by a structural validator, then compiled directly to TypeScript.
  3. Step 03 (Deploy): You approve the changes, and it deploys directly to your Cloudflare account.
  4. Step 04 (Call back): It runs globally in your account, and your agent can call it as a tool.
01Author
02Review
03Deploy
04Call back
AuthorSTEP 01 OF 04

You or your agent builds the workflow on canvas, in plain English, or over MCP.

Integrations

Yes, it connects to that.

SlackOpenAIStripeGitHubNotionAirtableHubSpotSupabaseGoogle SheetsAnthropicAnd more

Pre-wired for the modern stack.

What you build

Infrastructure-grade workflows.

Our analyzer reads your graph's shape and automatically assigns the correct Cloudflare compile target under the hood.

Refunds a human has to approve

Human in the loop
compiles to Cloudflare Workflow

A support agent that files its own tickets

AI agent
compiles to Email Worker

The 9am revenue digest

compiles to Scheduled Worker

Ask your docs, in chat

RAG
compiles to Worker

Form to CRM, without the copy-paste

compiles to Worker

Nightly sync into the warehouse

compiles to Cloudflare Workflow

GitHub issue triage & auto-reviewer

DevOps
compiles to Worker

Instant payment webhook & ledger sync

compiles to Cloudflare Workflow

Auto-scheduler & calendar invite agent

compiles to Email Worker
Demo

Watch an agent build one.

claude code · mcp

>

  • list_node_types209 nodes · 18 groups
  • get_node_schemas5 types
  • create_workflowrefund_approval
  • update_workflow7 nodes · 6 edges
  • validate_workflowok · 0 errors
  • compile_preview13.7 KB gzip

The agent writes graph JSON, never a script. What it hands us is data, which is the only reason the next three steps are possible at all.

Refund approval0/7 nodes
truefalsetrue01MCP Toolmcp_trigger02If/Conditionif03Slack: Post MessageslackReached on the "true" branch04Wait for Eventwait_for_eventdurable05If/Conditionif06HTTP Requesthttp_requestReached on the "true" branch07HTTP Requesthttp_requestReached on the "false" branch
Asks before deploying
by default
Can bypass the compiler
no
Runs on
your account
Available on
every plan
Control

Control at your fingertips.

Your agent can build, check and propose. By default, nothing reaches your Cloudflare account until you say yes.

  • Your agent never sees a credential

    No endpoint returns a credential's value, not to an agent and not to you. A test run can only send a credential to that service's own API.

  • Encrypted for your account alone

    AES-256-GCM under a key derived for your account. The master key is never stored in our database.

  • Keys we cannot use

    Lock a credential with a passkey or passphrase. We hold nothing that can unwrap it, so deploying it needs you there.

  • Permissions per agent

    Choose what each connected agent may do and which workflows it may touch, and cap its daily actions. It never gets more than its sign-in allowed.

  • Callable tools need a token

    A workflow your agent can call requires a bearer token by default. A blank one will not compile.

  • Your data stays in your account

    What your workflows read and write moves between your Cloudflare account and your services. We store no execution data, and fetch run history from your account when you look.

Read the full security model →
Cost

Scale your automations, not your bill.

Reasonable pricing, so you can allocate budget to what matters. Our flat fee stays predictable while executions run directly on your Cloudflare account at wholesale compute rates.

Monthly cost · both axes logarithmic100,000 runs
YouA leading per-task platformHover or drag the chart

The shaded gap is what a per-task platform would have cost instead.

Against a per-task platform

22×

less, at this volume — $500 a month against $23.

Nodes2Cloud Pro
$18flat and just once
Cloudflare requests
$5their bill, your account
Cloudflare steps · up to 4/run
$0within the allowance
Questions

The questions you were going to ask anyway.

Yes. Run:npx -y n2c-mcp@latest installto give Claude Code, Cursor, or any MCP client 37 tools to browse schemas, build workflows, preview compiled Workers, test nodes, and deploy. Deploys require your approval by default.

No. Describe what you need in plain English and the assistant creates the steps for you to review, or build by dragging nodes on the canvas. Nothing goes live until you approve it.

No. Your Workers execute in your own Cloudflare account, but Nodes2Cloud automatically provisions the necessary databases, storage buckets, queues, and secrets for you.

No. Cloudflare's free tier includes 100,000 Worker requests per day, D1 databases, and Workflows. If your volume expands, you pay Cloudflare directly with zero markup from us.

Yes. Add an MCP Tool trigger to your workflow. The deployed Worker exposes an MCP endpoint that coding agents can discover and call directly using a bearer token you control.

209 nodes are supported out of the box, connecting to 142 external services. You can also connect to any REST API using the HTTP Request node or run custom JavaScript via the Code node.

Yes. The editor includes an importer covering 109 node types with an upfront compatibility report. You only need to reconnect your service credentials once in Nodes2Cloud.

No. Workflows run directly inside your Cloudflare account, so execution payloads never pass through our servers. API secrets are encrypted per account in Cloudflare Secrets Store.

Your automations continue running uninterrupted because they live in your Cloudflare account. You can also export your project as standard TypeScript source code and deploy it from your own CI pipeline at any time.

Not today. We plan to release the compiler and node libraries under Apache-2.0 in the future, but Nodes2Cloud is currently proprietary.
early access

Ship automations in minutesLet the cloud handle the rest

Tell us one automation you need, and we’ll build it with you.Email the founders →
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.