// Platform overview
Deployment automation from release to target.
Jaws Deploy turns build artifacts into repeatable deployments. Model projects, environments, variables, targets, and release promotion once, then run the same process through cloud or self-hosted infrastructure.
CI stays focused on build and test.
TeamCity, GitHub Actions, GitLab CI, Jenkins, Azure DevOps, PowerShell, or the REST API can hand over a release when the artifact is ready.
Deployment logic lives with the platform.
Projects, steps, variables, feeds, environments, and targets are modeled in one place instead of being scattered across scripts and build jobs.
Operations get a clear release trail.
Every deployment has status, logs, target activity, and history, so production changes are easier to review and repeat.
// Core model
The platform connects the pieces teams already use.
Jaws Deploy does not try to replace your CI system. It becomes the deployment control plane after the build is complete.
// Platform components
Pick the right shape for your deployment environment.
Use these pages when you need details about platform components.
// Why teams move deployment here
Deployment deserves its own system of record.
Build pipelines are good at compiling, testing, and packaging code. Deployment needs different primitives: environments, promotion, target health, scoped configuration, release history, and operator visibility.
Jaws Deploy gives those primitives a dedicated home without forcing teams into a large platform migration.
Make the next release easier to explain.
Start with Jaws Deploy Cloud, or talk to us about self-hosted Jaws Deploy Stack for private infrastructure.