Various parts of the site hosted with us are stored in different places and you can find here more details about it.
The core files of WordPress are always
read-only as the core should never be altered in any way. In case you need to alter various default behaviors of WordPress, please use hooks and filters. Besides being read-only, the core files are not visible through SFTP or Git for the same reason, they are meant to be read-only. You cand find more details about this on our security page.
The code of your site is stored on our Git stack. Besides themes and plugins, we also store here other folders such as
languages or other folders that might be created by plugins. All changes done on these files, no matter if they're done from SFTP, Git or the WordPress Editor, are stored as Git commits.
In case you need to place a file or folder directly in the root of your site, these files need to be added in the folder
wp-content/root/. The contents of this folder is stored on Git, therefore if you need to place files that are downloaded, or large attachments, then we recommend placing them inside a folder from
wp-content/uploads/. That's the place where static files should stay.
For example, in case you need to verify the domain ownership by placing a file called
verify.html in the root of your site, then you need to copy this file in
wp-content/root/verify.html and it will become available at
example.com/verify.html. Folders work too, but you can't add a folder called root (e.g. example.com/root/file.html).
These files are stored by WordPress in
wp-content/uploads/ and the contents of this folder is stored on our ZFS stack. In short we have two pairs of servers for each cluster, in permanent sync with automatic failover in case the primary one goes down. The files are then mounted over NFS in the corresponding container of your site, on the backend server, where php gets executed and the pages are generated.
More information about our ZFS setup and snapshotting is available on our backup policy page.