ops0-ai / oxid

What is oxid?

Oxid is a Rust-powered standalone infrastructure-as-code engine that drops in as an open-source Terraform alternative, parsing your .tf and .tf.json files natively while connecting directly to providers via gRPC—no Terraform binary required. It delivers event-driven execution where resources start instantly after dependencies finish, stores queryable state in SQLite or PostgreSQL, and handles drift detection with simple CLI commands like `oxid plan`, `apply`, `destroy`, `drift`, and `query "SELECT * FROM resources"`. Think oxidation reduktion in IaC: it simplifies workflows by merging HCL with YAML configs for mixed setups.

Why is it gaining traction?

Unlike Terraform's wave-based batches that wait for the slowest resource, Oxid's per-resource parallelism cuts apply times dramatically, especially in deep dependency graphs. Developers love the full SQL access to state—no more wrestling JSON dumps—plus visualization via `oxid graph | dot` and import from .tfstate files. Its Apache-2.0 license and direct provider protocol make it a lightweight, embeddable oxid tool github option, akin to standalone github copilot for IaC without ecosystem lock-in.

Who should use this?

DevOps engineers maintaining Terraform configs who want faster applies and SQL-powered state introspection for audits or scripting. Teams building CI/CD pipelines tired of installing Terraform binaries everywhere, or solo infra devs experimenting with AWS/GCP/Azure providers in resource-heavy projects. Ideal for oxidative stress from slow plans in monorepos with hundreds of resources.

Verdict

Promising beta for Terraform drop-ins, but with 13 stars and 1.0% credibility score, treat it as experimental—test rigorously on non-prod stacks first. Strong docs and real AWS support make it worth watching for production escape hatches.

(198 words)