LOX · Liquid Oxygen for Embedded Systems

LOX DB Pro

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.

CommercialCommercialC
GitHubQuick Start
Last verified
Not audited against current README/docs
Platform scope
Depends on the selected module and adapter contract

What it solves

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.

How it works

1Application→2loxdb_api facade→3selected plain or secure path→4LOX DB core→5selected storage backend

Use it when

Use loxdb_api as one call surface that can switch between plain and secure mode at runtime
Add encryption, integrity and runtime safety validation with loxdb_secure and loxdb_safety
Add metrics, structured logging, health monitoring and alert state machines
Apply admission, retention, backup and schema-migration policies
Add replication, networking, OTA planning or CLI operations
Select optional FatFS SD-card or basic raw-NAND FTL backends

Quick Start

# LOX DB Pro modules are delivered as independent CMake targets.
# Link only the targets selected for the product, for example:
target_link_libraries(app PRIVATE loxdb::api loxdb::metrics)
# Confirm exact target names and availability against the delivered package.

Engineering evidence

  • The public documentation index links the commercial overview, module catalog, per-module API references, public API surface, build/integration guide and licensing guide
  • The published catalog groups facade, security/safety, observability, policy/lifecycle, connectivity/operations and optional backend modules
  • The repository explicitly separates its public integration documentation from implementation internals, source code and private validation procedures

Known limits

  • The public repository publishes API-level and integration documentation, not implementation source
  • Private validation procedures and proprietary know-how are outside the public documentation scope
  • Exact module availability, package contents and commercial terms must be confirmed for the delivered package