PointSav — company overview and three-organisation structure

PointSav Digital Systems is a technology vendor that builds and licenses sovereign, on-premise-capable operating systems and services for record-keeping, business administration, and cyberphysical-system integration. The company exists to engineer the substrate that runs its parent group's real-estate operations, then licenses that substrate to similarly-structured institutional customers. PointSav sits inside a three-organisation governance topology established by Woodfine Capital Projects Inc., a real-estate firm focused on procurement, development, and management of real property. This article covers the three-organisation structure, the structural advantages it produces, and the licensing and contributor model.

The three-organisation structure

The relationship flow is strictly one-directional: the vendor builds, the customer adopts, deployments run. There are no reverse writes — the customer never edits vendor source, and the vendor never manages customer records.

Why this structure matters

Three structural advantages emerge from the separation:

Clean IP custody. PointSav holds the intellectual property. MCorp licenses the product like any other customer. There is no commingling of corporate records and source code.

Reference deployment. Because MCorp is a real operator — not a test environment — every product feature must survive contact with actual business operations before it can be sold elsewhere. The reference customer is the quality gate.

Investor clarity. The vendor (PointSav) is the asset that scales. The customer (MCorp) is the asset that operates. Each can be measured, audited, and valued on its own terms.

Licensing model

The product strategy follows an open-core pattern, licensed per directory rather than as one blanket grant. os-console and os-workplace ship under AGPL-3.0-or-later. os-totebox ships under the Functional Source License (FSL-1.1-ALv2), which converts automatically to Apache-2.0 for each release after a fixed period. The fleet-aggregator product (os-orchestration) remains fully proprietary as the company's stated commercial moat — it is never distributed under either the AGPL commercial-alternative tier or the FSL tier the other three carry.

PointSav intends to partner with the Sovereign Data Foundation to oversee the integrity of the open-source components. Terms and structure of any such arrangement are planned and subject to finalisation.

Contributor model

Engineering work flows through staging-tier contributor identities — established contributors who are MCorp employees pushing to their own GitHub forks. The vendor administration function accepts contributions via squash-merge — the moment the intellectual property formally transfers from contributor to vendor. The customer organisation pulls release tags from the vendor. A double-blind air-gap applies: contributors never push directly to customer repositories; the customer organisation never has visibility into contributor forks. See the five-stage supply chain.

See also

• Legal and IP structure — corporate entities, IP transfer mechanics, patent and licence strategy
• Deployment patterns — the six canonical configurations for PointSav deployments
• OS family — eight operating systems, one substrate — the eight operating systems PointSav builds
• Machine-based authorization — the security model that underlies the platform
• Compliance and continuous disclosure — continuous-disclosure obligations and compliance posture