Octane
Octane adds capability to an OpenSearch cluster you already run. There is no migration, no fork, and no new engine to operate.
| Component | Shape | What it does |
|---|---|---|
| Autoscale | external controller | Grows, shrinks and rolls a cluster without losing a shard copy |
| Accelerator | plugin | Faster points, binary-quantized vectors, graph traversal |
| Content extraction | plugin | Extraction, chunking, embedding, imagery tiling and the geo stack |
| Governance & compliance | plugin | Ten regulatory profiles, redaction before indexing, per-organisation ingest governance |
| License | plugin | One registration shared by the others; self-serve 30-day trial |
| Advisor | standalone tool, free | Reads a cluster and reports what is wrong with it. No license, runs on any 3.x |
Nothing phones home. The license is verified locally, and the trial record lives in your own cluster state.
The shape of the thing
Two of these run inside your nodes and two do not, and the difference decides how you adopt them.
┌──────────────────────────────────────────┐
│ your OpenSearch cluster │
│ │
┌──────────┐ │ ┌───────────────────────────────────┐ │
│ autoscale│─REST─┼──▶│ node │ │
│controller│ │ │ ├─ octane-license (plugin) │ │
└────┬─────┘ │ │ ├─ octane-accelerator (plugin) │ │
│ │ │ └─ octane-content (plugin) │ │
│ scales │ └───────────────────────────────────┘ │
▼ │ │
StatefulSet / └──────────────────────────────────────────┘
custom resource
Autoscale does not install into the cluster. It runs beside it and speaks to the REST API. No per-node install, no restart to adopt it, no version pin — and it works against a managed service, where Octane's plugins cannot be installed.
The accelerator and content plugins do install, because a codec and an ingest pipeline both run inside the node and no API substitutes for being there. They install per node and take effect on restart — which is what the controller's rolling restart is for.
Requirements
- OpenSearch 3.3.0 through 3.8.x for all three plugins, which declare the same range
- Any 3.x for the controller and the advisor, which talk REST and install nothing in the cluster
- JDK 21
The advisor needs no license and no trial. It is the one piece you can run against a cluster today, including versions the plugins cannot install on at all.
The floor is set by OpenSearch's own version-range parser rather than by anything Octane calls, and the accelerator spans the range by shipping one compiled generation per Lucene SPI shape. See Compatibility for both mechanisms and what they mean on upgrade.
Where to start
- Advisor — start here. Free, read-only, no license: point it at a cluster and it tells you what is wrong with it. Nothing is installed and nothing leaves your machine
- Install — get the plugins onto a node, in the right order
- Quickstart — a working pipeline end to end, in about ten minutes
- Licensing — what is gated, what never is, and how to start a trial