v0.1.0-alpha.1
Current · pre-alpha- Version re-baseline. This project is pre-launch; releases through v1.26.3
Roadmap
What's shipped, what's next.
Shipped releases below are generated straight from the two repos' CHANGELOGs (last synced 2026-08-03) — Community is at v0.1.0-alpha.1, the Enterprise Srenix Enterprise binary at v0.2.0-alpha.1. The open-items list is hand-curated and verified against repo state on the same date.
Pre-alpha re-baseline. The project
re-baselined to 0.x-alpha (pre-launch). Community is at
v0.1.0-alpha.1; Enterprise Srenix Enterprise is at
v0.2.0-alpha.1 (adds RAG-live, deep-RCA, tier chaining). Earlier versions
(Community ≤ v1.26.3, paid ≤
v1.22.4) were internal pre-alpha
iterations and are marked pre-release — nothing has shipped GA yet.
Current release
The current shipped release per track. Every feature from the prior iterations is rolled into it. Every entry is parsed from the repo CHANGELOG at build time — nothing here is hand-copied.
Srenix Community — agentic-sre
CommunitySrenix Enterprise
Paidv0.2.0-alpha.1
Current · pre-alpha- Added: Firecrawl-grounded deep-RCA LLM investigator: performs structured root-cause analysis using live public web research (read-only cluster tools + web research via an LLM-synthesized, client-redacted query). Flags:…
- Added: Deep-RCA artifact persisted to srenix_investigations Qdrant collection; cross-cycle retrieval injects prior root-cause context into the T1 proposer.
- Added: Root-cause forwarded into every AI tier (T0–T3) via a <root_cause> prompt block so all tiers reason from the same root cause; T1 also receives T0 enrichment in the same block.
- Added: Ticket-closure outcome recorded to RAG/audit store (verdict=cleared, delivery=ticket-closed) so future short-circuit lookups benefit from resolved findings.
- Changed: --rag-short-circuit now defaults ON (previously default off). Inert without --memory-store-url.
- Changed: Community dependency remains pinned to v1.26.3 (no bump — the new code uses only existing Community symbols).
v0.1.0-alpha.1
Current · pre-alpha- Added: one-click Silence (SC: the Srenix Enterprise half)
- Changed: Community dependency pinned to v1.26.3 (adds pkgai.SilenceTokenClaims + SignSilenceToken/VerifySilenceToken + MintSilenceLinks, the approval-server silences create RBAC, and the /silence Ingress path).
Pre-alpha iteration history
Releases numbered 1.x before the 2026-06-18 re-baseline. These were internal pre-alpha iterations mis-numbered as 1.x; their work is folded into v0.1.0-alpha.1 above. Kept here for transparency — these are not the current version. Generated from the CHANGELOGs.
Srenix Community — agentic-sre 1 legacy 1.x
v1.26.3 (pre-rebaseline)
- Added: one-click Silence links on the LIVE watcher "needs human" Slack path (Community foundation)
Srenix Enterprise 2 legacy 1.x
v1.22.4 (pre-rebaseline)
- Added: one-click Silence (SC: the Srenix Enterprise half)
- Changed: Community dependency bumped to v1.26.3 (adds pkgai.SilenceTokenClaims + SignSilenceToken/VerifySilenceToken + MintSilenceLinks, the approval-server silences create RBAC, and the /silence Ingress path).
v1.22.3 (pre-rebaseline)
- Fixed: human-approved executions spuriously failing on missing rollback (OF1/CF1)
- Changed: Community dependency → v1.26.2
Open items
Living list of pending work as of 2026-08-03, each verified against repo state before listing. Engineering items reference the in-flight claims-fulfillment plan (P6.x); items on the product/marketing track don't block shipped capability.
| Item | Why it's still open | When |
|---|---|---|
| Idle-resource & GPU cost analyzer | Correlates what is allocated (requests, device-plugin reservations, nodeSelectors/taints) against what is actually used, and flags the negative-ROI trap of provisioned-but-idle capacity — most acutely reserved GPUs sitting at near-zero utilization. Proposes reclaim / scale-down / rightsize through the same signed-approval path, entirely in-cluster with no egress | Q3 2026 · Community |
| Zero-day exposure scan + patch sourcing (batch) | A scheduled (not real-time) pass that inventories the cluster's real component versions, correlates them against newly-disclosed zero-days/CVEs, and uses deep-RCA web research to locate the actual fix (patched version, vendor advisory, or service pack) before filing a remediation proposal. Batch by design: the research takes time | Q4 2026 · Enterprise |
| End-of-life inventory + upgrade/migration planner | Inventories installed software/infra versions and flags components approaching or past end-of-life (unsupported Kubernetes, deprecated APIs, EOL base images, DB/runtime versions), cross-references vendor EOL calendars via deep-RCA research, and proposes a concrete upgrade-or-migrate plan with sequencing — runs as a scheduled batch alongside the zero-day scan | Q4 2026 · Enterprise |
| Cosign-signed container images + Srenix Enterprise artifacts | The SBOM (CycloneDX) + cosign signing pipeline shipped (P6.2) and Community binary checksums are cosign-signed and Rekor-logged in the v0.1.0-alpha.1 line, but container-image and Srenix Enterprise artifact signing are still pending CI billing restoration | P6.2 — checksum signing live; image signing pending |
| Hosted playground | The "Try it now" path currently lands on quick-start; the live playground route is a coming-soon stub | P6.8 — in flight |
| OLM / OperatorHub publish | Operator bundle manifests + bundle-smoke CI gate exist; the bundle has not been published to OperatorHub | Next operator milestone |
| M7 phase 2 — per-probe dispatch | The GVRWatcher interface shipped (v0.1.0-alpha.1 line), but the watcher still runs every probe on every trigger (static watchedGVRs loop) | Q3 2026 |
| M7 phase 3 — controller-runtime reconciler per probe | ~10-day effort + separate design doc | Q4 2026 |
| Anonymized run-log opt-in collection | GTM day 14–90 milestone (no engineering blocker) | Product/marketing track |
| Multi-tenant SaaS variant | One binary serving N customer clusters; not yet designed, needs an RFC | Post first 3 paying customers |
| Deep-RCA Firecrawl egress domain allowlist (operator-configurable) | Current implementation uses default Firecrawl endpoint; operator-specified domain allowlist is a hardening follow-up | Next hardening sprint |
This page is the public roadmap. For shipped detail, see the release notes
and CHANGELOG.md that ship with each Community
release, or
get in touch.