Skip to main content

Data and Access

Isolated by design​

Every customer gets an isolated, sandboxed container and network - not a shared instance with other customers' workflows sitting next to yours. Your database is a separate database and role of its own, never a shared table with anyone else's data.

Hardening enabled by default​

Every instance ships with the following enabled from the start, not as an optional upgrade:

  • N8N_RUNNERS_ENABLED - workflow execution runs in its own isolated process
  • N8N_BLOCK_ENV_ACCESS_IN_NODE - workflows can't read environment variables/secrets outside their own instance
  • N8N_RESTRICT_FILE_ACCESS_TO=/data - filesystem access is confined to your own instance's data directory
  • N8N_BLOCK_FILE_ACCESS_TO_N8N_FILES - workflows can't read n8n's own internal files
  • Community nodes are disabled by default (opt-in only) - third-party nodes aren't silently available to every workflow

SSL and updates​

  • SSL/TLS is configured by default on every instance - HTTPS for webhooks, logins, and day-to-day use, with no manual certificate setup required.
  • The operating system on the server your instance runs on is security-patched by SpliceRun on Shared and Dedicated plans.

If you bring your own server (BYOS)​

The server itself - its operating system, firewall, and your relationship with your provider - stays your responsibility; SpliceRun manages the application layer running on it. We hold an SSH key on your machine so we can manage the app; you can revoke it at any time, and it's removed automatically when you cancel.

Agencies: isolation across multiple client instances​

If you manage automations for multiple clients, each client still gets the exact same isolated, per-tenant instance as any other SpliceRun customer - the Agency add-on gives you one dashboard and one consolidated invoice across all of them, but it does not change the isolation model between clients. See Choosing a hosting option for plan details.

Your data, your control​

  • Your workflows, credentials, and execution history belong to you.
  • We don't read the contents of your workflows. To tell you when an automation breaks, we can read execution metadata - whether a run failed, when, and the workflow's name - but only if you switch that on, and it is off by default. On managed n8n it is enforced by a database login that is denied access to the table your run data lives in. See What our monitoring can see, including the query you can run to check it yourself.
  • You can export everything at any time your account is active. See Backups & Data Recovery for how that works, and Billing, Cancellation, and Data Policy for what happens to your data if you cancel.

Not affiliated with the tools we host​

SpliceRun is an independent hosting provider. We're not an official product, partner, or reseller of n8n or any other tool we host - we run them reliably and are upfront about that rather than implying an official status we don't have.

Questions about security or access? Contact Support.

Published