Koru Stack Makes Infrastructure Compile-Time Data

Koru Stack’s compelling idea is making deployment topology part of the application’s static graph, rather than another runtime configuration layer. It is currently more promising as a compiler-native infrastructure experiment than a full Aspire competitor.

• –Service references automatically derive dependency and health-gated edges, reducing drift between connection strings and `depends_on`.
• –Build variants can remove development services entirely from production artifacts and reject duplicate, dangling, cyclic, or gated references early.
• –Reusing Koru’s existing grammar and Liquid templating keeps the DSL small, but requires teams to learn Koru to own their infrastructure.
• –The major gap is operational UX: dashboards and telemetry are absent, while process spawning and compiler-tracked stack lifecycle remain planned.
• –The package already paid off as a compiler stress test, surfacing seven defects that were fixed and regression-pinned.