# Integrations

Source: https://www.jawsdeploy.net/platform/integrations

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).

## Keep your CI. Add deployment.

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.

**CI hands off the artifact**

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.

**Deploy steps call anything**

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.

- **TeamCity**: A native build step creates releases and triggers deployments directly from a TeamCity pipeline without custom scripting.
- **GitHub Actions, GitLab CI, Jenkins**: Trigger Jaws Deploy from any CI system that can run a shell command or make an HTTP call. The REST API and PowerShell SDK cover both.
- **PowerShell SDK**: The PowerShell SDK wraps the full Jaws Deploy API. Use it in build steps, automation scripts, or anywhere PowerShell runs — Windows or Linux.
- **REST API**: Every Jaws Deploy action is available over REST. Create releases, trigger deployments, query history, and manage environments from any language or toolchain.

> **PowerShell in deploy steps - Outbound integration is just PowerShell.**
> 
> 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.

## Explore further

- [REST API docs](https://www.jawsdeploy.net/rest-api)
- [Jaws Deploy Agents](https://www.jawsdeploy.net/platform/agents)
- [PowerShell SDK](https://github.com/JawsDeploy/powershell-sdk)
- [Python SDK](https://github.com/JawsDeploy/python-sdk)