feat: add more info from questions raised by customers (#2213)

TrayserCassa · renaudhager · Isengo1989 · web-flow · commit 543b4c16abe5 · 2026-04-16T14:36:24.000+02:00
* feat: add more info from questions raised by customers

* Update products/paas/shopware/monitoring/index.md

Co-authored-by: Renaud Hager &lt;renaudhager@users.noreply.github.com&gt;

* change/links-and-small-fix

* fix: remove html tag

---------

Co-authored-by: Renaud Hager &lt;renaudhager@users.noreply.github.com&gt;
Co-authored-by: Micha &lt;m.hobert@shopware.com&gt;
diff --git a/products/paas/shopware/faq.md b/products/paas/shopware/faq.md
@@ -15,6 +15,10 @@ For now, no rollback is possible when you do a force push and lose your git hist
 No, all containers are stateless, and local file writes are discouraged. Persistent storage must use S3 buckets or other external storage solutions.
 Changes to the filesystem and Shopware code must be made directly in the Git repository.
 
+## Is Shopware PaaS Native available on Azure or Google Cloud Platform?
+
+No, Shopware PaaS Native currently runs on AWS only.
+
 ## How can I connect my already deployed application to a new branch?
 
 The application that you create is linked to a commit SHA and not to a branch. You can change the existing application commit SHA by running `sw-paas application update`. What matters is the commit configured for a given application.
@@ -35,6 +39,10 @@ Yes. Follow the guide on [databases](./resources/databases.md).
 
 No, the infrastructure is opinionated and pre-configured. Customizations at the server level are not allowed.
 
+## Can I protect an application with basic auth?
+
+Basic auth is not recommended because it can lead to unexpected behavior in the platform setup. To restrict access temporarily, use Shopware maintenance mode instead.
+
 ## Are CDN or database configurations customizable?
 
 No, PaaS uses Fastly as the CDN and provides a fixed database configuration at the moment. Customizations to these resources are currently under development.
@@ -59,18 +67,70 @@ Custom applications and decoupled storefront hosting will be evaluated based on
    - `exec`: Best for debugging, maintenance, and interactive work
    - `command`: Best for automation, CI/CD, and scheduled tasks
 
-## Can I connect to my PaaS instance via SSH
+## Can I connect to my PaaS instance via SSH?
 
 Yes, you can connect to your PaaS instance — but not via traditional SSH. Instead, we provide a remote terminal session through the `sw-paas exec` CLI command. This command allows you to execute shell commands inside your PaaS environment remotely, effectively giving you SSH-like access for troubleshooting, deployments, or interactive sessions.
 
 ## Where can I see the status of my PaaS application update?
 
 You can see the status of your PaaS application by running `sw-paas application list`. This command shows the current status of your application, including whether the update was successful or if it's still in progress. To monitor all real-time events associated with the project and its applications run `sw-paas watch` this provides a live stream of events and is especially useful for tracking the progress of an ongoing update.
 
+## Are deployments zero downtime?
+
+Yes. Deployments are designed to be zero downtime and use Kubernetes rolling updates.
+
+## In what order do deployment steps run?
+
+Database migrations run first. After that, the remaining deployment flow is handled by the [deployment helper](../../../guides/hosting/installation-updates/deployments/deployment-helper#execution-flow).
+
+## Can I configure pre-deployment and post-deployment hooks?
+
+Yes. Use the [deployment helper](../../../guides/hosting/installation-updates/deployments/deployment-helper#configuration) to define deployment hooks.
+
+## Can I automate deployments from CI/CD?
+
+Yes. The CLI supports non-interactive execution and machine-to-machine authentication with tokens, so you can trigger builds and deployments from your CI/CD system.
+
+## Can my build contact external services?
+
+Yes. Builds run as regular Docker builds and can contact external endpoints when required, for example configured Composer repositories.
+
+## Are database copies anonymized when cloning an application?
+
+No. Cloning restores an exact snapshot of the source application's database and filesystem data. Anonymization is not currently supported.
+
+## How often does the scheduler run scheduled tasks?
+
+The platform runs the scheduler every 5 minutes.
+
+## Can I configure additional queues?
+
+No. Creating additional queues is not currently supported.
+
+## Are OpenSearch and Grafana protected by SSO?
+
+No. Single sign-on for tools such as Grafana and OpenSearch is not available at this stage.
+
+## Are Blackfire or Tideways included?
+
+No. Tideways and Blackfire are not currently supported as part of the platform.
+
+## Are load tests provided by Shopware PaaS Native?
+
+No, managed load testing is not currently provided as part of the platform.
+
+## How many projects or applications can I create?
+
+The available number depends on the booked plan for your organization.
+
+## How do I request infrastructure changes or support?
+
+Infrastructure change requests and support requests are handled through the standard ticketing process. Agencies can coordinate those requests together with the customer. In some setups, a dedicated Slack channel may also be available for faster coordination.
+
 ## Why do I see “Runtime extension management is disabled” when trying to purchase extensions in the admin?
 
 When trying to purchase an extension via the in-app store, the admin shows the error “Runtime extension management is disabled.” Even after setting runtime_extension_management: true in `config/packages/z-shopware.yaml` and deploying, the error will persist.
 
-This behavior is intentional. Runtime extension management is deliberately disabled in the Shopware Admin UI when using PaaS due to its ephemeral nature, and cannot be enabled by changing the runtime_extension_management configuration.
+This behavior is intentional. Runtime extension management is deliberately disabled in the Shopware Admin UI when using PaaS due to its ephemeral nature and cannot be enabled by changing the runtime_extension_management configuration.
 
 To use the in-app extension store, the `SwagExtensionStore` plugin must be installed via Composer. Once this extension is installed, the Shopware Admin can connect to the extension store and allow in-app purchases.
diff --git a/products/paas/shopware/fundamentals/applications.md b/products/paas/shopware/fundamentals/applications.md
@@ -12,6 +12,22 @@ Each application has its own compute resources, infrastructure, and deployment c
 
 For instance, you might allocate smaller, hibernating compute instances for staging while reserving larger, always-on resources for production.
 
+The number of projects and applications available to an organization depends on the booked plan.
+
+## Default resource profile and scaling
+
+Applications are provisioned with a default resource profile for the main Shopware workloads:
+
+| Component    | Default replicas | CPU request | Memory request | Memory limit |
+|--------------|------------------|-------------|----------------|--------------|
+| `storefront` | `2`              | `50m`       | `256Mi`        | `2Gi`        |
+| `admin`      | `1`              | `25m`       | `128Mi`        | `2Gi`        |
+| `worker`     | `1`              | `50m`       | `256Mi`        | `1Gi`        |
+
+Horizontal scaling is the primary scaling mechanism in Shopware PaaS Native.
+
+Resource limits above the default profile depend on the booked plan, with some flexibility for scaling within that scope.
+
 ## Creating an Application
 
 Create a new application to a project:
@@ -34,6 +50,10 @@ This command initiates the build process, packaging your application and prepari
 sw-paas application build logs
 ```
 
+Builds run as regular Docker builds. External network requests are allowed during the build when your project requires them, for example to reach configured Composer repositories or other external package sources.
+
+If your build needs credentials or other sensitive values, provide them through [Vault secrets](./secrets.md) using `buildenv` or by using `BUILD`-scoped environment variables where appropriate.
+
 ## Update your application
 
 To update your application, you need to run the following command and provide the commit SHA:
@@ -44,6 +64,18 @@ sw-paas application update
 
 This command initiates the build process, waits until it's done, and runs the deployment for you.
 
+## Deployment behavior
+
+Deployments are designed to be zero downtime and use Kubernetes rolling updates.
+
+During deployment, database migrations run first. After that, the remaining deployment flow is handled by the [deployment helper](../../../../guides/hosting/installation-updates/deployments/deployment-helper#execution-flow).
+
+This works well for regular Shopware deployments because breaking database changes are expected only during major Shopware upgrades. When upgrading across major versions, make sure your deployment remains backward compatible throughout the rollout.
+
+Pre-deployment and post-deployment hooks are supported through the [deployment helper configuration](../../../../guides/hosting/installation-updates/deployments/deployment-helper#configuration).
+
+Automated deployments from CI/CD are supported. The CLI can run in non-interactive mode and supports machine-to-machine authentication with tokens.
+
 ## Deploy a specific build of your application
 
 To create a deployment with a specific build, use the following command:
@@ -71,7 +103,7 @@ sw-paas application deploy get
 
 ## Plugin Management
 
-Plugin management is done [via Composer](../../../../guides/hosting/installation-updates/extension-managment#installing-extensions-with-composer) because the platform runs in a high-availability and clustered environment.
+Plugin management is done [via Composer](../../../../guides/hosting/installation-updates/extension-management#installing-extensions-with-composer) because the platform runs in a high-availability and clustered environment.
 
 In such setups, local changes aren't feasible, as all instances must remain identical and stateless. This ensures consistency across all deployments.
 
diff --git a/products/paas/shopware/fundamentals/organization.md b/products/paas/shopware/fundamentals/organization.md
@@ -6,7 +6,9 @@ nav:
 
 # Organizations
 
-An organization serves as the top-level container representing a company or an entity in Shopware PaaS Native. It acts as the primary organizational unit that encompasses all resources, projects, and users associated with a particular business entity. By default, the initial admin user is added to an Organization and can further add more users.
+An organization serves as the top-level logical unit representing a company or an entity in Shopware PaaS Native. It acts as the primary organizational unit that encompasses all resources, projects, and users associated with a particular business entity. By default, the initial admin user is added to an Organization and can further add more users.
+
+Organizations are long-lived logical units and do not expire automatically.
 
 To create additional organizations via CLI, run;
 
@@ -18,6 +20,8 @@ sw-paas organization create
 
 Organization members are users who have been granted access to an organization and its resources.
 
+Access control within an organization is managed by organization administrators through role assignments.
+
 ### Roles
 
 Organization members can be assigned different roles that determine their level of access and permissions:
diff --git a/products/paas/shopware/get-started/prepare-codebase.md b/products/paas/shopware/get-started/prepare-codebase.md
@@ -20,15 +20,15 @@ Additionally, before installation, verify that each plugin supports **S3-based s
 
 ## How to uninstall plugins
 
-To uninstall plugins in the PaaS environment, use the [Deployment Helper](../../../../guides/hosting/installation-updates/deployments/deployment-helper.html#removal-of-extensions) which provides a streamlined process for extension management.
+To uninstall plugins in the PaaS environment, use the [Deployment Helper](../../../../guides/hosting/installation-updates/deployments/deployment-helper#removal-of-extensions) which provides a streamlined process for extension management.
 
 The uninstallation process involves two steps:
 
 1. **Set the extension to remove**: Configure the extension state as `remove` in your `.shopware-project.yml` file and deploy the changes to uninstall the extension.
 
 2. **Remove from source code**: After the deployment, remove the extension from your source code and deploy again.
 
-For detailed instructions and configuration examples, refer to the [Removal of extensions](../../../../guides/hosting/installation-updates/deployments/deployment-helper.html#removal-of-extensions) section in the Deployment Helper documentation.
+For detailed instructions and configuration examples, refer to the [Removal of extensions](../../../../guides/hosting/installation-updates/deployments/deployment-helper#removal-of-extensions) section in the Deployment Helper documentation.
 
 ## Generating the required files
 
diff --git a/products/paas/shopware/guides/clone-application.md b/products/paas/shopware/guides/clone-application.md
@@ -89,6 +89,10 @@ The cloning process happens in two stages:
 
 This ensures that the target application receives an exact copy of the source application's state at the time of the selected deployment.
 
+:::warning
+Cloning does not anonymize database content. The restored snapshot includes the full database state and filesystem data from the source application, including scheduled task data stored in the database.
+:::
+
 ### Monitor clone progress
 
 After initiating the clone, you can monitor the progress using:
diff --git a/products/paas/shopware/monitoring/index.md b/products/paas/shopware/monitoring/index.md
@@ -7,3 +7,9 @@ nav:
 # Monitoring
 
 Shopware PaaS Native provides comprehensive monitoring capabilities to help you track the health and performance of your applications. With built-in monitoring tools, you can observe your application's behavior, troubleshoot issues, and ensure optimal performance in your cloud environment. This section introduces 3 key components used in monitoring: Logs, Traces and Events.
+
+Grafana access is currently provided through credentials returned by the CLI via the `sw-paas open grafana` command. Single sign-on for Grafana and similar tools is not available at this stage.
+
+Application performance monitoring tools such as Tideways or Blackfire are not currently supported as part of the platform, but we are working on it.
+
+Shopware PaaS Native does not currently provide managed load testing as part of the platform.
diff --git a/products/paas/shopware/resources/databases.md b/products/paas/shopware/resources/databases.md
@@ -18,6 +18,8 @@ To connect to your database via CLI:
 sw-paas open service --service database --port 3306
 ```
 
+Database access is provided through the CLI tunnel. Direct public database exposure is not supported.
+
 ### Note
 
 Please check the [known issues](../known-issues.md) regarding network considerations when running this command.
diff --git a/products/paas/shopware/resources/object-storage.md b/products/paas/shopware/resources/object-storage.md
@@ -10,4 +10,6 @@ nav:
 
 Applications in Shopware PaaS Native are created by default with two S3-compatible object storage buckets. A public bucket and a private bucket.
 
-You can learn more about [shopware filesystem here](../../../../guides/hosting/infrastructure/filesystem.md).
+Shopware filesystem is configured to use S3-compatible object storage by default for new applications. This storage setup is part of the platform design and should not be changed later.
+
+You can learn more about the Shopware filesystem [here](../../../../guides/hosting/infrastructure/filesystem.md).
