// Platform
Connect any CI system to release orchestration without rewriting build pipelines. Jaws Deploy integrates inbound via API and PowerShell SDK — and reaches outward from deploy steps using PowerShell (v.5 and v.7).
Jaws Deploy does not ask you to replace TeamCity, GitHub Actions, GitLab CI, Jenkins, or Azure DevOps. Build pipelines are good at compiling, testing, and packaging — that work stays where it is. What changes is what happens after the artifact is ready: release creation, environment promotion, variable resolution, target execution, and deployment history all move to a system built for that purpose.
// Trigger Jaws from CI
When a build passes, trigger Jaws Deploy to create a release and start the deployment. Use the TeamCity plugin, a PowerShell SDK call, or a direct REST API request — whichever fits the build tool already running the pipeline.
// Reach out from deploy steps
Jaws Deploy runs PowerShell 5 and PowerShell 7 natively inside deployment steps. Deploy logic can call REST APIs, send notifications, update ITSM tickets, run health checks, or trigger downstream systems — all as part of the release flow.
Deploy steps in Jaws Deploy run PS5 or PS7. That makes outbound integration straightforward — call an API, update a ticket, notify a channel, run a health check. No plugin to install, no integration layer to maintain. Just PowerShell code that runs as part of your deployment.
// Next step