Back to Home

Security & Trust at N8nPort

Last updated August 5, 2026

Security & Trust at N8nPort

Page: /security

N8nPort provides managed n8n workspaces for teams and individuals running real business automation. Here's exactly how we handle your data, credentials, and infrastructure.

Your third-party credentials never leave your workspace

When you connect a service to a workflow — Google, Slack, OpenAI, a CRM, SMTP, or anything else — you enter that credential directly inside your own n8n workspace, using n8n's built-in credential manager. N8nPort does not ask for, collect, view, or store your third-party API keys or OAuth tokens as part of onboarding or support. Our support team will never ask you to send credentials by email, chat, or screenshot.

How your workspace is isolated

Each customer receives a dedicated, isolated n8n runtime with its own allocated CPU, memory, and swap resources — your workspace does not share a runtime process with other customers.

Encrypted access

Every managed workspace is served exclusively over HTTPS. Access to your n8n editor goes through secure single sign-on from your N8nPort account, so you don't manage a separate n8n password.

Backups

We run automated backups of your full workspace data directory, including your workflow definitions and n8n's internal database, on a scheduled basis. Backups are retained on a rolling window so you can request a restore to a recent recovery point if something goes wrong. Backup restore actions are logged.

Runtime health monitoring

Your workspace is monitored on a recurring schedule to detect downtime or instability. If your workspace becomes unhealthy, our team is alerted so we can investigate and, where the issue is on our side, resolve it.

Infrastructure

N8nPort's public-facing traffic is protected by Cloudflare (DDoS mitigation, TLS termination, bot management). Underlying compute runs on managed infrastructure with restricted operator access.

What we can see, and what we can't

We can see: account and billing information, workspace resource usage and health metrics, and — only if you explicitly grant support access for troubleshooting — the contents of a specific workflow you ask us to look at.

We cannot see, by default: the third-party API keys or credentials stored inside your workspace's credential manager, or the data flowing through your workflow executions, unless you choose to share it with us for support purposes.

Reporting a security issue

If you believe you've found a security vulnerability in N8nPort, please report it to [email protected] rather than filing a public issue. We aim to acknowledge reports within [X] business days.

Data protection

For details on how we collect, use, and protect personal data, see our Privacy Policy.

Where we are today

N8nPort is a small, focused team. We don't hold formal third-party security certifications today, and we won't claim any we don't have. What we do have is described above in plain terms: workspace isolation, HTTPS-only access, automated backups, health monitoring, and a strict policy of never handling your third-party credentials. As the company grows, we'll pursue formal audits where they add real value — and this page will be updated to reflect that, not the other way around.