Economic model — community and SMB customer tiers
PointSav's two-tier commercial structure: a free Community tier that serves as an adoption funnel, and a paid SMB Customer tier targeting regulated small-to-medium businesses that hyperscale billing models cannot serve economically.
Read the full articleRecently updated
All changes →- Professional CentresArchetypesTopic
- Co-location Tier NomenclatureReferenceTopic
- Parking Structures (PKS)ArchetypesTopic
- Vertical Warehouse (VWH)ArchetypesTopic
- Architecture Overview — PointSav PlatformArchitectureTopic
- PPN Tenant VM IsolationArchitectureTopic
- PPN VM Resource Pool ArchitectureArchitectureTopic
- Data Overview — Location Intelligence and GIS Data LayersPatternsTopic
PointSav builds operating systems and services for regulated businesses that need to own their data, their AI, and their record-keeping outright. The platform runs on customer hardware, produces continuous-disclosure-grade records by structure, and operates fully without AI for buyers that require an air-gap.
This wiki is the engineering library for that platform, maintained against the published editorial standard. It documents the architecture, the services, the operating systems, the governance commitments, and the design rationale that binds future development. It is written for institutional readers — auditors, technical due-diligence reviewers, and procurement evaluators — and for the engineers who build on or extend the platform. Where the engineering monorepo holds the code, this wiki holds the reasoning.
Forward-looking statements in this wiki carry planned, intended, or target language per the editorial standard.
New here? Start with these
Browse by area
Definitional materials for contributors across all audiences: style guides for each document genre, editorial philosophy, BIM and real-property reference corpus, glossary, and platform-specific terminology.
User-facing and internal applications built on the PointSav platform substrate — the wiki engine, marketing surface, GIS analytics engine, the browser developer workbench, the structured-input gate, and the design-intent articles that frame how those surfaces are composed.
The purpose-built operating systems that share a common seL4 and Rust substrate — Totebox, Console, Workplace, Orchestration, Infrastructure, Network Admin, MediaKit, and PrivateGit — each doing one job, holding no features it does not need, and communicating through a common Diode-based protocol discipline.
The autonomous services that implement Ring 1 boundary ingest and Ring 2 deterministic knowledge processing in the PointSav three-ring architecture — grouped by ring layer and function.
Fleet deployment topology, cloud operational runtime, and physical infrastructure — the WORM ledger storage substrate, edge deployment patterns, the private WireGuard mesh, sovereign telemetry, key-wiring operations, and the bookkeeping vault that anchors the SMB accounting surface.
Cross-cutting platform architecture: the three-ring composition model, AI routing and inference boundary, security and identity substrate, customer ownership principles, and the location intelligence domain.
The substrate category collects the platform's foundational mechanism concepts — the Compounding Substrate, Apprenticeship Substrate, Citation Substrate, Disclosure Substrate, Trajectory Substrate, Language Protocol Substrate, and the disciplines and primitives that compose them — each describing a structural property the platform relies on rather than a specific service or system.