zeropsio · tikinang · Sep 1, 2026 · Aug 27, 2026
diff --git a/apps/docs/content/alpine/how-to/create.mdx b/apps/docs/content/alpine/how-to/create.mdx
@@ -161,7 +161,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb"
 S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ"
 ```
 
-The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
+The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
 
 #### Description of description.yaml parameters
 

diff --git a/apps/docs/content/alpine/how-to/customize-runtime.mdx b/apps/docs/content/alpine/how-to/customize-runtime.mdx
@@ -90,7 +90,7 @@ Zerops caches custom runtime images to optimize deployment times. Learn about [c
 For information about managing builds and deployments, see [managing builds and deployments](/features/pipeline#manage-builds-and-deployments).
 
 :::warning
-Shared storage mounts and Local Storage volumes are not available during the runtime prepare phase.
+Local Storage volumes are not available during the runtime prepare phase, and start commands (such as a SeaweedFS mount) do not run there.
 :::
 
 ## Troubleshooting

diff --git a/apps/docs/content/alpine/how-to/shared-storage.mdx b/apps/docs/content/alpine/how-to/shared-storage.mdx
diff --git a/apps/docs/content/bun/how-to/create.mdx b/apps/docs/content/bun/how-to/create.mdx
@@ -165,7 +165,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb"
 S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ"
 ```
 
-The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
+The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
 
 #### Description of description.yaml parameters
 

diff --git a/apps/docs/content/bun/how-to/shared-storage.mdx b/apps/docs/content/bun/how-to/shared-storage.mdx
diff --git a/apps/docs/content/deno/how-to/create.mdx b/apps/docs/content/deno/how-to/create.mdx
@@ -160,7 +160,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb"
 S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ"
 ```
 
-The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
+The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
 
 #### Description of description.yaml parameters
 

diff --git a/apps/docs/content/deno/how-to/customize-runtime.mdx b/apps/docs/content/deno/how-to/customize-runtime.mdx
@@ -75,7 +75,7 @@ Zerops caches custom runtime images to optimize deployment times. Learn about [c
 For information about managing builds and deployments, see [managing builds and deployments](/features/pipeline#manage-builds-and-deployments).
 
 :::warning
-Shared storage mounts and Local Storage volumes are not available during the runtime prepare phase.
+Local Storage volumes are not available during the runtime prepare phase, and start commands (such as a SeaweedFS mount) do not run there.
 :::
 
 ## Troubleshooting

diff --git a/apps/docs/content/deno/how-to/shared-storage.mdx b/apps/docs/content/deno/how-to/shared-storage.mdx
diff --git a/apps/docs/content/dotnet/how-to/create.mdx b/apps/docs/content/dotnet/how-to/create.mdx
@@ -161,7 +161,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb"
 S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ"
 ```
 
-The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
+The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
 
 #### Description of description.yaml parameters
 

diff --git a/apps/docs/content/dotnet/how-to/shared-storage.mdx b/apps/docs/content/dotnet/how-to/shared-storage.mdx
diff --git a/apps/docs/content/elixir/how-to/create.mdx b/apps/docs/content/elixir/how-to/create.mdx
@@ -160,7 +160,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb"
 S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ"
 ```
 
-The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
+The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
 
 #### Description of description.yaml parameters
 

diff --git a/apps/docs/content/elixir/how-to/shared-storage.mdx b/apps/docs/content/elixir/how-to/shared-storage.mdx
diff --git a/apps/docs/content/features/backup.mdx b/apps/docs/content/features/backup.mdx
@@ -7,7 +7,7 @@ Zerops provides an automated, secure backup system for supported services. This
 
 ## Supported Services
 
-Zerops provides automated backup functionality for the following services. For specific backup format details and restore instructions, visit each service's documentation: [MariaDB](/mariadb/how-to/backup), [PostgreSQL](/postgresql/how-to/manage#backups), [Qdrant](/qdrant/overview), [Elasticsearch](/elasticsearch/overview), [NATS](/nats/overview), [Meilisearch](/meilisearch/overview), [Local Storage](/local-storage/how-to/manage#backups), and [Shared Storage](/shared-storage/how-to/manage#backups).
+Zerops provides automated backup functionality for the following services. For specific backup format details and restore instructions, visit each service's documentation: [MariaDB](/mariadb/how-to/backup), [PostgreSQL](/postgresql/how-to/manage#backups), [Qdrant](/qdrant/overview), [Elasticsearch](/elasticsearch/overview), [NATS](/nats/overview), [Meilisearch](/meilisearch/overview), [Local Storage](/local-storage/how-to/manage#backups), and [SeaweedFS](/seaweedfs/overview#backup-and-recovery).
 
 ## Managing Backups in the UI
 

diff --git a/apps/docs/content/features/coding-agents.mdx b/apps/docs/content/features/coding-agents.mdx
@@ -54,7 +54,7 @@ ZCP supports multiple coding agents including Claude Code (Anthropic), Codex (Op
 
 ### An ordinary Zerops project underneath
 
-The agent operates inside a normal Zerops project — same shape as production. Managed databases (PostgreSQL, MariaDB, ClickHouse), key-value stores (KeyDB, Valkey), search (Elasticsearch, Meilisearch, Typesense), vector store (Qdrant), message queues (NATS, Kafka), object, local and shared storage, managed Nginx — all on a private network, addressable by hostname. The same pipeline that deploys here can deploy to a separate HA production project with no `zcp` service attached. Not a sandbox the work outgrows.
+The agent operates inside a normal Zerops project — same shape as production. Managed databases (PostgreSQL, MariaDB, ClickHouse), key-value stores (KeyDB, Valkey), search (Elasticsearch, Meilisearch, Typesense), vector store (Qdrant), message queues (NATS, Kafka), object storage, Local Storage and SeaweedFS, managed Nginx — all on a private network, addressable by hostname. The same pipeline that deploys here can deploy to a separate HA production project with no `zcp` service attached. Not a sandbox the work outgrows.
 
 ### Human ↔ agent handover
 

diff --git a/apps/docs/content/features/pipeline.mdx b/apps/docs/content/features/pipeline.mdx
@@ -308,7 +308,7 @@ Learn more about building custom runtime images:
 :::warning
 Do not include your application code in the custom runtime image, as your built application code is deployed automatically into fresh containers.
 
-Shared storage mounts and Local Storage volumes are also not available during the runtime prepare phase.
+Local Storage volumes are also not available during the runtime prepare phase, and start commands (such as a SeaweedFS mount) do not run there.
 :::
 
 ## Deploy phase

diff --git a/apps/docs/content/features/scaling.mdx b/apps/docs/content/features/scaling.mdx
@@ -22,7 +22,7 @@ Unlike traditional hosting where resources must be predicted and pre-provisioned
 Zerops uses two fundamentally different approaches for optimizing infrastructure:
 
 #### **Resource Management (Vertical Scaling)**
-- **Applies to:** Runtime services, databases, local and shared storage, and Linux containers (Alpine and Ubuntu)
+- **Applies to:** Runtime services, databases, Local Storage and SeaweedFS, and Linux containers (Alpine and Ubuntu)
 - **What it does:** Adjusts CPU, RAM, and disk resources within individual containers
 - **Management:** Automated by Zerops, but customizable by users
 
@@ -37,7 +37,7 @@ Docker services do not support automatic vertical scaling. Resource values can b
   - Container/VM creation limits can be controlled
   - Docker containers run in VMs rather than native containers
 
-- **For Databases & Shared Storage:** High Availability Mode (fixed container count)
+- **For Databases & SeaweedFS:** High Availability Mode (fixed container count)
   - Single Container OR Multi-Container HA configuration
   - Must be chosen at service creation (cannot be changed later)
   - Managed by Zerops (no application changes needed)
@@ -51,7 +51,7 @@ Docker services do not support automatic vertical scaling. Resource values can b
       <th className="">Feature</th>
       <th className="">Runtime Services & Linux Containers</th>
       <th className="">Databases</th>
-      <th className="">Shared Storage</th>
+      <th className="">SeaweedFS</th>
       <th className="">Docker</th>
     </tr>
   </thead>
@@ -88,15 +88,15 @@ You can configure scaling settings at three different stages:
 
 - **During import** - Use YAML configuration files to define comprehensive scaling settings including `verticalAutoscaling` parameters and horizontal scaling limits. See [Import & Export YAML Configuration](/references/import) for complete syntax.
 
-- **After service creation** - Modify most scaling settings anytime through your service's **Automatic scaling configuration** page. Note that some parameters like deployment mode for databases and shared storage cannot be changed after creation.
+- **After service creation** - Modify most scaling settings anytime through your service's **Automatic scaling configuration** page. Note that some parameters like deployment mode for databases and SeaweedFS cannot be changed after creation.
 
 This flexibility lets you plan scaling strategies upfront or adapt them as requirements evolve.
 
 ## Part 1: Resource Management
 
 Resource management in Zerops focuses on efficiently allocating and adjusting CPU, RAM, and disk resources within individual containers based on actual usage patterns.
 
-These resource management capabilities apply to **runtime** services, **databases**, **shared storage**, and **Linux containers** (Alpine and Ubuntu).
+These resource management capabilities apply to **runtime** services, **databases**, **SeaweedFS**, and **Linux containers** (Alpine and Ubuntu).
 
 :::note
 Docker services do not support automatic vertical scaling. Resources for Docker services are fixed at the values set manually and do not automatically adjust based on usage.
@@ -275,7 +275,7 @@ Below are the parameters that control this behavior across all services that sup
 Container architecture in Zerops defines how services are distributed across containers. Different service types use fundamentally different approaches:
 
 1. **Horizontal Scaling** (Runtime Services, Linux Containers, and Docker)
-2. **Deployment Modes** (Databases and Shared Storage)
+2. **Deployment Modes** (Databases and SeaweedFS)
 
 ### Horizontal Scaling (Runtime Services, Linux Containers, and Docker)
 
@@ -298,9 +298,9 @@ To configure horizontal scaling, users need to set the minimum and maximum numbe
 Setting identical minimum and maximum values creates a fixed number of containers (disables automatic horizontal scaling).
 :::
 
-### Deployment Modes (Databases and Shared Storage)
+### Deployment Modes (Databases and SeaweedFS)
 
-For databases and shared storage services, Zerops offers two deployment modes focused on reliability and data integrity.
+For databases and SeaweedFS services, Zerops offers two deployment modes focused on reliability and data integrity.
 
 :::warning
 Deployment mode cannot be changed after creation.
@@ -332,7 +332,7 @@ Highly Available (HA) Mode creates multiple containers with built-in redundancy.
 - Recommended for production use
 
 :::important
-Database and shared storage services in HA mode have a **fixed number of containers** that cannot be increased or decreased.
+Database and SeaweedFS services in HA mode have a **fixed number of containers** that cannot be increased or decreased.
 :::
 
 **Recovery process:**

diff --git a/apps/docs/content/gleam/how-to/create.mdx b/apps/docs/content/gleam/how-to/create.mdx
@@ -161,7 +161,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb"
 S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ"
 ```
 
-The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
+The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
 
 #### Description of description.yaml parameters
 

diff --git a/apps/docs/content/gleam/how-to/shared-storage.mdx b/apps/docs/content/gleam/how-to/shared-storage.mdx
diff --git a/apps/docs/content/go/how-to/create.mdx b/apps/docs/content/go/how-to/create.mdx
@@ -161,7 +161,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb"
 S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ"
 ```
 
-The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
+The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
 
 #### Description of description.yaml parameters
 

diff --git a/apps/docs/content/go/how-to/shared-storage.mdx b/apps/docs/content/go/how-to/shared-storage.mdx
diff --git a/apps/docs/content/guides/backup.mdx b/apps/docs/content/guides/backup.mdx
@@ -6,7 +6,7 @@ description: "Zerops auto-backs up databases and storage daily (00:00-01:00 UTC)
 Zerops auto-backs up databases and storage daily (00:00-01:00 UTC) with X25519 encryption; backups are retained for 7 days minimum after service/project deletion.
 
 ## Supported Services
-MariaDB, PostgreSQL, Qdrant, Elasticsearch, NATS, Meilisearch, Local Storage, Shared Storage.
+MariaDB, PostgreSQL, Qdrant, Elasticsearch, NATS, Meilisearch, Local Storage, SeaweedFS.
 
 **ClickHouse**: not on the standard auto-backup path — back it up with the native `BACKUP ALL ...` SQL command (super user), stored as `.tar.gz`.
 
@@ -51,7 +51,7 @@ End-to-end with X25519 per-project keys. Decrypted only on download.
 | Qdrant | `.snapshot` |
 | NATS | `.tar.gz` |
 | Local Storage | tar → `.tar.gz` (archive of the live volume — pause database writes or use an application-level backup for guaranteed consistency) |
-| Shared Storage | tar → `.tar.gz` |
+| SeaweedFS | tar → `.tar.gz` (archive of the whole filesystem, restore by extracting through a mount) |
 
 ## Gotchas
 - Valkey/KeyDB are not backed up → rely on service persistence or application-level backup.