> For the complete documentation index, see [llms.txt](https://docufi3d.gitbook.io/docufi3d/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docufi3d.gitbook.io/docufi3d/technical-documentation/infrastructure-overview.md).

# Infrastructure Overview

<figure><img src="https://1270204656-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3rNBjnk1QooV43GjCjYX%2Fuploads%2F1PsHx8pHj9wjtPC0RayU%2FDocufi3d%20-%20Infrastructure.png?alt=media&amp;token=a105c643-d63d-4f41-8d94-c1ada5b80246" alt=""><figcaption></figcaption></figure>

***

### 📡 Docufi3d Infrastructure Overview – Summary (v1.1)

The Docufi3d system is built on a **redundant and secure architecture** that combines two main Laravel-based application servers, a cyber-protected backend, and integrations with various productivity, security, and blockchain services.

***

#### 1. 🔒 Access & Network Security

* **VPN** access is provided for employees (BYOD devices).
* External users (Kunden) connect via the **Internet**, routed through:
  * **Firewall**
  * **Load Balancer with Cluster IP Failover**
  * **Cyber Protect module**

***

#### 2. 🟨 Core Infrastructure Services (Yellow Box)

* **Cyber Protect Suite** includes:
  * Firewall
  * Load balancer (Cluster IP failover)
  * **Managed Backup** system
  * **Monitoring tools**
* These services support high availability and security for both Docufi3d servers.

***

#### 3. 🟥 Application Servers

**Docufi3d Server 1 & 2 (Red Boxes):**

* Each runs **Laravel-based Docufi3d application**.
* Components per server:
  * **NGINX** reverse proxy
  * **VPS** container or VM hosting the Laravel app
  * **Database**
  * **Logfile systems**
  * **Backup** processes
* **SSH** access from secure zones is used for maintenance.

***

#### 4. 🧠 AI and Service Integrations (Right Side)

The Docufi3d backend connects with multiple external services:

* **Authentication & Email:**
  * Apple, Google, Microsoft (OAuth)
  * Email & Password login
  * Mailgun for transactional emails
* **AI Modules:**
  * **AI Translate** → DeepL
  * **AI Contract Analysis** → Legatics
  * **AI Text-to-Speech** → Elevenlabs
* **Digital Signing & Blockchain:**
  * Sign → Swisscom Trust Services
  * **Seal (All Signatures collected)** → Pushed to **Cardano Blockchain**
* **Logging and Communication:**
  * Log → Slack
  * Contact module for end-users

***

#### 5. 🧩 External SaaS & Productivity Tools

Tools connected via API or team use:

* **Infrastructure / Hosting:**
  * Strato
* **Communication & Collaboration:**
  * Slack
  * ClickUp
  * Google Workspace (Gmail, GCalendar, GDrive, GMeet)
  * GitBook
  * GitHub
  * Miro

***

### ✅ Key Features

* **Redundant server setup** with shared architecture
* **Backup and failover-ready**
* **Integrated AI modules** for contract processing
* **Cardano blockchain sealing**
* **Swisscom Trust for compliant signatures**
* Modular connection with external services (OAuth, TTS, AI, mail, etc.)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docufi3d.gitbook.io/docufi3d/technical-documentation/infrastructure-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.