Oxidizer Lite
Oxidizer Lite helps you turn Python functions into data workflows. You describe what runs, in what order, and where the data comes from and goes in YAML. The controller keeps things moving, while workers process batches and save checkpoints along the way. Use it to pull data from APIs or object storage, pass records through Redis or Kafka, and write results to Iceberg tables.
Active development: interfaces and configuration may change between releases.
Key Concepts
| Concept | Purpose |
|---|---|
| Controller | Starts runs, schedules ready tasks, and tracks progress and checkpoints. |
| Worker | Executes Python task functions and handles configured inputs and outputs. |
| API / MCP (Topology) | Exposes run inspection, diagnostics, table queries, and configuration management to HTTP and MCP clients. The REST API also starts workflows. |
| Workflow (formula) | YAML describing task nodes, dependencies, and input/output methods. |
| Connection | Named backend settings referenced by workflows, separate from task logic. |
| Schema | Defines table columns, record identity, and write policies such as upsert or SCD2 history. |
See workflows and connections, schema configuration, and run state and checkpoints.
Quickstart
The supplied Redis demo reads a million-row Parquet fixture and writes Iceberg upsert and history tables using local RustFS storage.
From the repository root:
cd examples/quickstart
docker compose -f compose.redis.yml up -d
docker compose -f compose.redis.yml logs seed
Wait for Ready to invoke quickstart_observations_redis in the seed log.
The first API image build downloads its documentation-search model; serving
does not require a model download or API key.
REST API
Check readiness, then invoke the workflow:
curl --fail http://localhost:8027/api/health
curl --fail http://localhost:8027/api/docs/status
curl --fail-with-body --silent --show-error \
--request POST http://localhost:8027/api/invocations \
--header 'Content-Type: application/json' \
--data '{"formula_id":"quickstart_observations_redis"}'
Use the returned run_id to inspect progress:
curl --fail-with-body --silent --show-error \
"http://localhost:8027/api/formulas/quickstart_observations_redis/runs/<run-id>"
The quickstart guide includes result queries, expected counts, the Kafka alternative, customization, and cleanup instructions.
MCP
Connect an MCP client using Streamable HTTP at
http://localhost:8027/mcp. Example tool calls (not REST requests):
{"name":"list_formulas","arguments":{}}
{"name":"get_formula_state","arguments":{"formula_id":"quickstart_observations_redis","run_id":"<run-id>"}}
{"name":"search_docs","arguments":{"query":"How do I troubleshoot a stalled workflow?","limit":3}}
See the API and MCP reference for routes, tools, and documentation lookup.
The API/MCP server has no built-in authentication. Keep it on loopback or behind trusted access control. Quickstart credentials and storage are disposable demo settings, not production configuration.
Documentation
Metadata
Release files for oxidizer-lite 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| oxidizer_lite-0.2.2.tar.gz | 139.2 kB | With provenance | Details for oxidizer_lite-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| oxidizer_lite-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for oxidizer_lite-0.2.2-py3-none-any.whl |
Total release size: 298.8 kB
Release files / oxidizer_lite-0.2.2.tar.gz
| Download URL | oxidizer_lite-0.2.2.tar.gz |
|---|---|
| Size | 139.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
87f93455a5055904b749ee1ece53882c89ab57f959e02f1ff28b4b303dc74889
|
|
BLAKE2b-256 checksum How to use checksums |
9c277768d8d125f7d2a63e8168074f518885136156dc46c8147df069e6348c09
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.
Transparency logRelease files / oxidizer_lite-0.2.2-py3-none-any.whl
| Download URL | oxidizer_lite-0.2.2-py3-none-any.whl |
|---|---|
| Size | 159.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e23ad59f38aadf8b897459afad09f962def391d0013a0a9c150b82e0754572cd
|
|
BLAKE2b-256 checksum How to use checksums |
78a3d665e71d6543943a142726f566125953ebc11c07846a9556a53167298b04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.
Transparency logSecurity for oxidizer-lite 0.2.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for oxidizer_lite-0.2.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.