Nothing for you to patch
Patching is automatic. Every advisory and every upgrade lands on a runtime we run and get audited on.
CVE-2026-1183 patched · 4h
runtime v4.18.2 rolled out
CVE-2026-1179 patched · 11h
your patch tickets 0
For teams running n8n
The patching is yours. The scaling.
And the exposure.
The build already works. What it costs you is the patch queue, a resize every time volume moves, and whatever sits between an advisory landing and your team applying it. On Tray, all three are ours.
Thanks — someone from our team will be in touch soon.
Why teams move to Tray
Everything below is what running it yourself costs instead.
Tray auto-scales with your workloads
Volume climbs and your workloads scale automatically. Nobody sizes workers, Redis or a database.
throughput ↑ 9×
workers sized: auto
One platform. Unified. Managed.
Integration, automation, API management, agents and MCP on one platform Tray patches and scales. One contract, one place to look.
integration automation API mgmt agents MCP
all managed · one contract
Tray produces the evidence
Scoped access, approvals and a record of every run, ready when a reviewer asks. Your team does not assemble it.
run_9f2a11 approved
run_9f2a10 approved
run_9f2a0f held
export · SOC 2 ready
Policy on every agent call
Scope and policy are set on every agent and MCP call, then logged. Not a node somebody remembered to add.
mcp:crm.read allow
mcp:billing.write deny
agent:ticket.create allow
logged · scope set at platform
Only Tray has Helix
Vibe-coded apps go to production on the same platform, with SSO and secrets handled. Real vibe-coding, for integrations and apps.
approvals-app · helix
$ helix deploy approvals-app
SSO wired secrets injected policy inherited
live in production env:prod · 38s
Why enterprises choose Tray
The three costs
What running it yourself actually costs
Not one blocker. Three separate bills, and most teams are paying at least two of them right now without having costed either.
bill 01 unbudgeted
Risk and patching
paid in: engineer-days, per advisory
The advisories keep coming, and every one is your team scheduling, testing and rolling out an upgrade to stay ahead.
bill 02 every week
Operational overhead
paid in: a standing rota slot
Somebody babysits the deployment every week: Redis, Postgres, workers, upgrades, retention. Free covers the software, not the team running it.
bill 03 per spike
Scale and reliability
paid in: architecture projects
Every step up in volume is sizing work somebody does by hand: workers, memory limits, retention, and the spikes in between.
Industry recognized
3× Visionary Gartner Magic Quadrant for iPaaS, 2024, 2025 and 2026 
7× Leader Nucleus Research iPaaS Value Matrix, seven consecutive years Pioneer Gartner Emerging Market Quadrant for No-Code Agent Builders, 2026 14 Hype Cycles Gartner inclusions in 2026, including Agentic AI and Agentic Automation One platform, patched and scaled by us
Tray.ai is the AI orchestration platform. One platform, one contract, and one governance model across all of it.
- Integration and automation across 700+ managed connectors, so the systems you already depend on are first-class steps.
- API management on the same platform, rather than as a separate tool with a separate contract.
- Agents built and run where your integrations already live, not bolted on beside them.
- MCP, with policy on the call itself, so what an agent may reach is a platform decision rather than a per-workflow setting.
- We run the controls, not you: Patching, evidence and scope are Tray’s to carry, not a configuration your team owns.
Your team builds. Tray runs it.
- The advisory clock stops being yours. Tray.ai patches and monitors the platform, so keeping up is not a standing job on your rota.
- The controls are already on. What a review asks for does not sit behind a tier you have to buy at the worst possible moment.
- Volume stops being an architecture project. Sizing, tuning, and the infrastructure underneath are the platform’s job.
- Agents and MCP arrive governed. Scope and policy sit on the call, and every call is a platform record.
- Nothing you built is wasted. Your workflows come across as native Tray workflows.
Audited and certified
The controls are already on
SOC 1
audited annually
SOC 2 Type 2
with penetration testing
HIPAA
PHI handling
GDPR
EU data residency
CCPA
US data residency
700+
connectors managed
across integration, automation, and agents
1T+
processes run per year
on the platform
100%
workflow execution uptime
over the trailing 90 days
US, EU, and APAC data residency · Annual penetration testing · Uptime measured on status.tray.ai and publicly checkable there. As of August 2026.
See the trust centerMoving is not a rebuild
Point the migration kit at your n8n exports. Connectors are mapped with a confidence score on each, expressions are translated, and the build is ordered so callable workflows exist before the workflows that call them. Your flows come across as native Tray workflows, and you can migrate in minutes.
How the migration worksKeep reading
BlogRisk and patchingWhen the next n8n CVE drops, who patches it?BlogOperational overheadWhat it costs to run n8n yourselfBlogScale and reliabilityWhy n8n drops records without an error, and what you own at volumeBlogGovernance and complianceWho owns your SOC 2 report when you self-host n8n?BlogMigrationIntroducing the n8n to Tray migration kit
More on moving from n8n:Risk and patchingOperational overheadScale and reliabilityGovernance and complianceMigration
Contents
01 02
02 04
03 06
04 08
05 10
tray.ai · 12 pages
The guide · 12 pages
Five signs you've outgrown n8n
Five signs, what each one costs, and where your setup stands.
Get the guideWhy enterprises love Tray
“Since implementing Tray, we've quadrupled our integration delivery speed. More integrations mean happier customers that can respond to cybersecurity vulnerabilities even faster.”
Frequently asked questions
What is the best n8n alternative? +
It depends which of the three costs you are actually paying. If it is the security review and the patching hours, that is a question about who operates the platform. If it is the sizing and tuning work at volume, that is a question about architecture. If it is the tier that unlocks the controls you now need, that is a question about what comes standard. Tray.ai is the AI orchestration platform: integration, automation, API management, agents, and MCP on one managed platform, and we run the controls rather than leaving them to your team.
Do I have to start my workflows again from scratch to move? +
No. The migration kit reads your n8n exports and stands them up as native Tray workflows: connectors mapped with a confidence score on each, expressions translated, and the build ordered so callable workflows exist before the workflows that call them. You can migrate in minutes. The tricky parts are flagged up front rather than discovered later.
Is self-hosted n8n free? +
Free Community self-hosted is genuinely unmetered: unlimited executions, no meter, no phone-home. What sits outside it is the controls, which are on a paid tier, and the infrastructure, which is yours to run. The overhead page covers both, with n8n’s own published prices and a retrieval date.
Can n8n handle production volume? +
It runs at volume for plenty of teams, and n8n publishes a figure of 200 executions per second. The part that transfers to you is the sizing work: memory behaviour, queue-mode configuration, execution-data growth, and the remedy for each, all of which are documented and all of which are your team’s to implement.
What does Tray.ai give me that self-hosting does not? +
A platform Tray.ai patches and monitors, so the advisory clock is not yours. We run the controls, not you: the patching, the evidence and the scope are Tray’s, not a checklist your team keeps working. Policy and scope on every agent and MCP call, kept as a platform record. And scale that does not hand you the architecture.
Have you outgrown n8n?
Let's discuss your next step.
Thanks — someone from our team will be in touch soon.
GARTNER is a registered trademark and service mark, HYPE CYCLE and MAGIC QUADRANT are registered trademarks of Gartner, Inc. and/or its affiliates in the U.S. and internationally and are used herein with permission. All rights reserved. Gartner does not endorse any vendor, product or service depicted in its research publications and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner’s Research & Advisory organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.