Why teams switch

The teams we talk to usually mention one of three things: the renewal price, the time spent keeping the platform running, or features they pay for and don't use. If none of these apply to you, there may be no reason to move.

We ran our own deployments on Octopus for years before building Jaws Deploy, so the concepts carry over almost one to one.

What works the same

Projects One project per deployable thing. The deployment process lives on the project and is scoped to environments.
Environments and lifecycles Environments are the stages a release moves through. Variables scope to them, and lifecycles set the order.
Deployment processes An ordered list of steps built from templates and scripts. If you can describe an Octopus process, you can rebuild it here.
Releases and promotion A release is an immutable snapshot that you promote through environments. Rolling back means deploying the previous release.

What's different

  • Pricing. Professional is €45/month with 10 machines, then €2 per machine. Fleet is €199/month with 40 machines, then €1 per machine. The free plan has 2 machines. Octopus Cloud Professional starts at $4,330/year before machine add-ons (octopus.com/pricing, October 2026).
  • No runbooks. Ad-hoc operations tasks run as script steps in a project.
  • Tenants are supported. Each tenant has its own variables, machines and deployment history. See tenants.
  • No manual intervention step. Approvals happen outside Jaws Deploy, for example in your CI tool or change process.
  • A smaller template library. Built-in templates cover packages, IIS, Windows services, Azure Web Apps, Azure Key Vault and scripts. Anything else is a PowerShell or Python script, which you can turn into your own step template.

How a migration goes

A migration is mostly mechanical, but it isn't automatic. The Fleet and Dedicated plans include migration help from our team.

  • Read your Octopus setup through its REST API: projects, environments, variable sets and deployment processes.
  • Recreate each project in Jaws Deploy with the same steps and variables.
  • Rebuild custom step templates. The inputs carry over. Script bodies may need small syntax changes.
  • Change the CI call from creating an Octopus release to creating a Jaws Deploy release. See the example below.
  • Cut over one project at a time. Start with a non-critical project and run both tools in parallel for a sprint.

How long it takes

For a small team it's typically 1–2 weeks of part-time work. With 10–30 projects, expect 4–8 weeks. Hundreds of projects take a quarter or more and need someone leading the migration.

The CI change

If you create Octopus releases from CI today, this is the part of the build script that changes.

# Before: Octopus CLI
octo create-release `
    --project  "Checkout.Web" `
    --version  "2026.10.4.$buildNumber" `
    --server   "https://octopus.acme.example" `
    --apiKey   $env:OCTO_API_KEY `
    --deployTo "Staging"

# After: Jaws Deploy PowerShell SDK (github.com/JawsDeploy/powershell-sdk)
Import-Module ./JawsDeploySdk.psm1
$env:JAWS_API_LOGIN    = "<service account id>"
$env:JAWS_API_PASSWORD = $env:JAWS_API_KEY

Invoke-ReleaseAndDeployProject `
    -projectId       "<project id>" `
    -version         "2026.10.4.$buildNumber" `
    -environmentName "Staging"

When to stay on Octopus

  • Your team relies on runbooks more than on deployment processes.
  • You depend on community step templates that Jaws Deploy doesn't have.
  • You have internal tools built on the Octopus REST API. Jaws Deploy has its own API with a similar model but different endpoints.
  • The team is happy and the price works for you.

Try it with one project

Create a free workspace and rebuild one Octopus project: its deployment process and variables, not its history. If that takes less than a day and feels familiar, the rest of the migration will follow the same pattern.

Or ask about migration and we'll rebuild one project with you in an hour.