Aspire Deployment

From dev to production, seamlessly.

Generate deployment artifacts with aspire publish, then deploy anywhere — Azure, Docker, Kubernetes, or your own pipeline.

Deploy your first app Read deployment overview

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 Container Apps

Deploy directly to Azure Container Apps with a single command. Aspire provisions infrastructure, configures networking, and resolves secrets automatically.

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

Produce Kubernetes manifests and Helm charts that reflect your AppHost model. Deploy to any K8s cluster with your existing toolchain.

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

Deployment manifest

Understand the JSON-based manifest format that captures your entire application topology — resources, bindings, parameters, and inputs.

View manifest format

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 local AppHost model is your deployment model. No configuration drift, no surprises — just consistent, repeatable deployments.

Deploy your first app Browse integrations