Aspire (formerly .NET Aspire)
Aspire is an open-source (MIT) multi-language, code-first toolchain for building, running and deploying distributed applications. You describe how services, frontends, containers, databases, caches and their connections fit together in code; the Aspire CLI runs the whole app locally, exposes OpenTelemetry-based observability, and carries the same definition into deployment. The docs are explicit about what it is not: an application framework, a cloud provider or a production runtime.
Name and history
Aspire began as “.NET Aspire”, a .NET-only stack. Press coverage (InfoQ, Visual Studio Magazine, Microsoft’s devblog) reports that Microsoft dropped “.NET” from the name and made the platform polyglot with Aspire 13 in late 2025. The current README and docs at aspire.dev use only “Aspire”. The repository now lives at microsoft/aspire; the old dotnet/aspire path redirects to it.
Repository snapshot (GitHub API, 2026-11-20)
| Item | Detail |
|---|---|
| Repo | microsoft/aspire, C#, MIT |
| Created | 2023-09-25 |
| Activity | last push 2026-11-20; latest release v17.0.0 (2026-11-18) |
| Size | 6,439 stars, 1,040 forks |
| Release channels | Stable (production), Staging (prerelease from the release branch) and Dev (latest from main, less tested) |
Core concepts (aspire.dev)
- AppHost: the code-first model of your system and the single source of truth for its architecture. It can be written in C# (
apphost.cs) or TypeScript (apphost.ts). You start everything withaspire run. - Resources: what you add to the AppHost: projects, executables, containers, databases, caches and cloud services.
- Relationships: references, dependency ordering (
WaitFor) and service discovery, so code reaches its dependencies without hardcoded addresses and the same code works locally and in production. - Integrations: prebuilt packages for components such as PostgreSQL and Redis, plus app types such as Python apps, Node apps and Vite frontends.
- Dashboard: one place for logs, traces, metrics and resource state (see below).
- Workloads in many languages: the AppHost can orchestrate C#, JavaScript, Python, Go, Java, Rust, PowerShell and more.
A README example in C# adds a Redis cache, a Node API that references it, and a Vite frontend that references the API:
var builder = DistributedApplication.CreateBuilder(args);
var cache = builder.AddRedis("cache");
var api = builder.AddNodeApp("api", "./api", "src/index.ts")
.WithReference(cache).WaitFor(cache)
.WithHttpEndpoint(env: "PORT").WithExternalHttpEndpoints();
builder.AddViteApp("frontend", "./frontend").WithReference(api).WaitFor(api);
builder.Build().Run(); The dashboard
The Aspire Dashboard shows application logs, distributed traces and metrics from apps that export OpenTelemetry. With an AppHost it also shows resource state, health checks, console output and configuration, and it can persist resources and telemetry so you can compare finished runs. It can also run standalone as an OTLP viewer for any app that sends OpenTelemetry data (including Python and Node.js), started with the Aspire CLI or a container image; standalone mode has no resource start, stop or restart controls. Dashboard data can include secrets in environment variables, so restrict access to it.
Deployment
The same app model deploys with three CLI commands:
aspire publishemits target-specific artifacts for a one-way handoff to other tooling.aspire deploygenerates the output, resolves parameters and applies the changes directly.aspire do <step>runs a named pipeline step and its dependencies.
Built-in targets (aspire.dev): Docker Compose (publish and deploy; Compose output is docker-compose.yaml plus a .env file), Kubernetes (publish and deploy to any cluster in the current kubectl context), Azure Kubernetes Service, Azure Container Apps and Azure App Service (each with deploy support). Where a target lacks deploy support, you publish its artifacts and apply them with external tools.
Installing and tooling
Install the Aspire CLI with the install script from aspire.dev (a PowerShell one-liner on Windows, a shell script on Linux and macOS), choosing the stable, staging or dev channel. For coding agents, Aspire provides skill files, an MCP server and aspire agent init, which give an agent structured access to your app model, logs, traces and resources; see model-context-protocol. The docs also cover testing, including testing in CI.
Where it fits
Aspire replaces hand-written local wiring and Docker Compose files for multi-service apps, and gives development-time observability. It targets kubernetes and Docker (DOCKER) at deploy time, and its Azure targets sit within microsoft-azure.
Sources
- aspire.dev: What is Aspire, Deploy with Aspire and Dashboard overview (2026-11-20)
- microsoft/aspire README and GitHub API (2026-11-20)
- The rename and the Aspire 13 timing come from press coverage: InfoQ on Aspire 13 and Visual Studio Magazine, seen as search results.