From dev to production, seamlessly.
Generate deployment artifacts with aspire publish, then deploy anywhere — Azure, Docker, Kubernetes, or your own pipeline.
How deployment works
Aspire's deployment model is built on two complementary commands that keep your workflow clean, secure, and extensible.
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 referenceaspire deploy
Resolves parameters, applies configuration, and executes the deployment to your target environment. Works with Azure Container Apps, Kubernetes, and more.
View deploy referenceCustomize 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 moreDocker Compose
Generate production-ready Docker Compose files with parameterized environment variables. Perfect for self-hosted and on-premises scenarios.
Learn moreKubernetes
Produce Kubernetes Helm charts that reflect your AppHost model. Deploy to any K8s cluster with your existing toolchain.
Learn moreCustom integrations
Build your own publish or deploy integrations. The system is fully extensible — any hosting integration can participate in the deployment model.
Learn moreKey concepts
Parameter placeholders
Published assets use placeholders for secrets and environment-specific values. Shape stays consistent, values are injected at deploy time.
Learn about parametersState caching
Speed up repeated deployments with state caching. Aspire tracks what has changed and only updates what it needs to.
Explore cachingAzure security
Follow best practices for securing your Azure deployments — managed identities, key vaults, network isolation, and more.
Security best practicesShip with confidence
Your local AppHost model is your deployment model. No configuration drift, no surprises — just consistent, repeatable deployments.