What does "per-run capacity" mean?

Each plan defines the maximum total size of source data that can be included in a single sync run. For example, if you have a 10 TB plan, you can migrate any bucket up to 10 TB in one run. If your bucket is 3 TB, the entire 3 TB is included in the plan. The limit resets for every new run.

Does the limit reset every run?

Yes. The capacity limit applies per run and is not cumulative. If you have a 10 TB plan, you can run unlimited migrations of up to 10 TB each — including retries and resumes.

Can I run multiple migrations at the same time?

Yes. You can run multiple migrations concurrently. Each run simply needs to fit within your plan's per-run capacity.

How is the run size calculated?

The total size is calculated from all discovered source objects during the planning phase. Objects are counted based on their source size, even if they already exist at the destination.

What happens if my bucket exceeds my plan's capacity?

During planning, files are scheduled until the next file would exceed your plan’s capacity. That file and all subsequent files are excluded from the run. You can then upgrade your plan or split the migration into smaller runs.

Can I upgrade my plan?

Yes. You can purchase a higher-capacity license at any time.

What’s the difference between the Free plan and the 50 GB trial?

The Free plan includes a permanent 10 GB per-run capacity with no expiration. The 50 GB trial is a 30-day license available after registration, allowing you to evaluate larger migrations before purchasing.

Does retrying or resuming a migration consume extra capacity?

No. Each run is evaluated independently. As long as the total source size fits within your plan’s per-run capacity, you can retry or resume without penalty.

Do you charge for bandwidth or transferred bytes?

No. Godwit Sync is licensed based on per-run capacity, not on transferred bandwidth.

What S3-compatible providers are supported?

Godwit Sync works with any S3-compatible storage, including AWS S3, MinIO, Cloudflare R2, Backblaze B2, DigitalOcean Spaces, Wasabi, and self-hosted object storage.

Do I need a license for --plan-only mode?

Yes. Capacity is evaluated during the planning phase. The same per-run limit applies whether you run --plan-only or execute the migration.

Is my data processed through your servers?

No. Godwit Sync runs locally in your environment. Data flows directly between source and destination. Nothing passes through our infrastructure.

Does the license work offline?

Yes. The license is a signed file that is validated locally and does not require continuous internet access.

What payment methods do you accept?

We accept all major credit and debit cards via Stripe.

Production-Grade Data Migration

On-the-Fly Object Storage Migration at Scale

Godwit Sync is a predictable, plan-first migration tool for moving data between S3-compatible object stores. Built for control, observability, and production safety.

Get Started See How It Works

Rate Limited

Control read/write throughput

Resumable

Continue from exact checkpoint

No Local Staging

True stream-to-stream copy

Source Safe

Never overload source systems

Plan-First Approach

Plan Before You Move

Know exactly what will happen before any data moves. Generate migration plans, inspect them, modify as needed, and execute with confidence.

Deterministic migration plan generation (--plan-only)
Migration plans stored in SQLite
Inspect, modify, and reuse plans
Predictable execution every time

$ godwit sync \
    --source s3://production-bucket \
    --dest s3://backup-bucket \
    --plan-only --brief

────────────────────────────────────────
  PLAN CREATED
────────────────────────────────────────
  ✓ Run-ID: run-1770316589731184186
  ✓ Objects analyzed: 685,234
  ✓ Objects to transfer: 620,205
  ✓ Objects skipped: 65,029
  ✓ Data to transfer: 40.03 GB
  ✓ Data skipped: 4.7 GB
────────────────────────────────────────

End-to-End Checksums

Validate every object with real MD5 hashes, not just ETAGs.

Deterministic Runs

Identical inputs produce identical results—no hidden randomness.

Parallel, Controlled Transfers

High throughput without sacrificing stability or safety.

Metadata Fidelity

Preserve object metadata exactly as stored at the source.

Exact Object Ordering

Stable, predictable processing order across runs.

Chunk-Level Recovery

Recover from partial uploads without corrupting large files.

Production Safety

Production-Safe by Design

Built for environments where downtime and data loss are not options. Rate-limit operations, resume from any point, and keep your source systems healthy.

Rate-limited reads and writes
True stream-to-stream copy (no local staging)
Resume from exact file or chunk
Large file stability
No overload of source systems

Full Observability

Observable & Verifiable

Know exactly what's happening at every moment. Integrate with your existing monitoring stack and verify every byte after it lands.

Verbose CLI UI with real-time progress
REST status endpoint
Prometheus-compatible metrics
Predictable duration and progress estimates
Built-in MD5 verify after every transfer

Status Endpoint

JSON endpoint for real-time sync progress — objects, bytes, ETA, and storage class breakdown.

Learn more

Prometheus Metrics

Counters, histograms, and gauges for deep observability. Plug into Grafana or any Prometheus-compatible stack.

Learn more

# Reusable run IDs resume interrupted syncs
$ godwit sync \
    --resume --brief --run-id run-daily-backup \
    --source s3://prod \
    --dest s3://backup

────────────────────────────────────────
  RESUME READY
────────────────────────────────────────
  ✓ Run-ID: run-daily-backup
  ✓ Total objects: 20
  ✓ Uploaded objects: 15
  ✓ Objects left: 5
  ✓ Data to transfer: 2.00 GB
────────────────────────────────────────

# Automation-friendly exit codes
$ echo $?
0

Scale & Automation

Built for Repetition and Scale

Design once, run many times. Perfect for scheduled syncs, multi-bucket operations, and CI/CD integration.

Reusable run IDs
Incremental syncs
Multiple buckets and paths
Automation-friendly CLI workflows

Data Movement, Done Right

Godwit Sync turns risky storage migrations into planned, observable, production-safe workflows for modern infrastructure teams.

Plan-First Execution

Preview changes before they happen. No surprises in production.

Operational Transparency

Built-in metrics and monitoring. Integrate with your existing stack.

CLI as an API

Scriptable, automatable, and CI/CD ready from day one.

Automation Over Ad-Hoc

Designed for repeated, scheduled operations—not one-off scripts.

Predictable Cost & Time

Know transfer times and resource usage before you start.

Hybrid & On-Prem Ready

Works with any S3-compatible storage, cloud or self-hosted.

$ godwit sync \ --source s3://production-bucket \ --dest s3://backup-bucket \ --plan-only --brief ──────────────────────────────────────── PLAN CREATED ──────────────────────────────────────── ✓ Run-ID: run-1770316589731184186 ✓ Objects analyzed: 685,234 ✓ Objects to transfer: 620,205 ✓ Objects skipped: 65,029 ✓ Data to transfer: 40.03 GB ✓ Data skipped: 4.7 GB ────────────────────────────────────────

Production-Safe by Design

Built for environments where downtime and data loss are not options. Rate-limit operations, resume from any point, and keep your source systems healthy.

Rate-limited reads and writes

True stream-to-stream copy (no local staging)

Resume from exact file or chunk

Large file stability

No overload of source systems

Observable & Verifiable

Know exactly what's happening at every moment. Integrate with your existing monitoring stack and verify every byte after it lands.

Verbose CLI UI with real-time progress

REST status endpoint

Prometheus-compatible metrics

Predictable duration and progress estimates

Built-in MD5 verify after every transfer

# Reusable run IDs resume interrupted syncs $ godwit sync \ --resume --brief --run-id run-daily-backup \ --source s3://prod \ --dest s3://backup ──────────────────────────────────────── RESUME READY ──────────────────────────────────────── ✓ Run-ID: run-daily-backup ✓ Total objects: 20 ✓ Uploaded objects: 15 ✓ Objects left: 5 ✓ Data to transfer: 2.00 GB ──────────────────────────────────────── # Automation-friendly exit codes $ echo $? 0