Website Isolation & Site Access

Give Developers Access to One Website, Not the Whole Server

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

Three Roles, Three Access Paths

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.

Administrator

  • Manages the host: host SSH settings, keys and 2FA, firewall, runtimes.
  • Decides which user groups may open site SSH. By default, members may open temporary grants for their own sites, and only administrators may make them permanent.
  • Irreversible operations ask for a fresh 2FA code (step-up).

Site maintainer

  • Receives a time-limited SSH / SFTP key for one site.
  • Lands inside that site's sandbox. Other sites and the host system are not visible.
  • Access ends when the grant expires or is revoked.

Customer / member

  • Logs in to the panel with a member account and sees only the sites they own.
  • Works on files through the browser file manager, FTP or a temporary site SSH grant. There is no shell account on the host.
  • A request for another member's resource is refused with the same message as for one that does not exist.
Member view: only the member's own sites are listed, and site SSH is on with its remaining time.
Member view: only the member's own sites are listed, and site SSH is on with its remaining time. Addresses, accounts and domains are redacted.
Grant duration for site SSH: 2, 4, 8, 12 or 24 hours. "Permanent" needs a separately granted permission.
Grant duration for site SSH: 2, 4, 8, 12 or 24 hours. "Permanent" needs a separately granted permission. Addresses, accounts and domains are redacted.

Per-site virtual SSH: Time-Limited and Confined to One Site

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.

  • Key-only login. Nodekeeper generates the key, and the key's password is shown only once.
  • A grant lasts 2, 4, 8, 12 or 24 hours, with one grant per site at a time.
  • The session and SFTP are confined to that site's directory.
  • Revoking a grant ends open sessions.
  • Permanent site SSH is a separate permission. By default only the administrator group has it, and operators can grant it to a group they create for selected customers (custom user groups start at Pro).

Host SSH, 2FA, keys All plans, including Free

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.

Per-site virtual FTP

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.

How Isolation Works: Panel Accounts, Site Users and Processes

Panel account ≠ site runtime user

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.

File permissions and process isolation

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.

Links cannot cross the boundary

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.

Permissions by user group

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.

Limits and prerequisites
  • Isolation keeps sites apart from each other. It does not protect against someone who already has root on the host, and it does not replace patching the host.
  • Sites attached to one shared Apache instance share a runtime user and are no longer separated from each other.

A Maintainer's Workflow

  1. The site owner creates the site, binds the domain and requests a certificate.
  2. The owner opens a site SSH grant (for example 24 hours) and passes the key and its password to the maintainer.
  3. The maintainer works through SSH / SFTP inside the site, or uses FTP.
  4. The grant expires, or the owner revokes it, and open sessions are closed.

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

N Nodekeeper

Manage websites, office PCs and servers from one panel on your own hardware.

Support
support@host.mw WhatsApp: +817093066006

© 2026 Nodekeeper. All rights reserved.