RootGuard

Reliability before feature count

1.0 has arrived.
What's next?

The roadmap took RootGuard from a functional alpha stack to a recoverable, auditable, and stable Docker appliance. Every milestone had explicit acceptance criteria - all of them are met.

Release train

Step by step toward stability.

  1. FOUNDATION

    Functional alpha core

    AIO setup, protected DNS chain, login, Unbound lifecycle, local zones, and update foundations are available.

    DELIVERED
  2. 0.1 ALPHA

    Reproducible public alpha

    Versioned components, GHCR multi-arch, clean installs, real control-plane rollback, an accessible theme-aware WebGUI with global search, and documented limits are delivered and superseded starting with 0.1.0-beta.1.

    DELIVERED
  3. 0.2 DNS

    Essential Unbound configuration

    Guided conditional forwarding, private domains, reverse zones, a typed host inventory with a table view, FRITZ!Box import, a shared reusable guided-workflow pattern, export/import of the complete resolver configuration, and a directive-by-directive unbound.conf import assistant are delivered, along with six end-to-end scenario tests against a real Unbound container. Access-rule conflict detection stays deliberately post-1.0, since the guided surface it would need doesn't exist yet.

    DELIVERED
  4. 0.3 INTEGRATION

    Integrate AdGuard, do not rebuild it

    The native AdGuard interface remains responsible for filters, clients, and statistics. Protected access, automatic bootstrap, bundled status including the AdGuard version, contextual links into the native interface, a dedicated RootGuard-branded block page with a real, per-request block reason, and cross-service diagnostics across the full DNS chain are delivered.

    DELIVERED
  5. 0.4 OPS

    Operations, storage, and recovery

    A central area for bounded, redacted service logs, a scannable Stack page that inspects cleanup only on request, and a dedicated Backups page with explicit import paths, encrypted age full backup, and guided restore onto a clean installation are delivered. Verified snapshot/restore and power-loss tests, plus a disaster-recovery runbook rehearsed on a second host, round out 0.4.

    DELIVERED
  6. 0.5 SEC

    HTTPS, security, and accessibility

    Reverse-proxy documentation (Caddy, Zoraxy, Nginx Proxy Manager, HAProxy), a session inventory with targeted revocation, login/recovery and destructive-action rate limiting and audit logging, a threat model, automated security scans in CI, and reviewed WCAG 2.2 AA and reduced-motion support are delivered.

    DELIVERED
  7. 0.6 BETA

    Immutable release pipeline

    Signed images, SBOM, provenance, a migration framework, a compatibility matrix, and live-verified upgrade tests are delivered, starting with 0.1.0-beta.1.

    DELIVERED
  8. 0.9 RC

    Feature freeze and endurance test

    The 30-day DNS endurance test ran unattended with real update and restore exercises and finished clean: 4175 probes, 95% pass rate, no new failure class. Performance/memory baseline, a final accessibility and security review, a frozen platform/support policy, a no-prior-context documentation review, and the 1.0 migration guide are complete; the full install/upgrade/restore matrix is green. A final release-blocking-defect review has now run three times, most recently a dedicated correctness pass across the entire codebase - 32 findings, all fixed.

    DELIVERED
  9. 1.0 STABLE

    Stable single-node Docker appliance

    Repeatable installation, operation, update, and recovery with signed artifacts and matching documentation.

    DELIVERED

UNBOUND · 0.2

Configuration with explicit safety boundaries.

Not every directive belongs in a free-form WebGUI field. RootGuard separates a fixed security baseline, guided settings, controlled expert mode, and permanently blocked values.

GuidedConditional forwarding, private domains, reverse policies, PTR, host inventory, FRITZ!Box import, cache/logging, protocol mode, and classification/adoption of a hand-written unbound.conf delivered
Fixed baselineDNSSEC hardening, root hints, trust anchor, identity hiding, and safe listeners
Expert modeOnly narrowly supported directives with policy, preview, checkconf, and rollback
BlockedIncludes, file paths, remote control, trust-anchor replacement, and arbitrary commands

Definition of done

Done means demonstrably done.

SafetyNo browser input expands Docker or file access without control.
RecoveryEvery change and update has a tested recovery path.
TestsNormal operation, limits, failure, and recovery are tested automatically.
DocumentationWebGUI, translations, documentation, and development status agree.
Scope for 1.0: A reliable single-node Docker appliance. Bare metal, multi-node, high availability, and external identity providers follow after 1.0.