> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/corporate/corporate/governance-and-compliance/paas-architecture.md).

# PaaS Architecture

**MFC Safe Pty Ltd**\
**Platform Architecture Guide**\
**Title:** MFC Safe PaaS Architecture Overview\
**Version:** 1.0\
**Effective Date:** 2 June 2025\
**Next Review Date:** 2 June 2026

***

#### **1. Purpose**

This guide outlines the high-level architecture of the MFC Safe Platform-as-a-Service (PaaS) environment, including its core services, infrastructure components, integrations, and operational design principles. It is intended to provide stakeholders, technical staff, and auditors with a clear understanding of the architectural foundations that support the Didge platform and its associated services.

***

#### **2. Architectural Principles**

* **Modular Design:** Decoupled microservices to ensure scalability and fault isolation.
* **Secure by Design:** End-to-end encryption, identity access controls, and least-privilege defaults.
* **Resilient & Redundant:** High availability across cloud zones and automated failover.
* **API-first:** All services expose APIs for integration, automation, and extensibility.
* **Compliance Aligned:** Adheres to ISO 27001, ISO 9001, and privacy-by-design frameworks.

***

#### **3. Core Components**

**3.1 Application Layer (Didge Platform)**

* React-based web interface
* RESTful API backend
* Digital form engine (workflow logic, compliance rules)

**3.2 Microservices & Containers**

* Containerized using Docker
* Orchestrated via managed Kubernetes (EKS)
* Stateless services with internal API calls (e.g., sensor ingestion, alert engine, reporting)

**3.3 Data & Storage**

* **Primary DB:** MongoDB Atlas (cloud managed, ISO 27001 certified)
* **Backup:** Daily and weekly snapshots retained for 90 days
* **Storage:** Encrypted object storage (Amazon S3)

**3.4 IoT Integration Layer**

* LoRaWAN-based gateway connectivity
* Payload decoding, uplink confirmation, and sensor registration
* Dragino and Multitech devices supported via integration profiles

**3.5 Security & Identity Management**

* Auth0 for authentication (OIDC, MFA, RBAC)
* AWS IAM for internal services and encryption keys
* Secrets stored via AWS Secrets Manager

**3.6 Monitoring & Logging**

* Centralized logging (Sentry, CloudWatch)
* API request tracing, audit trails
* SLA monitoring and uptime dashboards

**3.7 CI/CD & DevOps**

* GitHub Actions for CI pipelines
* Terraform for infrastructure as code (IaC)
* Auto-deploy staging and production via branch gating

***

#### **4. External Integrations**

* **Email & Alerts:** Mailgun, Twilio
* **Edge Security:** Cloudflare WAF, DNS, TLS
* **ChatOps & AI Support:** OpenAI integration with NLP workflows

***

#### **5. Cloud Infrastructure**

* Hosted in AWS Sydney and Singapore regions
* Enforced VPC boundaries and subnet segregation
* Private API Gateways and VPN for protected service calls

***

#### **6. Compliance & Data Residency**

* Personally Identifiable Information (PII) stored in-region (AU/SG) based on customer configuration
* Daily compliance audits via internal dashboard
* Encryption at rest (AES-256) and in transit (TLS 1.2+)

***

#### **7. Maintenance & Change Control**

* Weekly code release windows (non-breaking)
* Monthly infrastructure reviews
* Incident response tests every quarter

***

**Maintained By:** Architecture & Security Team\
**Contact:** <technology@mfcsafe.com>\
**Approved By:** Technology Director, MFC Safe Pty Ltd

***

End of Document


---

# 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://docs.didge.io/home/corporate/corporate/governance-and-compliance/paas-architecture.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.