Who this is for

Small teams usually start deploying from CI: a deploy job after the build, then a script, then several scripts and a wiki page that explains them. It works until the person who wrote it is on holiday.

Jaws Deploy moves that logic into projects, environments and variables that the whole team can read, with a record of every deployment.

The first week

Day 1: first deployment Create a workspace, install the agent on a staging server, create a project and deploy a package. Plan on about 30 minutes.
Day 2: environments Add Development, Staging and Production. Tag your servers. Move connection strings and other settings out of the script into variables scoped per environment.
Day 3: releases from CI After a successful build, your CI creates a release through the REST API or PowerShell SDK and deploys it to Staging. The live log shows each step as it runs.
Days 4–5: promotion and rollback Promote the same release to Production. To roll back, redeploy the previous release.

What you no longer maintain

  • The deployment script. Built-in steps handle packages, IIS, Windows services and Azure Web Apps. What's left goes into a versioned step template.
  • A separate artifact server. The built-in package feed stores your build artifacts.
  • "Which version is on Staging?" The dashboard and deployment history show it.
  • The rollback runbook. Redeploy the previous release.
  • Digging through CI logs. Every deployment records who ran it, what it deployed and its full log.

Pricing for small teams

The free plan has 2 machines, 5 projects and 1 workspace, with no time limit. Professional is €45/month for 10 machines and 20 projects, then €2 per extra machine. Most small teams stay on one of these two plans. See pricing for the full table.

As the team grows

The environments, variables and release process you set up in week one still work with thirty people. New team members can read the deployment history to see how things ship.

We host and update Jaws Deploy Cloud. If you later need it on your own infrastructure, Jaws Deploy Stack is the same product, self-hosted, on the Dedicated plan.

When it isn't the right fit

  • You have no servers and deploy one app to one PaaS from a single CI workflow. Your CI is enough.
  • You need a GitOps controller that keeps Kubernetes clusters in sync with a repository.
  • You orchestrate thousands of microservices across several clouds with traffic shifting.

Try it with one project

Create a free workspace, connect a project you already ship, and deploy it once to a non-production environment. If anything takes longer than it should, tell us where.