> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/deployment-and-it-ops/deploy/infrastructure-management-on-premise.md).

# On-Premise and BYOC

Infrastructure requirements, ownership, and planning guidance for VM-based on-premises and BYOC deployments.

We offer separate VM-based and Kubernetes deployment options. This page focuses on the infrastructure and ownership requirements for the VM-based deployment. Kubernetes remains a separate offering with its own architecture and delivery process.

### **Deployment Types**

* VM (application components run in containers on one Ubuntu VM)
  * VM capacity is determined through a deployment assessment.
  * Databases can run on the VM or use the supported external-database variants below.
* Kubernetes with Managed Databases
  * This is a scalable and highly available deployment for 1000+ users.

***

### **VM Based Deployment Requirements**

The VM-based deployment runs the application on one customer-owned Ubuntu VM in a data center or bring-your-own-cloud environment. External databases or storage can reduce the amount of state held on the VM, but they don't remove the VM as the application's single failure domain.

{% hint style="warning" %}
The VM-based deployment isn't a highly available application topology. If your availability requirements need multiple application nodes, use the separate Kubernetes offering.
{% endhint %}

#### **Host Baseline**

| Resource              | Planning baseline                                                                                                                                      |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Operating system      | Ubuntu Server 24.04 LTS                                                                                                                                |
| CPU                   | 16 vCPU starting point                                                                                                                                 |
| Memory                | 64 GB starting point                                                                                                                                   |
| Storage               | SSD storage sized for the selected databases, screenshot and recording retention, backups, and expected growth. Use expandable storage where possible. |
| Administrative access | Key-based SSH for approved operators. The deployment account needs `sudo` access during installation and maintenance.                                  |
| Network               | Capacity for user traffic, screenshot or recording uploads, backups, updates, and external service traffic.                                            |

The CPU and memory values are reference starting points, not a guaranteed user capacity. We360 confirms the final VM, disk, and network sizing after reviewing the number of users, enabled capture modes, retention, database placement, backup design, and expected usage.

#### **Supported Database Placement**

The application components remain on one VM in every variant.

| Variant             | PostgreSQL                          | Clickhouse                          |
| ------------------- | ----------------------------------- | ----------------------------------- |
| Bundled databases   | Runs on the application VM          | Runs on the application VM          |
| External PostgreSQL | Customer-managed or managed service | Runs on the application VM          |
| External databases  | Customer-managed or managed service | Customer-managed or managed service |

Use the following starting requirements when a database is external:

| Database                 | Starting resources           | Additional requirements                                                                                                                    |
| ------------------------ | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| PostgreSQL 16, 17, or 18 | 2 vCPU, 8 GB RAM, 256 GB SSD | Support at least 300 connections. Allow the application VM to connect, enable backups, and enable WAL archiving or point-in-time recovery. |
| Clickhouse               | 2 vCPU, 8 GB RAM, 400 GB SSD | Allow the application VM to connect and enable disk snapshots.                                                                             |

These database values are planning baselines. Final CPU, memory, storage, IOPS, version compatibility, TLS, backup, and recovery requirements are confirmed during the deployment assessment. The customer owns external database availability, credentials, upgrades, and recovery.

#### **Storage for Screenshots and Backups**

| Tier   | Option                                  | Support boundary                                                                                                                                                    |
| ------ | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Tier 1 | External S3-compatible object storage   | Preferred. The endpoint, credentials, bucket permissions, browser access, signed URLs, and upload behavior must be validated for the selected provider.             |
| Tier 2 | NFS or a similar distributed filesystem | Requires design review and compatibility validation. The customer owns filesystem availability, latency, locking, durability, permissions, snapshots, and recovery. |
| Tier 2 | Additional attached SSD storage         | Requires design review. The customer owns disk availability, expansion, snapshots, and recovery. Confirm backup-workflow compatibility before deployment.           |

For Tier 2 options, We360 supports the approved application integration but can't guarantee against data loss, corruption, latency, or outages caused by the underlying storage platform. NFS interruptions can affect the application, and an attached disk shares the same host-level failure domain. A backup stored only on the same VM or disk isn't an off-host backup.

#### **Frontend Hosting**

| Option                | Infrastructure requirements                                                                                                                                                                            |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Frontend on the VM    | Provide a frontend DNS name, inbound HTTPS, and a valid certificate for the VM or its ingress.                                                                                                         |
| We360-hosted frontend | The frontend doesn't run on the VM. We360 and the customer confirm the public address, DNS ownership, allowed browser origins, cookies, and authentication redirects during the deployment assessment. |

#### **Network and Ingress**

Two ingress patterns are available:

* **Direct to the VM:** restrict SSH on TCP 22 to approved operator addresses; allow HTTPS on TCP 443; and allow HTTP on TCP 80 when redirects or HTTP-01 certificate issuance are used.
* **Customer load balancer or WAF:** complete a design review before deployment. The connection to the VM can use restricted private HTTP or verified HTTPS. Restrict VM access to the approved ingress, preserve the original host and scheme, and support WebSockets.

The single-VM deployment doesn't require unrestricted communication between multiple application hosts. Open only the approved ports between the application VM and any external database, object storage, SMTP, monitoring, DNS, or ingress service.

Outbound access is grouped by operational phase:

| Phase        | Required access                                                                                                                                                                                                                                                               |
| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Runtime      | The licensing and tenant-configuration service at <code class="expression">space.vars.company\_licensing\_server\_url</code>, the customer SMTP server, and any selected external database or object-storage endpoints. Client devices must also reach the licensing service. |
| Installation | The approved deployment-package location, container registries, Ubuntu and Docker package repositories, and the package or tool sources required by the approved release.                                                                                                     |
| Maintenance  | The runtime destinations plus the registries, package repositories, update sources, and certificate-authority endpoints needed for the planned maintenance activity.                                                                                                          |

We360 provides the exact release-specific destination and port Allowlist before deployment. If outbound access is normally restricted, allow installation and maintenance destinations only for the approved change window.

#### **IP Addresses, DNS, and Certificates**

For direct ingress, one reachable VM address is normally sufficient. For a load-balanced design, public DNS points to the customer ingress and the VM can remain private.

| DNS name       | When required                                  |
| -------------- | ---------------------------------------------- |
| Authentication | Always                                         |
| API            | Always                                         |
| Frontend       | Only when the frontend runs on the VM          |
| Storage        | Only when object storage is hosted with the VM |

All selected names must resolve correctly from the VM and from client networks. The customer supplies and renews certificates for direct HTTPS, or provides the DNS and inbound HTTP access required for approved HTTP-01 issuance. Load balancer/WAF certificate ownership, server-side TLS validation, and trusted forwarding settings are agreed during the design review.

#### **Email Server**

To enable invitations, reports, password resets, and other email features, the customer supplies:

* Sender display name and email address
* SMTP hostname and port
* Username and password or API key
* TLS, STARTTLS, or SSL requirements

The customer owns SMTP availability, credentials, sender authorization, and delivery policy.

#### **Ownership and Support**

| Customer responsibility                                                                                                              | We360 responsibility                                                                                                           |
| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------ |
| Provision and operate the VM, operating system, network, DNS, certificates, load balancer/WAF, SMTP, and selected external services. | Provide the approved deployment package, application images and versions, registry access, and deployment enrollment material. |
| Own infrastructure credentials, firewall approvals, monitoring, snapshots, backups, recovery, and maintenance windows.               | Review the proposed topology, provide the release-specific connectivity requirements, and validate the application deployment. |
| Approve and time-bound any support access.                                                                                           | Support the approved application configuration and deployment process. No permanent administrative access is required.         |

#### **Monitoring, Recovery, and Capacity**

At minimum:

* Alert when any VM disk partition reaches 80% usage.
* Alert when external screenshot, recording, or backup storage approaches its capacity limit.
* Enable disk snapshots or equivalent protection for the VM and external databases where applicable.
* Consider CPU and memory alerts based on the assessed workload.
* Consider certificate validity and expiry health checks when the customer owns certificate renewal.

Document recovery point and recovery time objectives for the selected topology. These are objectives, not guarantees: actual recovery depends on snapshot and backup frequency, retention, off-host availability, external service recovery, network capacity, and the tested restore procedure.

Use these values only for early storage planning:

| Data type         | Approximate monthly growth per user | Assumptions                                         |
| ----------------- | ----------------------------------- | --------------------------------------------------- |
| Screenshots       | 1 GB                                | Capture every five minutes across an eight-hour day |
| Screen recordings | 15 GB                               | Recording across an eight-hour day                  |

Actual usage varies with capture frequency, work patterns, resolution, compression, retention, and enabled features. Confirm capacity with a representative pilot and retain expansion headroom.

***

### **Kubernetes Requirements (1000+ Users)**

* Kubernetes Cluster (1.30+) with appropriate networking and load balancing.
* Kubernetes Worker Nodes:
  * 3-6 nodes of size 8 cores and 32GB RAM (worker node sizing/numbers will be based on user count)
  * Ensure worker nodes have a minimum of 100GB available for image caching and ephemeral storage.
* A storage provisioner (CSI Driver) that can provision at least 100 GB of disk space (SSD preferred)
* The two databases must be installed separately, either on virtual machines or as managed services.
  * PostgreSQL Database
  * Clickhouse Database


---

# 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.we360.ai/deployment-and-it-ops/deploy/infrastructure-management-on-premise.md?ask=<question>&goal=<user_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.
