​
Today: state manager & backend proxy

OpenTaco today is just a small subset of features that we believe to be essential for any TACO solution. It is not yet ready to replacement Terraform Cloud or Spacelift in production. We are starting with the “core” aka “Layer 0”:
  • Stateless self-hostable service that can be used on top of existing S3 backend bucket
  • Units CRUD and locking with granular RBAC
  • HTTP backend proxy (GET/POST/PUT/LOCK/UNLOCK) compatible with Terraform’s http and S3 backend types
  • Dependencies: digest-only edges in __opentaco_system and taco unit status.
  • CLI and Terraform provider for management operations.
The service is stateless and stores tfstate in S3 via a bucket‑only adapter (with an in‑memory fallback for local demos).

​
Work in progress

The bulk of the work is still ahead - we are not even calling it v0.1 just yet. When we get to #3 (VCS integration + UI) it will be feature-complete enough to be called a TACO; at this point a subset of TFC users will be able to start switching to OpenTaco v0.1
  1. Remote runs (CLI-triggered remote execution)
  2. GCS and other object storage providers in addition to S3
  3. VCS integration + UI (repo connections, units, runs)
  4. Drift detection
  5. OPA Policies
See Roadmap for more details on our plans.