Jaws Deploy is a deployment automation platform. It takes the build artifact your CI server already produced and walks it through your environments - Dev, Staging, Production, customer-specific tiers - in a controlled, repeatable, auditable way.
The distinction matters. CI systems are good at building and testing code. They are not designed to model environments, scope variables by deployment context, or replay the same deployment plan against ten machines with consistent behaviour. Jaws Deploy is.
What it actually does
A project in Jaws Deploy owns a deployment process - an ordered list of steps that runs against an environment. Each environment is wired to one or more targets: machines running the Jaws Deploy Agent, or managed cloud services. Steps resolve variables scoped to the current environment, target, or tag.
The shape stays the same regardless of scale. The same model handles a single Windows box hosting an IIS site and a hundred-target fleet across regions.
The objects you'll work with
Who it's for
Teams that ship to multiple environments and want the deployment story to be a structured, replayable plan rather than a CI script that grew teeth. Common shapes: small DevOps teams running Windows or mixed stacks, agencies repeating deployments across client environments, regulated organisations that need an auditable record of what reached production.
Where it sits in your stack
Jaws Deploy lives between your CI system and your infrastructure. CI keeps doing builds and tests. Jaws Deploy owns the deployment lifecycle: release creation, promotion through environments, variable resolution, target execution, and history.