// Guides
Jaws Deploy guides
Practical, technical guides for deploying with Jaws Deploy - from your first release to running Stack on your own infrastructure.
// Getting Started
What is Jaws Deploy?
A short tour of what Jaws Deploy does, who it's for, and how it sits between CI and production.
Read guide
Getting Started with Jaws Deploy
Sign up, create a workspace, model your first environment, install an agent, and ship a release.
Read guide
Jaws Deploy vs. Traditional Deployment Tools
Why teams move away from "deploy.ps1 in the build server" once they have more than one environment to keep honest.
Read guide
The Role of Jaws Deploy in CI/CD Workflows
Where Jaws Deploy fits next to your CI tool, what each owns, and how they hand off.
Read guide
// CI/CD Integration
Integrating Jaws Deploy with TeamCity
Use the TeamCity plugin or PowerShell SDK to create releases after every successful build.
Read guide
Integrating GitHub Actions
Trigger releases from a GitHub Actions workflow using the REST API or PowerShell SDK.
Read guide
Integrating GitLab CI
Call Jaws Deploy from a `.gitlab-ci.yml` job to ship every build to a staging environment.
Read guide
Integrating Jenkins
Wire a Jenkins pipeline step that creates and optionally deploys a Jaws Deploy release.
Read guide
Integrating Azure Pipelines
Call Jaws Deploy from an Azure DevOps pipeline using a service connection and an API key.
Read guide
Integrating CircleCI
Trigger Jaws Deploy releases from a CircleCI job using the REST API.
Read guide
// Projects, Steps & Targets
Projects and Deployment Logic
What a project is, what it owns, and how its deployment process holds together.
Read guide
Project Steps Explained
The unit of work inside a deployment process - ordered, scoped, and re-runnable.
Read guide
Step Templates in Action
Take a step you've copy-pasted three times and turn it into a versioned template with inputs.
Read guide
Custom Script Modules
Share PowerShell helper functions across every script step in every project.
Read guide
Environments and Targets
Model deployment stages and the machines or cloud services that receive deployments.
Read guide
Cloud Targets
Deploy to Azure Web Apps and other managed services without installing an agent.
Read guide
Managing Machines
Register, group, and decommission Windows and Linux machines as deployment targets.
Read guide
Azure Web App Deployment
Walkthrough: configure an Azure Web App cloud target and deploy a release to it.
Read guide
// Variables & Configuration
The Power of Variables
Why scoped variables remove most of the configuration pain teams hit in CI scripts.
Read guide
Variable Resolution Rules
How Jaws Deploy picks a value when several scopes match the same variable.
Read guide
Nested and Referenced Variables
Compose values from other variables and reuse them across steps and config files.
Read guide
// Releases & Lifecycles
Creating Releases
What a release captures, when to create one, and how to drive creation from CI.
Read guide
Executing Deployments
What happens when a release is deployed - target resolution, step execution, and live logs.
Read guide
Release Progression with Lifecycles
Define the ordered phases a release must walk through before it reaches production.
Read guide
Deployment History and Auditing
Use deployment history to investigate incidents, prove what shipped, and answer auditor questions.
Read guide
// Packages
Using Package Feeds
How feeds, packages, and deployment steps fit together in a release.
Read guide
Built-in Package Store
Push artefacts straight to the Jaws Deploy built-in feed without standing up a separate registry.
Read guide
Connecting External Feeds
Point Jaws Deploy at the artefact server you already run - NuGet, Artifactory, S3, Azure Artifacts.
Read guide
// Self-Hosting & Admin
Installation Guide (Jaws Deploy Stack)
Install the self-hosted Jaws Deploy Stack on a Windows or Linux server.
Read guide
Installing the Jaws Deploy Agent
Install the agent on Windows and Linux machines so they can receive deployments.
Read guide
Setting Up a Proxy for Stack
Run Jaws Deploy Stack behind a reverse proxy (nginx, IIS, Apache) with HTTPS.
Read guide
Adding OIDC to Stack
Authenticate Stack users through Entra ID, Okta, Google Workspace, or any OIDC provider.
Read guide
Service Accounts and Automation
Create non-human identities for CI tools and automation scripts that call the REST API.
Read guide
// Migration & Comparisons