n8n

Open coreWorkflow engine

AI workflow automation platform for technical teams

Homepage Docs Pricing Repository

Scanned 15 Oct 2026 · Schema v5 · features v21

From: €20/mo
Hosted subscription with monthly full-workflow execution allowances; unlimited steps per execution
Free tier: No
No card required.
Isolation: Not disclosed
the public docs do not say
Regions: 1
Frankfurt, Germany — n8n Cloud on Microsoft Azure
Capabilities: 18 / 61
10 partial · 12 fail · 0 not assessed
Agent readiness: 11/11 · 10/11
read · drive, pre-login surface

Advertised for

Workflow automation · AI agents · Data integration · ETL · API orchestration · Scheduled tasks & cron · Webhooks · Rag · Chatbots · Internal tools

Built for

Technical, then developers

· https://n8n.io/ — explicit technical-teams positioning with visual node workflow authoring and code escape hatches.
· https://n8n.io/pricing/ — full-workflow execution pricing and unlimited steps frame business automation, not raw compute.

01 Pricing Hosted subscription with monthly full-workflow execution allowances; unlimited steps per execution

Tier	EntryStarter	Pro	TopEnterprise
Price	€20/month, billed annually	€50/month, billed annually	Custom; contact sales
Includes	2500 executions/month; 5 concurrent; 1 shared project; 1600 Assistant credits/month; unlimited steps	10000 executions/month; 3 shared projects; up to 50 concurrent; up to 9600 Assistant credits/month; history and metric-based evaluations	Custom executions; 200+ concurrent; unlimited projects; external secrets; log streaming; SLA; Cloud or self-hosted

Workflow executions; separate Assistant credits and prepaid Gateway credits·Card required: No·n8n.io

02 Website design Desktop public website · assessed 15 Oct 2026

Complete assessment.

The desktop landing and pricing pages pair a nearly black violet canvas, light rounded sans-serif typography, glowing imagery and gradient calls to action. The docs index switches to a white, navigation-heavy layout with coral links and workflow-diagram thumbnail cards. All three public roles were captured; cookie banners obscure the lower marketing viewports.

Corporate
Technical illustration

Landing page: captured
Pricing: captured
Docs: captured

03 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.

Isolation & lifecycle

Isolation primitive

Not disclosedthe public docs do not say

Persistence

database-backed workflow state

Snapshots / forks

Resources & limits

Storage

Native Data Tables; execution storage; binary-data storage

Limits & quotas

Cloud Starter: 2500 executions/month, 5 concurrent, 5-minute execution maximum; Pro: 10000/month, 20 / up to 50 concurrent, 40-minute maximum; Enterprise: custom executions, 200+ concurrent, displayed 40-minute maximum.

GPU

Access

Deploy interface

dashboardapiclisdkmcptemplate

SDK languages

TypeScriptJavaScript

Network & secrets

Egress controls

Not documented

Secrets

Yes

Bring your own cloud

Placement & use

Jurisdiction

EU; Frankfurt, Germany for hosted plans

Advertised workloads

Workflow automationAI agentsData integrationETLAPI orchestrationScheduled tasks & cronWebhooksRagChatbotsInternal tools

04 Capabilities 18 pass · 10 partial · 12 fail · 61 of 61 assessed

Supported — Documented on the public surface and verified.
Partially supported — Exists with caveats: gated, thin, or enterprise-only.
Not supported — Checked and not offered.
Not assessed — Scanned before this capability was tracked. Not a lack.

Compute & storage 0/4

Persistent diskStorage that survives restart/stop (not ephemeral-only).

Not applicable

Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.

Not supported

Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).

Not supported

Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.

Not applicable

Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.

Not applicable

GPU computeGPU-backed instances available.

Not supported

Multi-regionCompute placeable in more than one geographic region.

Not supported

Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).

Not applicable

Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.

Not applicable

Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.

Not applicable

Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.

Not applicable

Networking & delivery 1/4

Automatic HTTPSTLS endpoints provisioned automatically per workload.

Not applicable

Built-in reverse proxyPlatform routes external traffic to workload services.

Not applicable

Custom domainsBring-your-own domain via CNAME/DNS.

Not applicable

Public preview URLsShareable per-deploy / per-branch URLs.

Not supported

Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.

Not applicable

Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).

Partially supported

Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.

Not supported

Email send / receiveSend and/or receive email from the workload.

Supported

Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.

Not applicable

Developer access 5/6

Public APIDocumented programmatic API.

Supported

OpenAPI specMachine-readable OpenAPI / Swagger spec published.

Supported

CLIOfficial command-line tool.

Supported

SDKOfficial client library/libraries.

Supported

SSH accessDirect SSH into workloads.

Not applicable

Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.

Not applicable

Git deployDeploy from a Git repo / push-to-deploy.

Partially supported

Private container registryHosted private image registry.

Not applicable

E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).

Not applicable

HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.

Supported

AI & agents 4/11

Built-in coding agentShips a first-party AI coding agent in the product.

Partially supported

Agent skillsInstallable / declarable agent skills or tools.

Supported

AI app builderPrompt-to-app / vibe-coding generation surface.

Partially supported

MCP serverExposes a Model Context Protocol server for agents.

Supported

MCP clientActs as an MCP client / consumes MCP tools.

Supported

MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).

Partially supported

LLM gatewayRoutes LLM API calls through the platform (multi-provider).

Partially supported

BYOK for LLMsBring-your-own LLM provider keys.

Supported

Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.

Not supported

Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).

Not supported

Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).

Not supported

Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).

Not applicable

Data 0/2

First-party databasePlatform-provided managed database.

Partially supported

Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.

Not applicable

Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.

Partially supported

Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.

Not applicable

Platform & operations 4/5

Scheduled tasksCron / scheduled job primitive.

Supported

Durable workflowsDurable execution / long-running workflow primitive.

Supported

Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).

Not supported

Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).

Supported

Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.

Not applicable

Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).

Supported

Organisation & security 4/8

Built-in authPlatform-provided authentication / IAM for workloads.

Partially supported

SSO / SAMLEnterprise single sign-on.

Partially supported

Secrets managementFirst-class secrets storage / injection.

Supported

TeamsMulti-user team accounts.

Supported

SharingShare a running workload/resource via link (optionally gated).

Supported

BYOCRuns inside the customer's own cloud account.

Not supported

Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).

Not applicable

Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).

Not supported

Self-host / OSS coreOpen-source core that can be self-hosted.

Supported

Proposed, not verified

Capabilities the scan saw but the registry does not track yet. A key is admitted only once two distinct products exhibit it. These are not scored.

Visual node-graph workflow authoring with code escape hatchvisual-workflow-builder
“Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.” github.com
AI workflow evaluationsai-evaluations
“Use n8n evaluations to build reliable AI workflows. Build confidence in your LLM-powered workflows by comparing the output from known test cases.” docs.n8n.io
Prebuilt app/node integration catalogueintegration-catalog
“400+ integrations.” github.com

05 Agent readiness Pre-login surface · counts, not a grade

Can an agent read it?

parse-ability · docs, metadata, machine-readable surfaces

11/11

8 full · 3 partial · 100% of applicable checks

llms.txt
Supported
“https://docs.n8n.io/llms.txt — HTTP 200 substantive documentation index; apex llms.txt is a much smaller reports-only index. Docs location earns full under rubric v3.”
llms-full.txt
Supported
“https://docs.n8n.io/llms-full.txt — HTTP 200, 8135957-byte root plus all 13 advertised /1–/13 modular continuations fetched. Bounded first-25-line pointer artifacts preserve URLs, HTTP metadata, sizes and excerpts rather than multi-MB source bodies. Apex /llms-full.txt 404 is not the scored docs endpoint.”
robots.txt AI policy
Partially supported
“https://n8n.io/robots.txt — wildcard default-allow, sitemap advertised; no explicit AI crawler directives. Half credit under rubric v3, not a block.”
JSON-LD
Partially supported
“https://n8n.io/ — Organization JSON-LD with name, legalName, logo and sameAs; no rich SoftwareApplication/Product with offers.”
Sitemap
Supported
“https://n8n.io/sitemap.xml — HTTP 200 nontrivial sitemap index with pages, integrations, workflows, creators and cross-integration shards.”
Meta tags
Supported
“https://n8n.io/ — descriptive title AI Workflow Automation Platform - n8n, description and OG metadata in retained response metadata.”
Markdown negotiation
Supported
“https://docs.n8n.io/ — Accept: text/markdown returns HTTP 200 text/markdown; charset=utf-8, 4967 bytes, Vary includes Accept. Apex still returns HTML; documentation content negotiation independently satisfies rubric v3.”
Content efficiency
Partially supported
“https://n8n.io/ — 7828 readable-text bytes / 353362 original HTML bytes = 2.215%; rubric 1–5% band is half, not full.”
Docs discoverable
Supported
“https://n8n.io/ — Documentation and self-host links are first-class navigation links in fetched HTML metadata.”
Machine-readable pricing
Supported
“https://n8n.io/pricing/ — parseable Starter/Pro/Business/Enterprise comparison; hosted-scoped replacement excludes self-host-only Business/Community.”
No anti-bot wall
Supported
“Landing/pricing/docs/legal/API/llms sources fetched without an anti-bot challenge. Trust Center initially returned a JS shell, then rendered successfully via foxcrawl; no persistent public access block.”

Can an agent drive it?

act-ability · APIs, SDKs, MCP, credentials, webhooks

10/11

8 full · 2 partial · 91% of applicable checks

Public API
Supported
“https://docs.n8n.io/api/ — documented public REST API; auth page states Cloud API unavailable during free trial.”
OpenAPI spec
Supported
“https://internal.users.n8n.cloud/api/v1/openapi.yml — HTTP 200; OpenAPI 3.0.0, API info version 1.1.1; bounded source and exact response/error excerpts retained.”
MCP server
Supported
“https://docs.n8n.io/connect/connect-to-n8n-mcp-server.md — instance control/authoring endpoint https://<your-n8n-domain>/mcp-server/http, documented OAuth/personal-token auth; well-known apex 404 does not negate this.”
SDK packages
Partially supported
“https://registry.npmjs.org/@n8n%2fworkflow-sdk/latest — official @n8n/workflow-sdk 0.36.3, TypeScript/JavaScript SDK family; one ecosystem, not multiple official language SDKs. Python Code node is not a Python SDK.”
Auth documented
Supported
“https://docs.n8n.io/connect/n8n-api/authentication.md — Settings > n8n API > Create an API key; expiration, Enterprise scopes; X-N8N-API-KEY request examples. MCP OAuth and token auth also documented.”
Self-serve credentials
Partially supported
“https://docs.n8n.io/connect/n8n-api/authentication.md — key issuance starts with Log in to n8n and dashboard actions; no unauthenticated programmatic bootstrap documented. No signup was attempted.”
Webhooks
Supported
“https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.webhook.md — webhook methods/auth documented; https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.stripetrigger.md documents HMAC-SHA256 X-Hook-Signature validation and 401 for missing/invalid signatures.”
CLI tool
Supported
“https://docs.n8n.io/connect/n8n-cli.md — official API client CLI, distinct from self-host server admin CLI; handles workflows, executions, credentials and projects.”
Error model
Supported
“https://internal.users.n8n.cloud/api/v1/openapi.yml — components.schemas.error is an object with required message:string and optional code:string/description:string, referenced by JSON error responses. Exact error/data schema excerpts retained.”
Rate limits documented
Not supported
“No n8n REST API request-limit/header contract found in fetched public API/auth documentation or full OpenAPI. No 429 response or Retry-After/X-RateLimit header definition found in that spec. Third-party integration rate-limit guidance is not the n8n REST API limit contract.”
Agent config files
Supported
“https://github.com/n8n-io/n8n/blob/master/AGENTS.md plus https://github.com/n8n-io/skills — multiple substantive first-party surfaces: repository agent guidance and installable 13-skill plugins. Apex agents.md/.well-known/agent 404s are genuine negatives, not evidence that all agent config is absent.”

06 Coding harnesses Which agents and IDEs are documented to run here

Advertised integrations 6

Claude Code Anthropic
Supported
“claude mcp add --transport http n8n https://<your-n8n-domain>/mcp-server/http”
Source docs.n8n.io
Documented external MCP client, not a coding harness hosted inside n8n.
Codex CLI OpenAI
Supported
“codex mcp add n8n --url "https://<your-n8n-domain>/mcp-server/http"”
Source docs.n8n.io
Documented external MCP client, not a coding harness hosted inside n8n.
Gemini CLI Google
Supported
“gemini mcp add --transport http n8n https://<your-n8n-domain>/mcp-server/http”
Source docs.n8n.io
Documented external MCP client, not a coding harness hosted inside n8n.
Cursor Anysphere
Supported
“In the Connect a client dialog, select Cursor from Your client, then select One-click setup.”
Source docs.n8n.io
Documented external MCP client, not a coding harness hosted inside n8n.
Windsurf Codeium
Supported
“Add the following entry to your ~/.codeium/windsurf/mcp_config.json file.”
Source docs.n8n.io
Documented external MCP client, not a coding harness hosted inside n8n.
OpenCode opencode
Supported
“OpenCode fetches and installs the plugin, which registers the n8n skills and fires the bash hooks after n8n MCP tool calls.”
Source github.com
Official n8n skills supports OpenCode CLI and Desktop; no harness-registry edit needed.

Plausible compatibility 0

Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.

No general shell access documented, so nothing is derived. Absence is not unsupported.

07 Compliance & regions Standards held, with ordinal rigor; never a score

Certifications held 3

SOC 2 Type II
certifiedhostedRendered public held-compliance list; report access gated. Vendor-published attainment, not an independently reviewed audit. Does not cover customer self-hosted infrastructure.
“SOC 2 Type 2”
Source trust.n8n.ioConfidence: high
SOC 3
certifiedhostedRendered held-compliance and Reports sections; no customer self-host coverage implied.
“SOC 3”
Source trust.n8n.ioConfidence: high
GDPR
self-attestedhostedVendor GDPR claim, not an independently issued certification.
“GDPR”
Source trust.n8n.ioConfidence: high

Regions 1

Frankfurt, Germany — n8n Cloud on Microsoft AzureEU (Frankfurt)

Pricing FAQ explicitly says hosted-plan data resides on Frankfurt servers in the EU; security identifies Azure. No additional selectable Cloud region disclosed. Operator-chosen self-host placement is not Cloud multi-region capability.

Legal

Privacy notice Terms of service

08 Open source NOASSERTION · fetched by machine, not quoted from marketing

Licence & repository

Licence: NOASSERTION
Primary language: TypeScript
Stars: 207,400
Forks: 61,118
Created: 22 Jun 2019
Archived: No

Activity

Last commit: 14 Oct 2026
Latest release: [email protected] · 14 Oct 2026
Issues open / closed: 351 / 10159 · 97% closed

Newest by creation time: [email protected] maintenance, 2026-10-14. Current 2.x stable: [email protected], 2026-10-14; [email protected] is beta/prerelease. Eight fetched rows span Oct 12–14: four stable versioned packages, two beta packages and rolling stable/beta aliases. Do not confuse the newest maintenance release with current stable 2.x.

Fetched via gh on 15 Oct 2026.

Self-hosting

Methods: dockercomposepackage-manager
You operate: —

Community Edition has no license charge for permitted internal-business, personal and non-commercial use, plus operator infrastructure. Sustainable Use License restricts commercial redistribution/hosting and is not OSI open source. Default single-instance storage uses bundled SQLite; PostgreSQL is supported; scalable queue mode requires Redis and PostgreSQL. External services are conditional rather than universal dependencies. Docker/Compose and npm install are documented. Business is self-host-only (€667/month annual billing for 40K executions); Enterprise can be Cloud or self-hosted. Community excludes SSO, source control/environments, external secrets, log streaming and multi-main. Gateway credits are Cloud Starter/Pro only; Assistant self-host uses separately configured provider access. Self-hostability is not vendor-managed BYOC.

Documentation signals 8/8

SupportedQuickstart
SupportedAPI reference
SupportedSelf-host guide
SupportedChangelog
SupportedExamples
SupportedOpenAPI
Supportedllms.txt
SupportedArchitecture doc

09 Company & presence Facts only, not scored

Company

Headquarters: Berlin, Germany
Founded: 2019
Team size: Not disclosed
Hiring: actively hiring

Funding

2020-03Seed · $1500000
2021-04Series A · $12000000
2025-03Series B · $60000000
2025-10Series C · $180000000
2026-05Strategic investment

Notable people

Jan Oberhauser (Founder and CEO)

Activity

Last release: 2026-10-14: [email protected] maintenance; [email protected] current stable; [email protected] beta github.com
Last blog post: 2026-10-13 — Build n8n workflows with Gemini 4 blog.n8n.io

Presence 7

Links found on the public surface scanned; not an exhaustive search.

10 Sources & method How this entry was produced

Public surface only

Everything here was read from n8n.io's unauthenticated pages, docs, pricing and repository on 15 Oct 2026. Nothing behind a login was used.

Statuses, not scores

Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.

Confidence is separate

Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.

Schema: scan v5
Features registry: v21
Keys tracked today: 61
Assessed on this entry: 61

Something wrong on this page?

Nearby in the atlas

All Workflow engine products →