Back to browse
GitHub Repository

Praxis is a declarative infrastructure platform that lets you declare AWS cloud resources in CUE and automatically plan, import, continuously reconcile, and manage them with durable, exactly-once execution, all without running a Kubernetes cluster.

0 starsGo

Praxis – AWS infrastructure automation, without the complexity

by shirvan·Jun 11, 2026·2 points·0 comments

AI Analysis

MidBold Bet

Terraform without state files, but alpha with zero stars and established competitors.

Strengths
  • Restate durable execution journals every AWS call so crashes resume without duplicates.
  • Single-writer resource objects eliminate locking and state file contention.
  • Five-minute continuous reconciliation corrects drift or reports it per resource.
Weaknesses
  • Alpha stage with zero stars means no real-world production validation yet.
  • Terraform, Pulumi, and Crossplane already solve this with massive ecosystems.
Target Audience

DevOps engineers managing AWS infrastructure without Kubernetes

Similar To

Terraform · Crossplane · Pulumi

Post Description

Hi everyone,

Praxis is the result of a decade of my experiences and frustrations working with IaC and infrastructure management in general. It aims to solve the core needs like templating, state management, continues reconciliation, and lifecycle management without needing a complex setup like Kubernetes or bolting on additional tooling like CI pipelines.

It uses a durable execution engine (https://restate.dev) to create and manage digital twins, it means every AWS call is journaled, so a crash mid-provision resumes where it stopped instead of leaving half-applied state. Each resource is a single-writer object, so there's no locking and no state file. Continuous reconciliation is just a durable timer that re-checks every resource every five minutes and either fixes drift or reports it, your choice per resource. The whole thing runs from one Docker Compose stack.

You can declare resources in CUE templates (typed, validated, with real constraints), and there are 45 AWS drivers so far across networking, compute, storage, IAM, and monitoring. Using CUE gives us a lot of goodies like policy enforcement out of the box and our templates doc (https://github.com/shirvan/praxis/blob/main/docs/TEMPLATES.m...) explains the choice of using CUE in more detail.

It's in early development and not everything is tested on a live AWS account, so use at your own risk.

Similar Projects