Website Isolation & Site Access
Website isolation keeps each site running on its own, and per-site SSH, SFTP and FTP let a maintainer enter only the site they are responsible for. Nodekeeper keeps site access separate from host administration, and permissions are granted by user group: only users who hold the permission can open site SSH, upload files or read logs.
All plans, including Free Site isolation and site SSH / FTP are included in every plan. Custom user groups, roles and delegated administration start at Pro.
On this page: Three roles · Site SSH and SFTP · How isolation works · A maintainer's workflow
Whoever runs the server, whoever maintains a site and whoever only sees their own sites each take a separate path, and none can cross into another.


Site SSH is served by a separate Nodekeeper SSH service, not by the host's own sshd. A site SSH account is a virtual access mechanism that Nodekeeper manages. It is not a virtual machine, a container or a separate kernel.
Host access stays with the administrator. In the panel you configure the host's SSH service, authorised keys and two-factor authentication. These settings are separate from site grants: giving someone site SSH never adds them to the host's SSH configuration.
Each site's FTP service runs as that site's user, so it reaches only that site's files. The password is shown once, when it is created or reset. After a reset, restart that site's FTP instance so the new password takes effect.
A member logs in to the panel with a panel account. Each site's code runs as that site's own system user and group, which no other site shares. One panel account is not one mailbox, database or site user.
The site root is owned by root, so a site cannot open its own boundary even if it sets its files to 0777. PHP-FPM gets one pool per site, and Apache (mod_php) gets one instance per site by default. A site's runtime logs can be read only by that site's user and root.
Archives extracted or restored in the panel never produce symbolic or hard links. Such entries, ../ paths and absolute paths are skipped and listed. nginx does not follow a link that points to files owned by another user.
Every permission can be configured per user group, and each request also checks who owns the resource. Member accounts come with every plan. User groups, roles and delegation (Multi-user and permissions) start at Pro.
To see these steps on screen, open the visual guide to secure hosting and site access. Once the site is running, see how self-hosted website analytics show what visitors do.
Related guides: How to give developers SSH access to one website
Manage websites, office PCs and servers from one panel on your own hardware.