Products built on the MIT LOX DB core may need one runtime-selectable API plus security, safety validation, observability, lifecycle policy, connectivity and additional storage backends.
LOX DB Pro is a commercially licensed, pick-and-choose set of independent C modules delivered as CMake targets in the loxdb namespace. The public repository documents integration-facing contracts; implementation, source code and proprietary know-how remain private.
LOX DB Pro is described as a commercially licensed set of C modules around the MIT-licensed LOX DB core. The public loxdb_pro_docs repository publishes integration-facing API contracts, module descriptions, build guidance and licensing notes. It intentionally excludes source code, implementation internals and proprietary validation procedures.
The catalog describes loxdb_api as a plain/secure facade for KV/TS/REL, loxdb_secure as encryption/integrity integration with key rotation and DB-ID binding, and loxdb_safety as runtime validation plus a safety-profile identifier.
Documented modules cover fixed-frame or CBOR metrics export, audit/trace hooks and basic counters, health policy, optional self-heal/watchdog hooks, and alert state transitions driven by metric snapshots.
The API catalog describes quotas/rate limits, operation gates, retention callbacks, logical backup/import, and backup-first schema migration with migration history.
Documented modules include transport-agnostic replication, framing helpers, OTA planning/state and rollback hooks, CLI tools, optional FatFS SD storage and a basic raw-NAND FTL shim.
These are public API descriptions. The catalog does not expose implementation internals that would allow this site to claim behavior beyond those contracts.
The public overview presents a phased integration path: begin with LOX DB and a selected storage backend; add the loxdb_api facade in plain mode; enable secure mode with explicit key-management review; then select observability and any needed policy, retention, backup, migration or OTA modules.
The documentation's listed CMake target names and headers are integration contracts. A consumer needs the applicable commercial source distribution or repository access to build those targets.
The docs index points to a module catalog, per-module API references, a public API surface map, build/integration guidance and licensing notes. The published material is intended to explain integration-facing behavior while withholding internal architecture.
The public documentation names targets in the loxdb:: namespace, such as loxdb::api, loxdb::secure, loxdb::metrics and optional adapter targets. The exact public headers, options, dependencies and compatibility rules should be checked in the versioned documentation supplied for a specific commercial delivery.
The public repository describes module purpose, integration flow, API surface, build expectations and licensing.
The repository README explicitly says implementation source and proprietary engineering details are excluded.
Private validation procedures are not published in the documentation repository and cannot be assessed from it.
The public GitHub repository page does not list published Releases. Distribution should be confirmed through the commercial delivery channel.
Public API documentationModule catalogAPI surfaceBuild and integrationLicensing
LOX DB Pro is positioned around LOX DB. The MIT core's open source and evidence boundary are described separately on the LOX DB page.