Community nodes are not available
If you open Settings → Community nodes in your n8n instance and find that the option is missing, or if you see an error when trying to install a community package, this is expected - community nodes are disabled on SpliceRun.
Why they are disabled
Community nodes are npm packages that run arbitrary code inside your n8n instance. On a multi-tenant host, a malicious or broken package can affect other customers on the same machine. On BYOS and Dedicated, the risk is to your own instance - a package with a supply-chain compromise can read your credentials or disrupt your workflows.
SpliceRun disables community package installation by default to protect customers who are not thinking about this risk when they are trying to install a useful node.
What you can do instead
1. Use the HTTP Request node. If the community node you want is a connector to a third-party API, the HTTP Request node can call that API directly. Most n8n community nodes are thin wrappers over a REST API - the HTTP Request node plus a few expressions does the same thing without needing a package.
2. Use the Code node. If you need custom logic that a community node would
provide, the Code node runs JavaScript directly. It has access to $input, $env,
$node, and the n8n expression helpers.
3. Ask about your specific case. Open a support ticket naming the community node you need and what you are trying to do. If there is a safe way to enable it for your instance without affecting others, or if there is a built-in alternative we can point you to, we will tell you.
The community nodes restriction applies to all SpliceRun plans. It is not something that changes by upgrading to Dedicated or BYOS - the restriction is about the install mechanism, not the hosting model.