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

Add a node to a running fleet

Prerequisites

At least one node already enrolled and heartbeating (see Enroll a PPN node)
A second machine with service-vm-host deployed
A VM_NODE_ID that doesn't collide with any node already in the fleet

Purpose

Enroll a second (or third, or Nth) node into a fleet that's already running — a few minutes, and it's exactly the same procedure as enrolling the first node. There is no separate "add to a running fleet" mechanism; the fleet controller accepts new nodes at any time without disturbing existing ones.

Procedure

Check the existing fleet's current node IDs so your new one doesn't collide:
```
curl -s http://<fleet-controller-host>:9203/v1/nodes
```
The fleet controller rejects nothing at enrollment time based on naming — but reusing an ID would just mean the new node's heartbeats overwrite the existing node's record, not a clean rejection. Pick a genuinely distinct VM_NODE_ID.

On the new machine, set the same three required environment variables as any node enrollment:

VM_FLEET_ENDPOINT=http://<fleet-controller-host>:9203
VM_NODE_ID=<new-unique-node-id>
VM_WG_IP=<new-node-wireguard-ip>

Start service-vm-host under systemd, as with any node. It begins heartbeating immediately — no registration call, and no restart of the controller or any existing node is required.

Expected outcome

The new node appears in the fleet controller's listing alongside every existing node, each heartbeating independently, within one heartbeat interval (10 seconds by default).

Verification

curl -s http://<fleet-controller-host>:9203/v1/nodes

Confirm your new VM_NODE_ID appears with a recent last_heartbeat, and confirm every previously-existing node is still present and heartbeating too — adding a node doesn't touch any other node's state.

Rollback

Stop the new node's service-vm-host process. It drops out of the fleet listing on its own after roughly 30 seconds without a heartbeat — no separate removal step, and no effect on the rest of the fleet.

Next steps

Enroll a PPN node — the same procedure in full, including every environment variable and its default
Configure a tenant namespace — set up quotas for tenants placing VMs on this expanded fleet

See also

service-vm-fleet — the PPN VM fleet controller — the fleet controller's real route table and state model
Private Platform Network: pooled compute from hardware you already own — the fleet architecture this node joins

Cite this record: /wiki/add-a-fleet-node — revision 9b9339a2, last updated 6 August 2026.

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 →