Diff: systems/infrastructure-os
From e2380b3 to e2380b3
+0 / −0 lines
| Before | After |
|---|---|
| --- | --- |
| schema: foundry-doc-v1 | schema: foundry-doc-v1 |
| title: "Infrastructure OS" | title: "Infrastructure OS" |
| slug: infrastructure-os | slug: infrastructure-os |
| category: systems | category: systems |
| type: topic | type: topic |
| quality: complete | quality: complete |
| short_description: "Infrastructure OS is the virtualization layer and private network engine that hosts and coordinates multiple Totebox Archives across on-premise and cloud environments." | short_description: "Infrastructure OS is the virtualization layer and private network engine that hosts and coordinates multiple Totebox Archives across on-premise and cloud environments." |
| status: active | status: active |
| bcsc_class: public-disclosure-safe | bcsc_class: public-disclosure-safe |
| last_edited: 2026-05-04 | last_edited: 2026-05-04 |
| editor: pointsav-engineering | editor: pointsav-engineering |
| cites: [] | cites: [] |
| --- | --- |
| **Infrastructure OS** is the virtualization and networking backbone of the PointSav ecosystem. It operates as the foundational host layer that permits the execution of multiple isolated Totebox Archive instances on a single physical or virtual machine. | **Infrastructure OS** is the virtualization and networking backbone of the PointSav ecosystem. It operates as the foundational host layer that permits the execution of multiple isolated Totebox Archive instances on a single physical or virtual machine. |
| ## Virtualization and Orchestration | ## Virtualization and Orchestration |
| The primary role of **Infrastructure OS** is to virtualize hardware resources for the PointSav substrate. It acts as the underlying host for the **Micro Virtual Machines** that run individual Toteboxes. | The primary role of **Infrastructure OS** is to virtualize hardware resources for the PointSav substrate. It acts as the underlying host for the **Micro Virtual Machines** that run individual Toteboxes. |
| Through its integration with [[topic-totebox-orchestration]], Infrastructure OS manages the lifecycle of these archives, ensuring they remain isolated at the kernel level while providing the necessary compute resources for their internal services (such as extraction, indexing, and search). | Through its integration with [[topic-totebox-orchestration]], Infrastructure OS manages the lifecycle of these archives, ensuring they remain isolated at the kernel level while providing the necessary compute resources for their internal services (such as extraction, indexing, and search). |
| ## PointSav Private Network | ## PointSav Private Network |
| Infrastructure OS creates and maintains the **PointSav Private Network**. This is an encrypted, peer-to-peer overlay network that permits secure communication between distributed PointSav appliances. | Infrastructure OS creates and maintains the **PointSav Private Network**. This is an encrypted, peer-to-peer overlay network that permits secure communication between distributed PointSav appliances. |
| Every node running Infrastructure OS becomes a verified member of this network, allowing for: | Every node running Infrastructure OS becomes a verified member of this network, allowing for: |
| * **Encrypted Data Transfer:** Moving Totebox Archive bootable images between locations safely. | * **Encrypted Data Transfer:** Moving Totebox Archive bootable images between locations safely. |
| * **Linguistic Signaling:** Coordinating task execution across clusters without exposing raw data to the public internet. | * **Linguistic Signaling:** Coordinating task execution across clusters without exposing raw data to the public internet. |
| * **Remote Administration:** Enabling secure access via [[topic-console-os]]. | * **Remote Administration:** Enabling secure access via [[topic-console-os]]. |
| ## Hybrid Deployment | ## Hybrid Deployment |
| Infrastructure OS is designed for **Hybrid Deployment**. It can boot directly on Bare metal resources for maximum performance and security on-premise, or it can be deployed on public cloud resources (such as GCP, AWS, or Azure) to provide scalable infrastructure while maintaining the same sovereign security protocols. | Infrastructure OS is designed for **Hybrid Deployment**. It can boot directly on Bare metal resources for maximum performance and security on-premise, or it can be deployed on public cloud resources (such as GCP, AWS, or Azure) to provide scalable infrastructure while maintaining the same sovereign security protocols. |
| ## See Also | ## See Also |
| - [[topic-totebox-os]] | - [[topic-totebox-os]] |
| - [[topic-totebox-orchestration]] | - [[topic-totebox-orchestration]] |
| - [[topic-totebox-archive]] | - [[topic-totebox-archive]] |
| - [[topic-network-admin-os]] | - [[topic-network-admin-os]] |