Skip to content

PointSav Documentation

The engineering library for the PointSav platform — operating systems and services for regulated businesses that own their data, their AI, and their record-keeping outright. Where the monorepo holds the code, this wiki holds the reasoning: architecture, services, security, and the governance commitments that bind future development.

PointSav Digital Systems

Self-host a deployment

← All revisions

2434003b · PointSav Digital Systems ·

Track-B documentation wave: self-hosting category — 2 R0/R1 redactions (internal doc citations, unverifiable published-artifact claim, internal Foundry paths in rendered procedure)

View the full record as of this revision →

@@ -2,7 +2,7 @@
schema: foundry-doc-v1
title: "Self-host a deployment"
slug: self-host-a-deployment
short_description: "Boots the published os-totebox and app-orchestration-slm seL4 appliance images under QEMU, with configuration baked in at build time via device-tree bootargs, and verifies both come up healthy."
short_description: "Builds the os-totebox and app-orchestration-slm seL4 appliance images from source and boots them under QEMU, with configuration baked in at build time via device-tree bootargs, and verifies both come up healthy."
category: self-hosting
index_group: getting-the-platform-running
content_type: how-to
@@ -14,16 +14,15 @@ last_edited: 2026-08-04
editor: pointsav-engineering
paired_with: self-host-a-deployment.es.md
research_trail:
  sources: [GUIDE-deploying-os-totebox-orchestration-appliances.draft.md (project-totebox, 2026-08-03), BRIEF-os-totebox-platform.md, .agent/binary-targets.yaml]
  verification_method: "independently confirmed by project-totebox 2026-08-06 against real source (build-guest-rootfs.sh + deploy-loader-img.sh present for both os-totebox and app-orchestration-slm; vendor-libvmm/ confirmed genuine upstream seL4 Microkit VMM) after this archive raised a direct contradiction question against capability-based-security.md and os-totebox's Cargo.toml; app-orchestration-command's separate, not-yet-built seL4 packaging status was confirmed at the same time and does not apply to this guide, which never references that product"
  sources: [pointsav-monorepo os-totebox/scripts/build-guest-rootfs.sh, app-orchestration-slm/scripts/build-guest-rootfs.sh, vendor-libvmm]
  verification_method: "re-verified 2026-09-05: build-guest-rootfs.sh exists for both os-totebox and app-orchestration-slm and produces a loader image as a build output; no evidence found that either appliance's loader image is published as a downloadable artifact under a fixed filename, so this guide describes building from source rather than downloading a release"
---

## Prerequisites

- A host that can run QEMU for `aarch64` (the appliance images target this architecture regardless of your host's own CPU)
- The published `os-totebox-loader.img` and, optionally, `app-orchestration-slm-loader.img` from `software.pointsav.com`
- The source repo, the Microkit SDK, and an `aarch64` cross-compilation toolchain — building a loader image for `os-totebox` and, optionally, `app-orchestration-slm`, from source
- A persistent disk image, created once and kept — an ext4-formatted raw file the guest mounts at `/data`
- If you need non-default configuration (a specific orchestration endpoint, a Tier B license): the source repo, the Microkit SDK, and an `aarch64` cross-compilation toolchain — the published images alone don't let you change configuration after the fact (see Step 3)

## Purpose

@@ -52,7 +51,7 @@ Self-hosting a deployment means booting one or both of two independent, self-con
     -netdev user,id=netdev0,hostfwd=tcp::<host-port>-:<guest-port>
   ```

3. If the published, generic image's default configuration is sufficient, skip to Step 4. Otherwise, understand this before you try to change anything: **runtime configuration is baked into the image at build time**, in the device tree's `bootargs`. There is no post-boot config file and no `-append` equivalent on this boot path. Changing configuration means rebuilding the image yourself, with your own `foundry.*` bootarg values, and replacing the published one — see the relevant keys below and the full rebuild procedure in the internal dogfood development guide (`GUIDE-live-flow-doorman-orchestration-yoyo.draft.md`, project-totebox).
3. Understand this before you build: **runtime configuration is baked into the image at build time**, in the device tree's `bootargs`. There is no post-boot config file and no `-append` equivalent on this boot path. Setting configuration means passing your own `foundry.*` bootarg values to the build.

   | Key | Appliance | Purpose |
   |---|---|---|
@@ -88,7 +87,7 @@ Stop the QEMU process. The persistent disk (`persistent.raw`) is untouched by st
## Known limitations, as shipped (2026-08-03)

- No automated update mechanism — a configuration change means a rebuild and a full image replacement, not a live edit.
- The published images have not been through a customer-scale security review; treat as an early release.
- These images have not been through a customer-scale security review; treat as an early release.
- Real GPU-scale training requires your own Yo-Yo compute backend — the images themselves don't include one.

## See also
Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is currently a trade name of Woodfine Capital Projects Inc. ("Woodfine"), planned to become a wholly-owned Woodfine subsidiary upon incorporation. 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. The full trademark notice appears in the footer of every page on this site.

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 →