Cross Platform

Cross-platform solution based on .net 8 and PowerShell 7. All deployment steps and custom scripts are based on PowerShell 7.

Windows and Linux Agents supported!

• More scripting languages are on our roadmap for late 2024/early 2025.
• Kubernetes (YAML, Helm and Kustomize) is on our roadmap for early 2025.

Agent Installation

Extremely easy to set up. No server installation. Just install Jaws Deploy Agent on your target machines (windows and linux). New Agents will send a handshake to the JawsDeploy Server - just accept it in the web app and the machine is ready for use.

Agents update themselves.

Configure your own

• projects (apps)
• environments
• machines
• tags (for organizing machines) - more info below
• global variables (reusable across projects)
• project variables
• script modules (code snippets reusable across projects) not implemented yet
• step templates

Tag and keep track

Create your own tag sets to group machines per application, geographical location, hardware specs and any other criteria you need.

E.g.:

• “region:Europe”, “region:SouthAmerica”
• “role:applicationServer”, “role:DbServer”

Push or Pull Packages and Builds

• Push builds securly into our built in NuGet feed or grab them from an existing remote NuGet feeds
• Work with .zip / .tar.gz or any other bundles you like
• Specify credentials to access external feeds which require authentication
• e.g. TeamCity, Azure Devops etc.

Define your deployment as a list of steps

Every step can be scoped to specific environments, machines or tags (i.e. it will be executed when the defined scope matches current machine and environment)

Define steps by either:

• Writing a one-off PowerShell script - full control and a bit more complexity
• Re-use deployment logic via our existing step templates - pre-written scripts that hide the complexity, and let you control the step logic with just a few inputs

Step templates :

• You can import existing step templates (just copy and paste a JSON step definition)
• You can create your own step templates
• Step templates can be customized with variables and more custom scripts (e.g. “Deploy package” template can be re-used in multiple projects, and on top of that you can define more custom logic per project that will get executed before the deployment, after configuration files are transformed and finally after files are deployed to the destination folder)
• We will release a step template library with loads of pre-made logic (Azure, AWS, Docker and many more) - in Q1 2025