Get started
Explore Crewship
GitHubGet started

Use case · Operations

Big migration

Long work keeps checkpoints, so a crew can resume or fork instead of starting over.

  1. Mission
  2. Checkpoints
  3. Resume or fork
Copy 1CheckCopy 2Cutover

How the crew does it

Illustrative workflow. Times, data and outcomes are examples.

Mission: move billing to the new cluster
AveryRuns long jobs with checkpoints.
Copy 1 finished, checkpoint saved3h
Server restarted, resuming from checkpoint
Copy 2 matches by checksum2h
Both copies match. Ready for cutover on 15 December. You can fork from any checkpoint if you want to try a different plan.

What you need

  • Missions
  • Journal

Set it up

The guide walks through the routine, the crew and the credentials step by step.

Read the guide
All use cases
02:00nightly-maintenance
Nightly maintenanceBackups, cleanups and reports run at night. Repeat failures trip a breaker and land in your Inbox.

Your crew is waiting.

Install Crewship on your own machine in a few minutes.

Get started Read the docs