Skip to content
PointSav Digital Systems

Last updated · 17e01f7b · Español

Compute substrate

os-infrastructure is the compute substrate that hosts the other PointSav operating systems. One instance runs on one piece of hardware — a bare-metal server in an office, a colocated rack, or a cloud virtual machine. Taken together, a fleet of os-infrastructure nodes forms the PointSav Private Network (PPN): an encrypted WireGuard mesh that ties Toteboxes, Consoles, MediaKits, and PrivateGit instances together without exposing any node to the public internet. This article covers the three deployment postures, the Genesis Protocol that bootstraps a fleet, and the structural gap in conventional cloud offerings that the design exploits.

The three deployment postures

os-infrastructure is the same OS in three postures. The operator chooses where their compute lives — and can blend any combination in a single fleet:

App surface Hardware Trust profile
app-infrastructure-onprem Servers on the operator's own premises Highest trust; the operator owns and can physically verify the hardware
app-infrastructure-leased Colocated bare-metal at an external data centre Hybrid trust; the operator controls the OS but cannot physically verify every boot
app-infrastructure-cloud Hyperscaler VMs (GCP, AWS, Azure) Lowest trust; used for stateless edge relay, not persistent storage

The same WireGuard mesh runs across all three. An operator can start with a single cloud relay and add on-premises nodes later without restructuring software.

The Genesis Protocol

Conventional fleet management requires a control plane to exist before any compute node can join. os-infrastructure inverts this. When a node boots and finds no PPN beacon, it does not fail — it declares itself a Private Network of One.

  1. Blind boot. The node ignores DHCP and DNS conventions. The seL4 kernel generates a Tier-1 fiduciary keypair at first boot.
  2. Scan. The node looks for an os-network-admin beacon on the local mesh.
  3. Genesis fork. If nothing answers, the node creates its own one-node PPN and seals all external ports except one.
  4. Holding pattern. A single hardened WebSocket endpoint waits for an administrative claim.
  5. Claim. When an administrator boots os-network-admin and presents the administrative fiduciary key, the node verifies the claim, binds to the fleet, and joins the mesh.

A customer can ship fifty servers to fifty edge locations. Each boots, forms a single-node PPN, and holds. Whenever the administrator is ready, the central os-network-admin claims all of them, merging them into one global fleet. The nodes do not need to know in advance how many siblings they will eventually have.

The PointSav Private Network

Every os-infrastructure node is a member of the PPN — the WireGuard overlay that connects all PointSav appliances in a fleet:

  • Encrypted data transfer: Totebox archive images move between locations without touching the public internet.
  • Linguistic signalling: os-network-admin broadcasts 16-byte binary commands across the mesh; every node receives simultaneously, only the addressed node acts.
  • Remote administration: os-console pairs to os-totebox instances through the PPN without requiring a VPN client on the operator's host machine.

The Hyperscaler Gap

The architecture deliberately exploits a structural gap in conventional cloud offerings:

Conventional cloud os-infrastructure
Couples compute to proprietary storage; charges egress for data movement Treats the cloud as a stateless relay; persistent storage stays on the operator's hardware
Provides rental access; withholds custodial ownership The operator can physically unplug and move the substrate
Requires network engineering before compute can be added Nodes self-bootstrap via the Genesis Protocol
Single-vendor control plane as a single point of failure Every os-infrastructure node can genesis a fleet independently

An operator running os-infrastructure on a single server in their office, a cloud relay node for public connectivity, and os-network-admin on an administrative workstation has built a fleet that is not locked to any hyperscaler and is inaccessible to external attackers without a valid fiduciary key. The storage architecture for each node follows the WORM discipline that governs all PointSav data persistence.

See also

Important Information

Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is a trade name of Woodfine Capital Projects Inc. ("Woodfine"). PointSav does not itself offer, sell, or solicit any security. Any securities offering associated with Woodfine's real-property direct-hold solutions is made exclusively by Woodfine, and only by means of the applicable Private Placement Memorandum.

No investment advice. This wiki's content is provided for engineering, operational, research, and development purposes. Nothing on this wiki constitutes investment advice or a solicitation to invest in any Woodfine partnership or direct-hold solution.

Intellectual property. The PointSav name, trade name, wordmark, and marks, together with all current and future PointSav- and Totebox-branded products, services, and offerings — and the software, source code, documentation, design system, and all related materials — are proprietary to Woodfine and its affiliates, except for components identified as open source. No rights are granted except as expressly set out in a written license or agreement. See TRADEMARK.md in this repository for the full trademark notice.

Open source components. Portions of the platform are made available under permissive open-source licenses identified in the accompanying repository. Use of those components is governed by their respective license terms.

No warranty; informational use. Content on this wiki is provided for general informational purposes only and does not constitute a representation, warranty, or commitment with respect to product functionality, availability, pricing, or roadmap. Some articles describe planned or intended features, capabilities, and milestones — language such as "planned," "intended," "targeted," "may," and "expected" marks this forward-looking content, which is subject to change and does not constitute a commitment regarding future performance.

Confidentiality. Where an article describes an operational or deployment detail that is not intended for public disclosure, that article is not published on this wiki. Content here is general-purpose engineering documentation, not customer-specific configuration.

Jurisdiction. Woodfine Capital Projects Inc. is organized in British Columbia, Canada. References to the Sovereign Data Foundation on this wiki describe a planned or intended initiative only, not a current equity holder or active governance body.

Changes to this notice. PointSav may update this notice from time to time; the version posted on this page governs.

Not a filing system. This wiki is not a securities filing system, an electronic disclosure repository, or a substitute for SEDAR+ or any other regulatory filing system. Formal securities filings are made through the applicable regulatory filing system, not through this wiki.

Full disclaimer. This notice supplements, and does not replace, the full Disclaimers article. In the event of any conflict, the full Disclaimers article governs.

Read the full disclaimer →