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.
Leer el artículo completoActualizado recientemente
Todos los cambios →- 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 desarrolla sistemas operativos y servicios para empresas reguladas que necesitan poseer sus datos, su inteligencia artificial y su registro contable de forma integral. La plataforma funciona en hardware del cliente, produce registros con calidad de divulgación continua por diseño y opera completamente sin IA para los compradores que requieren un entorno aislado.
Esta wiki es la biblioteca de ingeniería de esa plataforma. Documenta la arquitectura, los servicios, los sistemas operativos, el sistema de diseño y los compromisos de gobernanza que rigen el desarrollo futuro. Está redactada para lectores institucionales — auditores, revisores de debida diligencia técnica y evaluadores de adquisiciones — y para los ingenieros que construyen sobre la plataforma o la amplían. Donde el repositorio de ingeniería contiene el código, esta wiki contiene el razonamiento.
¿Primera vez aquí? Empieza con estos
Explorar por área
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.