IN DEVELOPMENTProduction enrollment isn’t open yet
shipstead.

For software vendors · Customer-hosted applications

Ship updates.
Keep customers
in control.

Your software runs on their servers. Shipstead brings the release, their approval and the deployment record into one workflow.

Check your fitSee the workflow

Built for a defined Docker application. No sales call required.

SHIPSTEAD / DISPATCH

ONE RELEASE. CLEAR AUTHORITY.

02.05.08Application release
  1. 01
    Vendor signsExact images & deployment plan
  2. 02
    Customer approvesThe change & execution window
  3. 03
    Host executesHealth checks & operation record
ILLUSTRATED WORKFLOW NOT LIVE STATUS

You have the release.
They have the infrastructure.

Keep the handoff from becoming the whole job.

When each customer hosts a separate copy, an update becomes a chain of files, approvals, checks and follow-ups. Shipstead gives that chain a repeatable structure, with the customer still deciding when their installation changes.

A release has three owners

Know who can
change what.

  1. You define the release.

    Sign the application package and deployment intent outside the hosted control plane. Publish a specific change, not a general permission to run commands.

  2. Your customer gives permission.

    They review the exact plan and its execution window. Downloading an image or an installation kit does not approve a deployment.

  3. The host leaves a record.

    The scoped broker executes the approved operation. Health checks and journals make completed, failed and uncertain outcomes explicit.

The actual product

See each installation.
Know the next step.

See host readiness and the next setup step in a single installation view. This is the working local application, using test data.

Shipstead setup page showing installation requirements, download and host connection status
Local test workspace · setup and connection checks View full size ↗
Walk through an installation

The planned offer

One application.
Up to 25 installations.

$149 / month, proposed

For vendors with a repeatable application package and customer-owned hosts. Customer infrastructure stays separate.

See the scope and exclusions ↗

Make the numbers yours

Does it buy back
enough time?

Compare the update effort you spend today with the effort you expect to keep. Include setup time and extra infrastructure.

Calculate the tradeoff ↗

An estimate of engineering capacity, not a promise of savings.

Field notes

Before the next update.

All guides ↗
01 / Operations

Updating software on customer-owned servers

Separate release preparation, permission and execution. 02 / Control

What should a customer actually approve?

Define the exact change before asking for a yes. 03 / Recovery

Plan a Docker update before touching production

Images, persistent data and recovery are different jobs.

Start with your application

See where your
application fits.

Find out whether your customer hosts and update workflow match Shipstead’s planned scope.

Check compatibility

No email. No call. Results stay in your browser.