──INTRODUCING:/~\Oxidv0.2.0

Infrastructure as Code, Reimagined

A standalone IaC engine that parses your .tf files natively and talks directly to Terraform providers via gRPC. No terraform binary. No baggage.

Get Started >>

Apache-2.0 · Written in Rust · Built by ops0.com

──WATCH IT RUN

13 resources across VPC, S3, EC2 — independent branches execute in parallel, dependents fire the instant their deps complete.

oxid apply — 13 resources — 36s

──FEATURES

Better Building Blocks=Better Infrastructure

Built from the ground up in Rust for speed, correctness, and a developer experience that stays out of your way.

01

Native HCL Parsing

Reads your existing .tf files directly with hcl-rs. No wrapper, no transpilation. Your Terraform configs work out of the box.

02

Event-Driven Parallelism

Resources start the instant their dependencies complete. No wave-based batching -- every millisecond counts.

03

Direct gRPC to Providers

Communicates directly with AWS, GCP, Azure, and every Terraform provider via the tfplugin5/6 protocol.

04

SQL-Queryable State

State lives in SQLite (or PostgreSQL for teams). Query your infrastructure with full SQL instead of parsing JSON.

05

Drift Detection

Run oxid drift to instantly detect configuration drift across your entire infrastructure. Know before it breaks.

06

Import Existing State

Migrate from Terraform seamlessly. Import your .tfstate files and keep going without missing a beat.

──PERFORMANCE

Wave-Based vs Event-Driven Execution

Both tools walk the dependency graph in parallel. Terraform batches resources into synchronized waves — the next wave waits for the entire previous wave to finish. Oxid fires each resource the instant its specific dependencies are satisfied. No idle gaps.

Terraform

wave 2
wave 3
wave 4
wave 5
wave 6
S3 Bucket
S3 Versioning
S3 Encryption
S3 Policy
S3 Notification
VPC
Subnet
IGW
Security Group
Route Table
RT Assoc
Lambda
EC2 Instance
API Gateway
S3
VPC
Compute
batched waves

Oxid

S3 Bucket
S3 Versioning
S3 Encryption
S3 Policy
S3 Notification
VPC
Subnet
IGW
Security Group
Route Table
RT Assoc
Lambda
EC2 Instance
API Gateway
S3
VPC
Compute
event-driven

Honest take: For small configs, both tools spend 90% of the time waiting on cloud APIs — timings are nearly identical. The gap widens on deeper dependency chains, larger infra, and higher parallelism settings.

──STATE INSPECTION

Query Your State Like a Database

Terraform dumps everything. Oxid stores state in SQLite/PostgreSQL — query exactly what you need with SQL.

Terraform
$
Oxid
$

Why SQL? Oxid stores every resource in a real database (SQLite locally, PostgreSQL for teams). Filter by type, status, module — join across resources. No more piping terraform show through grep and jq.

──COMPARE

How Oxid Stacks Up

Architectural differences that make Oxid faster and more transparent.

FeatureTerraform / OpenTofuOxid
Execution ModelWave-based (batch)Event-driven per-resource
ParallelismResources in same wave wait for slowestDependents start instantly when deps complete
State BackendJSON file or remote backendSQLite (local) / PostgreSQL (teams)
Config LanguageHCL onlyHCL + YAML
Provider ProtocolWraps binary / shared libDirect gRPC (tfplugin5/6)
Queryable Stateterraform showFull SQL queries
LicenseBSL / MPLApache-2.0

──PIPELINE

How it Works

From HCL parsing to state persistence, every step is designed for speed and transparency.

01

Parse

Reads .tf files using hcl-rs, extracting resources, data sources, variables, outputs, and providers.

02

Build DAG

Constructs a dependency graph from explicit depends_on and implicit expression references.

03

Start Providers

Downloads provider binaries from registry.terraform.io, starts them as subprocesses, connects via gRPC.

04

Plan

Calls PlanResourceChange on each provider to compute diffs, showing you exactly what will change.

05

Apply

Event-driven DAG walker executes resources as dependencies are satisfied, calling ApplyResourceChange via gRPC.

06

Store State

Persists resource attributes to SQLite database, queryable with full SQL at any time.

──ARCHITECTURE

A Clean Pipeline from Config to Cloud

.tf / .yaml files
HCL Parser
WorkspaceConfig
DAG Builder
Resource Graph
AWS
GCP
Azure
gRPCgRPCgRPC
SQLite / PostgreSQL State

──QUICK START

Up and Running in Seconds

Works on Linux and macOS. No dependencies required.

01Install
curl -fsSL https://raw.githubusercontent.com/ops0-ai/oxid/main/install.sh | bash
02Initialize providers
oxid init
03Preview changes
oxid plan
04Apply infrastructure
oxid apply

More Commands

oxid destroyTear down infrastructure
oxid state listList all managed resources
oxid driftDetect configuration drift
oxid query "SELECT * FROM resources"SQL-query your state
oxid graph | dot -Tpng -o g.pngVisualize the dependency DAG

──OPEN SOURCE

Ready to Drop the Baggage?

Oxid is free and open source. Start managing your infrastructure with a faster, more transparent engine.