Aspire Roadmap - Q2 2026 Update (June 2026) #18023
Pinned
davidfowl
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Aspire Roadmap - Q2 2026 Update (June 2026)
It’s been a few months since our Q1 roadmap update, and since then we’ve shipped Aspire 13.3 and Aspire 13.4. This update looks back at the original roadmap: what we shipped, what changed shape, and what still needs work.
As always, thank you for the issues, discussions, PRs, Discord conversations, streams, bug reports, and feedback. The roadmap continues to be directional, but your feedback keeps shaping what we prioritize and how we build it.
🎉 Major Accomplishments
The biggest milestone this cycle is that TypeScript AppHost is now generally available. The original roadmap described Aspire becoming a code-first, polyglot toolchain, and 13.4 is a major step toward that vision: C# and TypeScript are now both first-class ways to model Aspire apps, with generated SDKs, TypeScript documentation parity, and new TypeScript samples.
Deployment also moved forward significantly.
aspire publishandaspire deployare now generally available, Docker Compose is stable,aspire destroygives us a real teardown story, and Kubernetes/AKS support advanced with Helm-based deployment, Gateway API, cert-manager, Kubernetes manifests, external Helm charts, and Azure Application Gateway for Containers support.The CLI and dashboard continued to mature as the main operational surfaces for Aspire. Since the last update, we shipped
aspire dashboard run,aspire integration list/search, CLI-side log and telemetry search, richer resource commands, browser logs/screenshots/network capture, command result notifications, structured dashboard filtering, the dashboard AI Agents entry point, and the newaspire docs apigroup for browsing, searching, and retrieving Aspire API reference docs (C# and TypeScript) straight from the CLI.AI workflows also evolved beyond the original MCP-server shape. Aspire now has
aspire agent, richer dashboard and telemetry APIs for agents, and the newmicrosoft/aspire-skillsbundle of workflow skills you can install with a singleaspire agent init.And we held Aspire Conf 2026! Sessions are available on the Aspire YouTube playlist. Explore the session list Aspire Conf: Sessions.
🧑💻 Local Developer Experience
.localhostDNS Support🧪 Testing Experience
📊 Dashboard
🛠 Tooling
🌐 Polyglot Support
🤖 AI Workflows
☁ Hosting Integrations
Authentication
Azure Integrations
🚀 Deployment
Environment Support
Deployment Target Status
CI/CD Integration
📚 Content & Community
🔮 Looking Ahead
Looking back at the original roadmap, the biggest remaining gap is still testing. We have useful building blocks like
aspire wait, dashboard export/import, and easier dashboard hosting in test environments, but the full testing experience — live dashboard during tests, capture and replay from CI, partial AppHost execution, request redirection/mocking, and coverage — still needs first-class work.The large-app inner loop also remains a major focus. Run subsets, debugging .NET projects inside containers, and multi-repo support continue to come up from teams building larger distributed systems.
For the dashboard, we’ve made a lot of progress on search, filtering, telemetry, command results, browser diagnostics, and AI-agent workflows, but external storage and custom layouts/grouping are still not done.
On hosting and deployment, Kubernetes and AKS continue to move quickly, but the remaining original asks include auth providers, Event Grid, APIM, Azure Functions on App Service, fuller environment support, and generated CI/CD pipelines.
The encouraging part is that many of the foundations are now in place: a stronger CLI, TypeScript AppHost GA, richer resource commands, deployment primitives, dashboard APIs, and agent-ready workflows. The next phase is about closing the remaining gaps and making the whole system feel cohesive end to end.
📚 Resources
Beta Was this translation helpful? Give feedback.
All reactions