Automation tool
Latenode
Hosted scenario-based automation platform, with a JavaScript node and a headless browser, billed by compute time.
In short
Latenode is aimed at people who want to mix a visual builder with code. There is no subscription anymore: 10,000 CPU seconds are free each month and the rest is billed by the second. The number of steps doesn't matter but run time does, so cost depends on how slow the services you call are. Hosting is listed as US.
Documented strengths
- No base subscription: 10,000 free CPU seconds every month, then per-second billing in decreasing brackets
- The number of nodes in a scenario doesn't change the bill: only execution time counts
- JavaScript node and headless browser included in both plans, Free included
- Adjustable monthly spending cap, with a separate cap for AI
Documented limits
- Cost follows run time: a slow API, a large file or the headless browser lengthens billed time, the vendor says
- Hosting providers listed as "US"; no EU region or self-hosting in the pages we read
- AI models used without your own API key are billed on top, in "PnP tokens"
- 10-minute interval for scheduled triggers; 5 minutes or 1 minute only as a paid add-on
Who it suits
- You can read a little JavaScript, or want the option to drop some into a scenario
- Your scenarios have many steps but run fast: you don't pay per step
- You want to start with no subscription and pay only for the time you use
Probably not for
- You need data kept in the European Union, or want to host the tool yourself
- Your scenarios spend a long time waiting on slow services: waiting is part of billed time
- You want a flat, predictable monthly fee
Latenode in three lines
Latenode is a hosted automation platform: you build scenarios out of nodes, and you can drop in JavaScript or a programmatically driven browser. The vendor, Nocode LTD, founded in 2022, lists its headquarters as Cyprus. It no longer sells credit-based subscriptions: it bills the compute time of each execution, in “CPU seconds”, after a free monthly allowance.
This page analyzes Latenode’s public pricing and documentation as recorded on the date shown. Nobody here has run the product.
What Latenode actually does
A scenario starts from a trigger (a webhook, a schedule, an event in an app) and chains nodes. According to the pricing page, three things set it apart from purely visual tools:
- a JavaScript node in both plans: JavaScript node ("Full-Code Node") included in both plans, including Free;
- a headless browser, meaning a web browser driven by the scenario with no window, used to pull data from a page, fill in a form or take a screenshot; the vendor describes it as “Chromium and Puppeteer-style control”;
- AI building blocks: an “AI Agent” node, RAG storage (documents a model searches for its answers) and a database, all included from the free plan up.
On the catalog, two figures sit side by side: "5,500+ Integrations"; the "About" page also says "1,200+ apps and LLMs in one plan" source.
On triggers, webhooks fire instantly (see the webhook guide). For everything else: 10 minutes (scheduled or polling triggers); 5 or 1 minute as a paid add-on; instant webhooks.
What Latenode bills: compute seconds
Credits are gone. If you read elsewhere that Latenode sells “Micro”, “Starter”, “Grow” or “Prime” plans in credits, that is the old grid: the billing documentation says those plans are archived and visible only on legacy accounts. Holders of an old one-time-payment deal keep their allocation, converted at 1 credit for 30 “CPU seconds”.
The current rule: Latenode meters the compute time of an execution, from start to finish, not its steps. Take a 5-step automation that runs 1,000 times a month. The number of steps changes nothing; run time decides:
| Average time per execution | CPU seconds per month | Against the 10,000 free allowance |
|---|---|---|
| about 1 second | 1,000 | a tenth of the allowance |
| about 10 seconds | 10,000 | the whole allowance, nothing to pay |
| about 30 seconds | 30,000 | 20,000 billed seconds, in the first bracket |
The same automation would use 4,000 tasks on Zapier (four actions per run) and 1,000 executions on n8n. Here, it all depends on what the steps do. The vendor says so itself: two scenarios with the same number of executions can cost different amounts, because waiting on slow APIs, large files or the headless browser lengthens billed time.
Two details from the documentation: running a single node on the canvas uses nothing, and a nested scenario is only counted within the main scenario’s time. In the run history, the “Duration” column (elapsed time) and the “CPU seconds” column (billed time) are not equal (Latenode documentation, FAQ on the billing unit (accessed )).
To place this unit next to other tools’ tasks, credits and executions, see the guide to billing units.
The plans at a glance
| Plan | Monthly price | Monthly price, billed annually | Monthly quota included | Limits |
|---|---|---|---|---|
| Freesource | $0 | not recorded | 10,000CPU seconds | 5 active scenarios, 1 parallel execution, 3 minutes per execution, 3-day history. 10-minute interval, 10 connected accounts, 16 MB files. |
| Pay as you gosource | $0 | not recorded | 10,000CPU seconds | No base subscription ("No base fee"): 10,000 free "CPU seconds" every month, then per-second billing in decreasing brackets. Unlimited active scenarios, 5 parallel executions, 10 minutes per execution, 30-day history, 10-minute interval, unlimited connected accounts, 16 MB files. Execution time (up to 60 minutes), interval (5 minutes or 1 minute) and file size (up to 1,024 MB) can be extended with paid add-ons. |
Just two plans, with no base subscription:
- Free: 10,000 CPU seconds per month, 5 active scenarios, one execution at a time, up to 3 minutes per execution, 3-day history. No credit card.
- Pay as you go: the same 10,000 free seconds every month, then per-second billing in decreasing brackets (the scale is in the box above). Unlimited active scenarios, 5 parallel executions, 10 minutes per execution, 30-day history.
No trial of a paid plan is mentioned: you move from Free to “Pay as you go” by adding a payment method. Paid monthly add-ons extend the maximum time per execution (up to 60 minutes), shorten the trigger interval or raise the file size limit; their prices are in the notes at the bottom of this page.
A monthly spending cap can be set in the account: once it is reached, new executions fail before they start. The tier table further down repeats the vendor’s own volume examples; the cost calculator compares those volumes with other tools.
Hosting and data
On where the service runs, the list of subprocessors says: Hosting on Microsoft Azure and Amazon Web Services, both listed as "US" in the list of subprocessors source. The pages we read mention neither a choice of EU region nor self-hosting: both points stay “not recorded”, which doesn’t mean they don’t exist.
The documentation states that the database is encrypted at rest, customer instances are logically isolated and audit logs are kept for at least three months (Latenode documentation, customer data protection and encryption (accessed )).
AI and agents
"AI Agent" node; models used without an API key are billed in "PnP tokens" (1 token = $1), on top of "CPU seconds" source. Tokens are charged at the model provider’s actual usage, plus a margin, on top of CPU seconds. The coding helper, “AI Code Copilot”, is listed as “Trial access” on Free and “Pay per use” on “Pay as you go”.
What the pages don’t say, or say twice
- Invites. The vendor’s pages contradict each other: for “Pay as you go”, the pricing page says you can invite teammates to workspaces, while the billing documentation counts a single workspace invite.
- What happens when the free allowance runs out on the Free plan, short of moving to “Pay as you go”: not recorded.
- Interface languages: not recorded.
Alternatives worth a look
- The closest head-to-head: Latenode vs n8n, two tools that accept code, one billed by the second, the other by the execution and installable on your own server.
- For a unit that is easier to forecast: Activepieces (one credit per run) or n8n.
- The wider picture: workflow automation tools compared, Zapier alternatives and n8n alternatives.
Plans and pricing
| Plan | Monthly volume (CPU seconds) | Monthly price | Monthly price, billed annually |
|---|---|---|---|
| Free | 10,000 | $0 | not recorded |
| Pay as you go | 100,000 | $10.80 | not recorded |
| Pay as you go | 500,000 | $48.80 | not recorded |
| Pay as you go | 1,000,000 | $83.80 | not recorded |
Recorded features
| Criterion | LatenodeAutomation tool |
|---|---|
| Data residency | Hosting on Microsoft Azure and Amazon Web Services, both listed as "US" in the list of subprocessorssource |
| Integrations | "5,500+ Integrations"; the "About" page also says "1,200+ apps and LLMs in one plan"source |
| AI features | "AI Agent" node; models used without an API key are billed in "PnP tokens" (1 token = $1), on top of "CPU seconds"source |
| Minimum interval | 10 minutes (scheduled or polling triggers); 5 or 1 minute as a paid add-on; instant webhookssource |
| Active workflows | 5 active scenarios (Free); unlimited on "Pay as you go"source |
| Code step | JavaScript node ("Full-Code Node") included in both plans, including Freesource |
Alternatives compared
| Criterion | LatenodeAutomation tool | n8nAutomation tool | MakeAutomation tool | ActivepiecesAutomation tool | ZapierAutomation tool |
|---|---|---|---|---|---|
| Lowest paid plan | not recorded | €24 per monthStartersource | $16 per monthCoresource | $20 per monthPlussource | $29.99 per monthProfessionalsource |
| Free plan | 10,000 CPU seconds per monthsource | Nosource | 1,000 credits per monthsource | 1,000 credits per monthsource | 100 tasks per monthsource |
| Billing unit | CPU secondssource | executionssource | creditssource | creditssource | taskssource |
| Self-hosting | not recorded | Yes: free Community edition, no license key; paid self-hosted plans Business and Enterprisesource | No: no self-hosted plan on the pricing page; AWS hosting (EU, North America) for every plansource | Yes: free Community Edition with no credits; every plan on the pricing page is also available self-hostedsource | No: no self-hosted plan; the vendor hosts data on AWS servers in the United Statessource |
| License | not recorded | Sustainable Use License 1.0 ("fair-code"); ".ee." files under the n8n Enterprise Licensesource | not recorded | MIT ("MIT Expat") for the core; commercial license for the Enterprise edition folderssource | not recorded |
| Data residency | Hosting on Microsoft Azure and Amazon Web Services, both listed as "US" in the list of subprocessorssource | Hosted plans: EU, servers in Frankfurt (Germany); self-hosted: wherever n8n is installedsource | Data center in the US or the EU, chosen when the organization is created and not changeable afterwardssource | Cloud hosted in the EU, in Frankfurt by default; another region on request; self-hosting in the region of your choicesource | AWS servers in the United States; no EU-only storage option ("Zapier does not support this option")source |
| Integrations | "5,500+ Integrations"; the "About" page also says "1,200+ apps and LLMs in one plan"source | "500+ native integrations" (home page); "2,000+ integrations" (integrations page, community nodes included)source | More than 1,000 apps according to the pricing FAQ; "3,500+ apps" on the plan cards of the same pagesource | 775 "pieces" and 6,759 actions according to the pieces page; "770+" on the pricing pagesource | More than 9,000 apps ("9,000+ apps"); "premium" apps reserved for paid planssource |
| AI features | "AI Agent" node; models used without an API key are billed in "PnP tokens" (1 token = $1), on top of "CPU seconds"source | AI Agent node included (Cloud and Community); models paid with your own keys or Gateway creditssource | "Make AI Agents" (beta), every plan: 1 credit per operation, plus token-based credits with Make's AI providersource | Agents, Chat and AI Router; AI steps at 2, 10 or 20 credits depending on the model, 1 credit with your own keyssource | AI by Zapier (paid plans): 1, 3 or 5 tasks per step; Agents: separate add-on, counted in "activities"source |
| MCP protocol | not recorded | MCP Server Trigger and MCP Client included in every Cloud plan and in the Community editionsource | "MCP server" included in every plan according to the pricing pagesource | Built-in MCP server; "Free on every plan, cloud or self-hosted" according to the vendorsource | Zapier MCP available on every plan; 2 tasks per successful tool callsource |
| Minimum interval | 10 minutes (scheduled or polling triggers); 5 or 1 minute as a paid add-on; instant webhookssource | not recorded | 15 minutes (Free); 1 minute (Core, Pro, Teams, Enterprise)source | not recorded | 15 minutes (Free); 2 minutes (Professional); 1 minute (Team, Enterprise)source |
| Active workflows | 5 active scenarios (Free); unlimited on "Pay as you go"source | Unlimited active workflows on every plansource | 2 active scenarios (Free); unlimited on paid planssource | Unlimited flows on every plansource | Free: unlimited number of Zaps, limited to two stepssource |
| Code step | JavaScript node ("Full-Code Node") included in both plans, including Freesource | not recorded | "Make Code App": not included in Free; 2 credits per second of execution on paid planssource | not recorded | Code by Zapier: 1 second per step (Free), 30 seconds (Professional, Team), 2 minutes (Enterprise)source |
| Support | not recorded | Forum (Starter, Pro, Business); dedicated support with SLA (Enterprise)source | Free: "90-day expert access to get started"; Enterprise: 24/7 supportsource | Community (Free, Plus); email (Team); dedicated support (Ultimate)source | No email support on Free; email on Professional, chat from the 2,000-task tier; priority support on Teamsource |
| Vendor | Nocode LTDCyprus (headquarters listed as "Remote-first (Cyprus)" on the "About" page)source | n8n GmbHGermanysource | Czechia (headquartered in Prague according to the About page)source | Activepieces Inc.United Statessource | Zapier, Inc.United States (Delaware corporation)source |
| Vendor | Visit Latenode (opens in a new tab) | Visit n8n (opens in a new tab) | Visit Make (opens in a new tab) | Visit Activepieces (opens in a new tab) | Visit Zapier (opens in a new tab) |
Data recorded from the official pages: Latenode (), n8n (), Make (), Activepieces (), Zapier ().
Good to know
- The levels in the grid are the vendor's own examples: 100,000 "CPU seconds" correspond to 100,000 executions of about 1 second or to 10,000 executions of about 10 seconds; 500,000, to 50,000 executions of about 10 seconds; 1,000,000, to 100,000 executions of about 10 seconds. The vendor notes that two scenarios with the same number of executions can cost different amounts: waiting for slow APIs, large files or the headless browser lengthen the billed time. source
- Adjustable monthly spending cap: once it is reached, new executions fail before starting. Optional extras ("add-ons") are priced per month and charged per day (one thirtieth per day). If unpaid invoices exceed $2, the subscription is canceled and the account goes back to Free. source
- Paid add-ons for "Pay as you go", per month. Polling interval: 5 minutes, $5; 1 minute, $10. Maximum time per execution: 20 minutes, $10; 40 minutes, $20; 60 minutes, $30. File size per execution: 32 MB, $5; 128 MB, $10; 256 MB, $20; 512 MB, $50; 1,024 MB, $70. "Reserved Execution Workers": $10 per worker. "High-Volume Events Filtering": $20. Extra RAG storage: $10 per storage. source
- The vendor's pages contradict each other: for "Pay as you go", the pricing page (https://latenode.com/pricing-plans) says "Invite teammates to workspaces", while the billing documentation (https://documentation.latenode.com/account-management/billing-page-and-managing-subscription) says "1 workspace invite". source
- AI: "PnP tokens" are charged according to the model provider's actual usage (the provider's rate plus a small margin), on top of "CPU seconds"; the scenario-building assistant also spends them. "AI Code Copilot": "Trial access" on Free, "Pay per use" on "Pay as you go". A separate spending cap can be set for tokens. source
- Running a single node on the canvas uses nothing. A nested scenario ("Latenode scenario" node) is counted only within the execution time of the main scenario. source
- The headless browser is included in both plans, including Free; the vendor describes it as "Chromium and Puppeteer-style control" (scraping, forms, screenshots). source
- The former monthly plans ("Micro, Starter, Grow, Prime", billed in credits) are archived and remain visible only on legacy accounts. Holders of a one-time-payment plan ("LTD (lifetime deal)") keep their allocation, at 1 credit for 30 "CPU seconds"; no one-time-payment plan is shown on the pricing page. source
Sources
Official pages consulted for Latenode, recorded on November 11, 2026.
- latenode.com/pricing-plans
- latenode.com
- latenode.com/about
- documentation.latenode.com/get-started/frequently-asked-questions/what-is-credits
- documentation.latenode.com/account-management/billing-page-and-managing-subscription
- documentation.latenode.com/legal/subprocessors
- documentation.latenode.com/get-started/frequently-asked-questions/what-is-pnp-nodes
Frequently asked questions
Is Latenode free?
Yes. The Free plan is permanent and needs no credit card: 10,000 CPU seconds per month, 5 active scenarios, one execution at a time and up to 3 minutes per execution. The "Pay as you go" plan keeps those 10,000 free seconds each month and bills the rest by the second.
How does Latenode pricing work?
There is no subscription price. After the month's 10,000 free CPU seconds, each second is billed on a scale of decreasing brackets. The scale and the vendor's volume examples are in the billing-unit box and the tier table on this page, with the date they were recorded.
Does Latenode still use credits?
No. According to the billing documentation, the former monthly credit plans are archived and only remain visible on legacy accounts. The unit is now the CPU second; holders of an old one-time-payment deal keep their allocation at 1 credit for 30 CPU seconds.
Can you self-host Latenode?
That point is not recorded: the pages we read (pricing, billing documentation, subprocessors) don't mention self-hosting and only describe a service hosted by the vendor.