Get started

From zero to your first Shipment.

Choose managed or self-hosted, learn the five concepts that matter, and build a workflow that can move with you.

Choose a route

Run it your way.

Both paths use the same core workflow model. The difference is who operates the environment.

Self-host the core

$0

Use the public Docker image or build from source. You provide the runtime, MongoDB, mail service, and operational care.

Read installation docs

Plan a bespoke setup

Let’s talk

Have unusual topology, scale, or integration requirements? Describe the workflow and we’ll discuss the right shape.

Contact Harbormaster

Learn the model

Five concepts. One clear vocabulary.

Harbormaster’s components are named for the work of coordinating a safe, visible journey.

HARBOR

A modular unit that performs one discrete piece of work.

LANE

A workflow step that runs a Harbor and points to what comes next.

CHARTER

A complete execution path made from one or more Lanes.

MANIFEST

The configuration and state passed from one Lane to another.

SHIPMENT

The record created when work starts and completes, including its result.

SALVAGE PLAN

The Lane that runs when a Shipment returns a non-zero exit code.

Build your first flow

Compose, ship, observe.

Start with one useful unit of work. Add complexity only when your operation needs it.

01

Define a Harbor

Wrap a command, API call, transformation, or remote action as a discrete service.

02

Connect the Lanes

Set the successful followup and the Salvage Plan for work that fails.

03

Start a Shipment

Run it from the dashboard or an authenticated hook, then inspect the result.

Harbormaster
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.