Cloud & Enterprise

Introduced 0.12.0

The Cloud & Enterprise capabilities extend a Lucenia cluster for demanding, regulated production: the cluster can be autoscaled to match real demand, distributed analytics compute can run co-located with your data, and a standards-based compliance and content-governance layer controls how sensitive data is detected, redacted, and which external sources content may be ingested from.

warning

The autoscaling and distributed analytics capabilities are driven by the Lucenia Kubernetes operator, which is available with a commercial Lucenia subscription and is not published publicly. Their in-cluster building blocks (the autoscale engine's capacity, safety, and drain APIs) ship with Lucenia, but the operator that consumes those signals to actually add, remove, and resize nodes is distributed only as part of Lucenia's enterprise offering. There is no license key or in-code license check — the gate is simply that the operator is not publicly distributed. The compliance and content-governance capabilities below, by contrast, ship in-cluster and require no operator.

In this section

• Autoscaling — the in-cluster autoscale engine (capacity deciders, safety verdicts, and node-drain APIs) and how the Kubernetes operator consumes it to scale StatefulSets safely.
• Distributed Analytics — co-located distributed analytics compute that runs alongside Lucenia data nodes, analyzing cluster data in place.
• Compliance & Content Governance — the standards-based governance layer: sensitive-data detectors and profiles, named policies, industry presets, OSCAL regulatory frameworks, and access-governance blueprints. Ships in-cluster; no operator required.
• Content-source governance — deny-by-default allow/deny control over the external URIs the ingest pipeline may fetch from. Ships in-cluster; no operator required.

How the pieces fit together

Lucenia ships an in-cluster autoscale engine (the autoscale module) that acts as the "brain": it evaluates whether each node tier needs more or fewer resources, vetoes unsafe actions, and coordinates node drains. The engine takes no action on its own — it exposes REST APIs and waits to be asked.

The Lucenia Kubernetes operator is the "hands": it deploys and manages Lucenia clusters as Kubernetes StatefulSets, polls the autoscale engine, and translates its recommendations into real scaling operations (adding or resizing node pools, draining and removing nodes) while preserving data safety.

Because the operator is the component that actually performs scaling — and because it is the same operator that co-locates distributed analytics compute with your data — both capabilities in this section require the commercial operator.