Skip to main content
At rest, Project files live in a durable object storage system, the Domino Blob Store. Domino natively supports the Domino File Store with the following cloud storage services:
  • Amazon S3
  • Azure File Storage
  • Google Cloud Storage
The Domino File Store can also be backed with a shared Kubernetes Persistent Volume from a compatible storage class. You can provide a Network File System (NFS) storage service, and the Domino installation utilities can deploy the nfs-client-provisioner and configure a compatible storage class backed by the NFS system.

​
Encrypted Project files

Domino supports server-side encryption with customer-provided keys (SSE-C) for Amazon S3, and EBS file system encryption using the industry-standard AES-256 algorithm on Elastic Block Store. Domino also supports default encryption keys for Amazon S3, Azure File Storage, and Google Cloud Filestore. Domino does not provide pre-write encryption for nfs-client-provisioner volumes.

​
How data is stored in Project files

When a user starts an execution, the files from their Project are fetched from the Domino File Store and loaded into the working directory of the Domino File System. When the execution finishes, or the user starts a manual sync in a Workspace session, any changes to the working directory are written back as a new revision of the Project files. Domino’s versioning system tracks file-level changes and provides rich file difference information between revisions. Any of the following creates a new revision:
  • A user uploads files from the Domino application upload interface.
  • A user authors or edits a file in the Domino web application file editor.
  • A user syncs local files to Domino from the Domino Command Line Interface.
  • A user uploads files to Domino through the Domino API.
  • A user runs code in a Job that writes files to the working directory.
  • A user writes files to the working directory during a Workspace session, then starts a manual sync or commits those files when the session finishes.
Project files are a component of the Domino Reproducibility Engine, so by default Domino keeps every revision indefinitely. Users can always return to and work with past revisions, except for files subjected to a full delete by a system administrator.

​
Access to data in Project files

Users can read and write files in the Projects they create, on which they automatically hold an Owner role. Owners can add collaborators with roles and associated file permissions. See Collaborator permissions for details. Users can also inherit roles from membership in organizations. Some administrative system roles grant additional access to Project files across the deployment they administer. See Roles for more information.

​
Delete every instance of a file

A system administrator can use a full delete to remove all instances of a file’s contents from the Domino File System. It finds the contents across every revision of every Project, erases them, and replaces them with a message you supply. Use it when a file holds data that must be destroyed, for example for compliance reasons.
A full delete irrevocably removes every file matching the exact contents of the file you delete, even where the filenames differ. If several Projects contain a data.txt file with identical contents, full-deleting it in one Project deletes it in all of them. Files that share the filename but not the contents are unaffected.
  1. In the Project that the file belongs to, click Code.
  2. Click the three dots at the end of the file’s row and click Full Delete, or click the file and then click Full Delete.
    You can perform a full delete on one file at a time.
  3. Enter a commit message and confirm. Anyone who later opens the deleted file finds that message in place of the contents.
The operation leaves the revision history of the affected Projects intact: every commit that contained the file contents still exists, and only the contents are replaced.
Domino endpoints published from Project revisions that contained a fully deleted file still carry that file inside their images, and those images cannot be purged. Contact Domino Support if you have questions about such files.
Last modified on September 3, 2026