Design Partner Program · App Vitals
Have the people who built Shipwright run it on your pipeline.
Shipwright is free and MIT-licensed — install it yourself in five minutes. But if you'd rather have autonomous delivery working in your repo in weeks, not quarters, Dan and Dave install it, tune it to your stack, and run alongside your team for the first 8–10 weeks. A small cohort at a time, hands-on.
Why a design partner, not a fullstack vendor
The delivery layer.
Not another fullstack agent.
Shipwright is a thin, open-source harness on top of Claude Code — it ships zero model or inference code, runs entirely in your cloud on your codebase, and your code never leaves your control. That means a design-partner engagement is not a lock-in bet.
Transparent trial
The whole harness is open source. You can read exactly how it works before you commit to anything — nothing hidden behind a black box.
Clean, cheap exit
If you ever leave, you lose Shipwright the engine — plan → queue → loop. But you keep everything it wrote: your CLAUDE.md, docs, skills, and commands, all vanilla Claude Code primitives that keep working on plain Claude Code. Leaving Devin, Cursor, or Copilot strands your whole workflow in their stack. Leaving Shipwright leaves your repo better than it found it.
Learn it, then own it
The point of the partnership is that you end it able to run the loop yourselves. We hand off; we don't create a dependency.
Who this is for
A real backlog you want shipped.
- → Remote-first, US-based teams
- → Engineering orgs of roughly 40–100+ engineers
- → Already a Claude Code shop (or ready to become one) — adopting Shipwright is an extension, not a migration
- → A real backlog you want shipped, not a demo you want to watch
If you need a committee to try this, we're probably too early for you. If you don't — let's run Shipwright on your pipeline.
The engagement
8–10 weeks.
Install → Tune → Hand off.
Weeks 1–2
Install & configure
Dan and Dave stand up Shipwright in your cloud, wire it to your repo, CI, and review process. Metrics dashboard live.
Weeks 3–6
Tune to your stack
We customize the knobs, extensions, plan/queue config, and review policy to your product and your codebase — the last-mile infrastructure work off-the-shelf tools don't touch. Agents start shipping real, human-reviewed PRs against your backlog.
Weeks 7–10
Hand off
Your team owns the loop. We step back to advisory. You keep everything — the harness config, the primitives, the artifacts.
What you get: the software plus Dan and Dave, hands-on, for the whole pilot — not a license and a docs link.
Proof
We ship with it every day.
On our own metrics.
85 PRs a week
Planned and reviewed by humans, written and shipped by agents — the same pipeline running against App Vitals' own business.
Read the post →393 PRs in two weeks
We personally opened fewer than 10 of them.
Read the post →In production in six weeks
Clients running it in production — not a demo, not a branch nobody merges.
Read the post →FAQ
Questions, answered honestly.
Is Shipwright free?
Yes — MIT-licensed, install it yourself, no accounts. The design-partner program is the done-with-you option for teams who want it running fast and tuned to their stack.
Does our code leave our environment?
No. Shipwright runs entirely in your own cloud, on your codebase.
What happens when the pilot ends?
You own the loop and keep every artifact it produced. The exit is clean by design.
What if we just want to try it ourselves first?
Do — that's the invitation. shipwrightharness.com, five-minute quickstart. Come back when you want it tuned.
Book a 30-minute discovery call with Dan and Dave.
No pitch deck, no pressure — an honest assessment of whether autonomous programming fits your shape.