> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/resources/policies-and-security/corporate-policies-and-security-compliance/product-level-certifications/backup-and-archive/flosum-backup-and-archive-security-and-compliance-statement/system-architecture.md).
# System Architecture
The Backup & Archive application frontend and backend are segmented on different subnet zones for security isolation. Our web servers are placed in a DMZ network, and database servers reside on a separate internal network. Firewalls, IPS, and strict access controls limit traffic between application tiers. Flosum has configured Security Groups that allow making requests only on port 443. Backup & Archive also provides a configuration file for self-hosted environments that can be used to reconfigure ports as needed.
The latest stable versions of frameworks and languages are used to avoid known vulnerabilities. The operating systems and software libraries are frequently patched and hardened. Load Balancing and failover systems maintain uptime during traffic spikes. Infrastructure redundancy removes single points of failure.\
\
Logical segregation of database data from other customers is applied. Customer-Hosted is a dedicated-tenant architecture. Flosum-Hosted is multi-tenant segmented by Salesforce Org ID. Flosum Backup & Archive does not have a data sharing mechanism. Communications take place only in the UI, or with the Salesforce orgs being backed up. Stringent access controls are in place to ensure the isolation of every Backup & Archive account within a dedicated virtual machine, in accordance with Backup & Archive SOC2 Type II policies. S3 buckets are never exposed to the public internet. They are set to Private as default and it is never changed. Flosum also uses a reverse proxy server to provide private links to customers.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.flosum.com/resources/policies-and-security/corporate-policies-and-security-compliance/product-level-certifications/backup-and-archive/flosum-backup-and-archive-security-and-compliance-statement/system-architecture.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
