Aspire deployment overview

From dev to production, seamlessly.

Use aspire publish to emit deployment artifacts as a one-way handoff, or use aspire deploy to generate, resolve, and apply changes directly. Both workflows run the AppHost as part of the deployment pipeline to produce target-specific output.

Deploy your first appDeploy with Aspire

How deployment works

Aspire’s deployment model is built on two complementary commands that keep your workflow clean, secure, and extensible.

1. aspire publish

   Transforms your AppHost model into integration-specific artifacts — Docker Compose files, Kubernetes manifests, Bicep templates, and more. Secrets remain as parameterized placeholders.

   View publish reference
2. aspire deploy

   Resolves parameters, applies configuration, and executes the deployment to your target environment. Works with Azure Container Apps, Kubernetes, and more.

   View deploy reference
3. Customize your pipeline

   Build custom deployment pipelines that plug into the same model. Use CI/CD variable injection, scripts, or your own toolchain to resolve parameters and apply changes.

   Custom pipelines

Deploy anywhere

Aspire is not locked to a single cloud. Your local dev topology translates directly to production infrastructure through hosting integrations.

Azure

Choose Azure Container Apps or Azure App Service. Aspire provisions Azure infrastructure, resolves parameters, and applies the deployment from your AppHost model.

Learn more

Docker Compose

Generate production-ready Docker Compose files with parameterized environment variables. Perfect for self-hosted and on-premises scenarios.

Learn more

Kubernetes

Publish Helm charts or deploy directly to any Kubernetes cluster — self-managed or AKS — with full publish and deploy support.

Learn more

Custom integrations

Build your own publish or deploy integrations. The system is fully extensible — any hosting integration can participate in the deployment model.

Learn more

Key concepts

Parameter placeholders

Published assets use placeholders for secrets and environment-specific values. Shape stays consistent, values are injected at deploy time.

Learn about parameters

State caching

Speed up repeated deployments with state caching. Aspire tracks what has changed and only updates what it needs to.

Explore caching

Azure security

Follow best practices for securing your Azure deployments — managed identities, key vaults, network isolation, and more.

Security best practices

Ship with confidence

Your AppHost model drives deployment output for each target platform. No configuration drift, no surprises — just consistent, repeatable deployments.

Deploy your first appBrowse integrations