In this section
Product / explicit boundaries

Roadmap

The roadmap describes capability boundaries and acceptance targets, not delivery dates. A feature moves to available only when its contract, failure behavior, and relevant acceptance path are documented and tested.

Status definitions

StatusMeaning
AvailableUsable in the current alpha with a documented contract and acceptance path.
In developmentActively being hardened or expanded; expect compatibility work and contract review.
PlannedDirection accepted, but implementation has not started or is not committed.
DeferredIntentionally out of the current product boundary.

Available today

Resolver preflight is available. Additive heimdall.agent/v8 fields report system DNS, direct port-53 interception, or private-mount fallback together with NSS/nscd evidence, AppArmor/userns settings, inspection argv, and deterministic pre-exec blockers.

Relay CA preflight is available. Generated CAs and leaves carry strict signing extensions; incompatible material makes agent readiness false before execution.

Current platform scope. Published packages and the complete transparent backend remain Linux-only. Apple silicon can run the reduced cooperative macos-explicit backend from source. macos-interpose is active daemonless fallback research. The optional Network Extension control/provider prototype is deferred, source-only, and excluded from release artifacts.

In development

Track 01

Daemonless lifecycle

The NixOS current/LTS, Ubuntu 24.04, and Debian 13 gates cover descendants, all owner signals, concurrent sessions, parent-death recovery, exact authorization, both TLS modes, and loader-configured OpenSSL mapped after exec. Extend this lifecycle matrix without retaining setup privilege at runtime.

Track 02

Agent event evidence

Per-run health and per-flow explanations now have strict offline schemas. Expand beyond the available bounded, recoverable, provenance-linked HTTP/1 evidence only where new parsers remain conservative and directly usable with Linux tools.

Track 03

Proxy compatibility

Ubuntu 24.04 proves namespace-free fake DNS under its AppArmor restriction. Debian 13 proves the private resolver mount for its stock nss-resolve status-action chain without host resolver edits or a session D-Bus service. Expand namespace-free compatibility across NSS modules and caches that bypass port 53.

Track 04

TLS boundaries

Relay mode preserves ALPN and SNI, supports long-lived streams, emits strict CA/leaf extensions, and rejects incompatible CA material before execution without claiming pinning or client-certificate mTLS support.

Track 05

Capture analysis

Expand the available flow explanation, boundary, direction, and blob inspection plus private run-store retention only where the result remains bounded, provenance-linked, and agent-readable.

Track 06

Performance and observability

Low-cardinality run summaries and repeatable current/6.6 LTS NixOS, Ubuntu 24.04, and Debian 13 real-eBPF performance baselines are available. Repeat the contracts across more distributions.

Track 07

Native ARM completion

Artifact hygiene is available. Run the defined aarch64 current/Linux 6.6 LTS real-eBPF gates on an ARM Linux executor, then add that result to the release transaction.

Track 08

macOS backend

The native-accepted macos-explicit source backend stays available. Next, build the separately named macos-interpose fixture around authenticated DYLD interposition, TCP connect, libc resolver calls, and the foreground relay; add Proxyman-style child-only runtime proxy/trust adapters. Keep Hardened Runtime, SIP, static code, alternate APIs, unsupported descendants, strict scope, UDP, and TLS unavailable until native evidence proves each boundary. The heimdall.macos.control/v1 and NETransparentProxyProvider prototype remains deferred source research with release_included=false; package and release construction must not build or include it. Read the design →

The proxy-compatibility track keeps resolver reporting aligned with runtime decisions while expanding namespace-free compatibility only for NSS stacks that genuinely reach port 53.

Deferred boundaries

Heimdall is not a cluster controller, replacement VPN, desktop traffic dashboard, host-wide always-on system proxy, or universal TLS decryption layer. Shipping, signing, installing, or activating the checked-in macOS Network Extension prototype is also deferred. These are deliberate exclusions that keep the command wrapper reliable and inspectable.

How to influence the roadmap. Open an issue with a minimal command, configuration, kernel/runtime details, and the output of heimdall agent. Discuss the boundary and acceptance criteria before opening a pull request.