n8n is not just shipping fast. It is using that shipping pace to move upmarket into enterprise AI orchestration. ToolVitals tracks 49 release events in 30 days, 30 GitHub releases in 90 days, a 100 shipping score, and 187,774 GitHub stars. The recent SAP and Mercedes-Benz posts show what that work is being aimed at: AI workflows that connect visual builders, code, agents, and controlled enterprise deployment.

The SAP news is the sharpest signal. n8n says SAP invested in the company at a $5.2bn valuation and that n8n will be embedded inside SAP Joule Studio on the SAP Business AI Platform. The partnership post says teams will be able to build AI workflows and orchestrate agents from the n8n canvas across SAP and third-party systems, with SAP handling identity, access control, and operations.

That is a different story from generic workflow automation. n8n is positioning itself as the place where deterministic business logic and probabilistic agent behavior meet. The SAP investment post makes that explicit: compliance checks, billing, and data updates need one correct outcome, while ticket triage or anomaly handling may need judgment. n8n wants to host both kinds of work in the same automation layer.

The Mercedes-Benz case study backs up the same bet from another angle. n8n says Mercedes-Benz has rolled it out as a global low-code automation platform across business units, with use cases in customer support, sales, and IT operations. The important part is not the logo. It is the deployment story: self-hosted, cloud-agnostic, and built for teams that need data control.

The product pages line up with that. n8n now markets itself as an AI workflow automation platform for technical teams, with visual workflow building, JavaScript or Python when needed, testing with real data, replay or mock data, logs, native evaluation, Docker deployment, source access on GitHub, and hosted cloud. The release feed shows the less glamorous side of that promise too. The beta release page includes core bug fixes for expression evaluation. That is exactly the sort of plumbing an automation platform has to keep tightening if it wants to run production workflows.

The signal: enterprise AI needs boring control

The interesting part is the mix. ToolVitals gives n8n a 100 health score, a 100 shipping score, and a 94 ToolVitals score. That says the project is alive and moving. The first-party announcements say the motion is not random.

n8n is betting that enterprise AI adoption will not be won by chat widgets alone. It will be won by systems that connect agents to existing business tools, keep audit trails, support self-hosting, and let technical teams drop into code when the visual canvas is not enough.

That is why the SAP embedding matters. If n8n becomes available inside Joule Studio as planned, it gets closer to SAP customers without asking those customers to bolt on yet another external automation service. The SAP post says general availability is expected in Q3 2026, so this is still partly forward-looking. Treat it as positioning plus planned distribution, not proof of shipped SAP-native adoption.

The AI content push also fits. Recent n8n posts cover production AI monitoring, agent architecture patterns, LLM memory, and advanced RAG. That is not casual SEO fluff. It maps to the product thesis: agent workflows need evaluation, memory, retrieval, topology, and failure containment.

What ToolVitals can and cannot infer

ToolVitals can say n8n is highly active by public signals. It has 49 release events in 30 days, 30 GitHub releases in 90 days, 187,774 GitHub stars, and top scores for health and shipping. ToolVitals can also say the company’s first-party narrative is currently centered on AI workflow orchestration for technical and enterprise teams.

ToolVitals cannot prove the workflows are good. It cannot see customer satisfaction, revenue quality, support burden, hosted cloud reliability, or whether the SAP and Mercedes-Benz stories generalize to smaller teams. It also cannot judge code quality from stars and release counts alone.

There is one wording trap here. n8n is fair-code, not OSI-approved open source. The payload says it publishes source and supports self-hosting, but uses the Sustainable Use License, which is not OSI-approved. So call it fair-code or source-available, not open source.

There is also a product-claim mismatch worth handling carefully. The supplied payload describes 400+ integrations, while current first-party pages and posts describe a larger integration library. The safer editorial claim is that n8n has a large integration library and is actively positioning those integrations as part of its AI orchestration story, rather than anchoring the article on one integration count.

Competitor context

n8n is not alone in the high-activity cluster. LangChain also has a 240.0 hot score and a 100 shipping score, with 136,689 GitHub stars and 30 release events in 30 days. That comparison is useful because LangChain is OSI-approved OSS under MIT, while n8n is fair-code. They are both hot, but the governance and product shape are different.

Tracecat is the closer automation comparison. It has 3,598 GitHub stars, a 98 shipping score, and 12 release events in 30 days. Skyvern has 21,604 stars, a 100 shipping score, and 17 release events in 30 days. n8n is much larger by stars and much louder by release events, with 49 in 30 days.

OpenClaw is the outlier by raw stars in this related set, with 371,708 stars, a 100 shipping score, and 38 release events in 30 days. But it sits in developer tools, not automation, so it is less useful as a direct product comparison.

Recommendation

If your team is building internal AI workflows that need human review, API integrations, deterministic steps, and agentic pieces in the same flow, evaluate n8n. The public signals show a tool shipping at serious speed, and the first-party roadmap is clearly aimed at production AI orchestration inside controlled enterprise environments.

If you need an OSI-approved open-source automation stack, do not blur the licensing. Compare n8n’s fair-code model against Tracecat or Skyvern, both tracked here as OSI-approved OSS under AGPL-3.0. The right choice depends less on stars and more on whether your team values n8n’s scale, visual builder, hosted option, and enterprise controls more than OSI-approved licensing.

Sources