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

# Deployment

The OPORA Platform is deployed as a dedicated instance within your organisation’s AWS  environment. This ensures **data sovereignty, compliance with local regulations**, and **full control** over your infrastructure, aligned with your geographical and operational needs. 

### Cloud Infrastructure

The platform operates in a **controlled, private AWS Virtual Private Cloud (VPC)**. Key features include:

* **Regional Hosting**: Deployed in the AWS region that corresponds to your operational geography.
* **Private Networking**: Services communicate internally via a **TSL-encrypted API** within your VPC- **never exposed to the public internet**.
* **Scalable and Secure**: The architecture is designed for scalability, reliability, and strict security boundaries.

{% hint style="success" %}
Read more about [AWS Server infrastructure here.](/opora-health-documentation/about-opora-core/deployment/server-infrastructure.md)
{% endhint %}

### Security and Compliance

Deployment includes robust security features to meet high-assurance environments:

* **Role-Based Access Controls (RBAC);**
* **Multi-Factor Authentication (MFA);**
* **Secure Software Development Lifecycle (SDLC);**
* **TLS 1.3 encryption** for all data in transit;
* **AES-256 encryption** for data at rest;
* **Regular backups** with retention policies;
* **Firewall and IP whitelisting** for endpoint control;
* **End-to-end encryption** across mobile/web apps and VPC services.

### Multi-Region Support

The platform is designed for global scale, supporting multi-region deployments:

* **Region-Specific Databases**: Separate data stores ensure legal and regulatory alignment.
* **Smart Routing**: User data residency is detected at onboarding and routed accordingly.
* **Anonymisation Layer**: Enables global insights through aggregated, de-identified data.
* **Audit Logs**: Data transfer logs provide a traceable compliance trail.

### Branding and White Labelling

The platform supports full **white-labelling and UI customisation**, including:

* Organisation name;
* Brand colours;
* Logo placement;
* Feature toggles and interface customisation.

This ensures a cohesive brand experience across all user touchpoints.

### Devices and OS Supported 

#### OPORA is available and validated for following devices:

1. Application for Users and Patients - iOS, hardware - from iPhone 7 and newer, OS - from 17 iOS and newer; Android.
2. Web platform for Clinicians, Managers, Sales and Admin - Web browsers: Chrome, IE, Firefox, Safari, Opera. Web dashboards are adapted for browser screens that include tablets such as iPad.

### Mobile application publishing 

The User-facing Mobile applications can be tested with invited users and published via Apple AppStore and Google Play Market. More on that [here](/opora-health-documentation/core-features/mobile-app.md). 

### Deployment Timelines

The OPORA Platform follows a **rapid deployment model**:

* **The CORE Platform**: Deployed within **two weeks** from infrastructure access and credential provisioning. This includes baseline functionality, security configuration, and system integration within your VPC. This time frame does not include registration, submission, and approval processes for mobile app distribution via the App Store and Google Play. These steps depend on third-party review timelines.
* **Customisation Phase**:
  * **Branding** (name, logo, colours) is typically completed within **3–5 business days** post core deployment.
  * **Feature Customisations** (workflow adjustments, bespoke modules, UI elements) are **subject to scope**, and timelines vary depending on complexity and validation cycles.

We work closely with your team to define these requirements early, ensuring transparency and timely delivery.

> *Note: A detailed project timeline is shared during onboarding, and weekly progress updates are standard throughout deployment.*