INFRAWEAVER ALPHA

infraweaver/roadmap

Roadmap

Taken from the project's own planning documents, not from a wish list. Nothing here has a date attached, because this is a spare-time alpha and a date would be a lie.

Next up

From NEXT-FEATURES-PLAN.md. Small and mid-sized work with a clear shape.

SRV backfillReconcile service records that exist in the cluster but never made it into DNS.SMALL
Replica floorSay how many of each pod should exist, per app and per pod, and have the platform hold that line.SMALL
Per-workload placementPlacement rules exist but are not reachable per workload from the console. They should be.MEDIUM
Plugin updates with rollbackThe WordPress connector updates core; it should update plugins too, with a rollback that works.LARGE
Fail state with resolve and retryA failed fleet operation should be a state you can resolve and retry, not a log line you have to read.MEDIUM
Signed plugin download with handshakeDownload the connector from an external site and have it pair with your platform automatically. Security-sensitive by construction.LARGE

The longer arc

From ENTERPRISE-WAVE-PLAN.md. These are the ten workstreams that would take InfraWeaver from a homelab platform to something an organisation could defend in an audit. They are directional, and several will change shape before they are built.

Boundaries and evidence

  1. Access boundariesWorkspaces with scope-enforced RBAC on every surface, not only on the ones that remembered.
  2. Evidence-grade audit pipelineAn audit trail that is worth something to someone other than the person who wrote it.
  3. Directory syncSCIM 2.0 provisioning and, more importantly, deprovisioning.
  4. Compliance engineSigned evidence packs generated from the running cluster rather than assembled by hand.

Control and scale

  1. Public API v1Service-account tokens, an iwctl CLI, and an OpenTofu provider — the console stops being the only way in.
  2. Sealed modeA provable air gap plus signed offline update bundles.
  3. Addon platformSigned, versioned extensions that a third party can publish and you can install.
  4. Multi-clusterOne control plane over several clusters, from the session cookie down.
  5. Supply-chain verificationProvenance gates and SBOMs, so "where did this image come from" has an answer.
  6. SLOs and game daysError budgets that mean something, and failure drills you actually run.

WHAT IS NOT ON THIS LIST

A hosted service, a paid tier, and a support contract. InfraWeaver installs on hardware you own and reconciles from a git server inside your own network; that property is the point, and none of the work above changes it.