Quality work starts itself.

Ship plugs into the places your team already works and picks up quality work as it happens — from code changes to bug reports to production issues.

Every change gets tested.

Ship analyzes each PR, understands its blast radius, identifies what needs testing, and runs the right regressions before merge.

  • Impact analysis
  • Test coverage
  • Regression runs
  • Defect detection
Shipship/change intelligence
LIVE
acme / storefront · #1234Fix checkout session handling
fix/checkout-session+42−183 files
Blast radius mapped3 affected flows
CheckoutPaymentsAuth
Targeted regressions12 / 12 completed
Regression caught before mergeExpired sessions block the payment step.
P1

Every bug gets investigated.

When a bug lands in Linear, Jira, Slack, or your service desk, Ship reproduces it, captures evidence, and investigates the likely root cause.

  • Automatic triage
  • Bug reproduction
  • Step-by-step evidence
  • Root cause analysis
Shipship/investigations
LIVE
JIRA / BUG-842just now
Checkout never finishes

“The spinner keeps going after my session expires. I can’t complete my order.”

Ship
Ship picked it upReproduce → Trace → Diagnose
Reproduced00:38 elapsed
session replay
Processing…
00:1200:38
01Restore session02Retry payment03Request stallsReplay & network trace attached
LIKELY ROOT CAUSE87 auth/refresh.ts token === null

Production teaches Ship what to test next.

Ship analyzes real user sessions for anomalies, reproduces suspicious behavior, and turns what it learns into permanent regression coverage.

  • Session analysis
  • Anomaly detection
  • Automatic reproduction
  • Regression coverage
Shipship/production signals
LIVE
SESSION INTELLIGENCESmall signal. Permanent coverage.
1,284sessions analyzed
01anomaly found
Last 15 min
Repeated payment attemptsSession #8f2a · 14:37:08
14:3014:3514:4014:45
Anomaly→ Reproduced→ Covered
Ship
NEW REGRESSION TESTCheckout recovers expired sessionsAdded to suite · runs on every future PR

No test plan to trigger. No QA queue to manage. Ship sees the work and starts testing.

Ship joins your existing stack.

Keep your developers in GitHub, your bugs in Linear, and your conversations in Slack. Ship works across the tools already running your engineering process.

  • Code & CI

    Understand every change and test the deployed product.

  • Issues & support

    Turn incoming bugs into reproduced, actionable issues.

  • AI coding agents

    Hand verified root causes and context directly to Claude or Codex.

Ship makes every release safer — and cheaper.

Ship doesn’t just run more tests. It catches more regressions earlier, improves coverage as your code changes, and reduces the cost of quality with every release.

of regressions caught before merge

72%

Ship finds defects closer to the code change that introduced them — before they become release blockers or production bugs.

change-to-test coverage

94%

See whether the parts of your product changing in each release are actually being exercised by tests.

ShipRelease Quality Report

Release 284

Analyzed
92/ 100
Quality Score↑ 8vs. previous release
  • 31code changes analyzed
  • 47impacted tests identified
  • 3regressions caught
  • 1production anomaly reproduced
  • 2regression tests added
ESTIMATED DEFECT COST AVOIDED$18.4K
Coverage ↑ 12% · Cost / release ↓ 18% · Escaped defects ↓ 36%
faster bug resolution

68%

Automatic reproduction, evidence capture, and root-cause analysis dramatically reduce the time between “something broke” and “here’s what to fix.”

lower quality cost per release

43%

Spend less on test execution, maintenance, debugging, and AI as Ship learns what matters and runs the right work automatically.

The goal isn’t more testing. It’s fewer escaped defects, faster releases, and lower cost per release.

Your AQE can start today.

Connect Ship to your engineering workflow and let it begin learning your product.

Connect your stack

Add your codebase, deployed environment, issue tracker, and team tools.

Give Ship context

Connect your tests, documentation, tickets, designs, and historical bugs so Ship understands how your product should behave.

Let Ship start working

Ship begins reviewing changes, reproducing bugs, running regressions, and surfacing issues automatically.

Quality shouldn’t slow down shipping.

“It feels like adding another QA engineer without adding another queue.”
David Jin

Clari

“We went from ‘can you reproduce this?’ to having the reproduction already attached.”
Kerri Barton

Skillibrium

“Our engineers spend less time figuring out what broke and more time fixing it.”
Bessy Alcerro

Codexitos

Start with Ship. Scale with your releases.

One credit system across every Ship workflow. Pay for the testing and analysis Ship does, never for seats.

  • 1 credit = $0.025
  • Unlimited users on every plan
  • Root cause and autofix included

Free trial

See Ship test your product before you pay anything.

$0for 15 days

3,000 credits one-time

Start 15-day trial

Includes

  • Everything in Starter
  • Enough for a crawl, a code analysis and your first test runs
  • Unlimited users

Starter

For small engineering teams getting started with autonomous QA.

$49/ month

2,000 credits every month

Start 15-day trial

Includes

  • Unlimited users
  • 1 GitHub repository
  • 5 parallel test runs
  • PR impact analysis
  • Bug analysis and reproduction
  • Regression and post-merge testing
  • Root cause and autofix
  • Live sessions, fair use
  • Additional credits at $0.025

Enterprise

For quality engineering across products and teams.

Custom

Volume credits by contract

Talk to sales

Everything in Pro, plus

  • Volume pricing
  • SSO and enterprise controls
  • On-premise deployment
  • Dedicated mobile devices
  • Custom parallel runs
  • Dedicated support

[ Trusted Clients ]

[ What a credit buys ]

One credit, every workflow.

Every plan uses the same rates. Credits come off your monthly allowance first, then your additional credits.

Testing

  • Test run

    Ship executes your test in a real browser, with video, trace and screenshots.

    1 credit per 4 steps

  • PR impact analysis

    Maps what a pull request changes, which flows it touches and which tests to run.

    10 credits per PR

  • Bug analysis

    Reproduces a reported bug, captures evidence and adds a regression test when it confirms one.

    15 credits per bug

Setup and coverage

  • Code analysis

    Reads a repository once so Ship understands your codebase and generates tests from it.

    1,000 credits per repository

  • Crawl

    Explores your application, maps its pages and flows, and generates test cases.

    500 credits per crawl

  • Requirement upload

    Turns a requirements document into test cases.

    20 credits per upload

  • Ask a document

    Ask questions of your uploaded documents and knowledge base.

    5 credits per question

  • Chrome recording

    Record a test in the Chrome extension; Ship names it and writes each step and its pass criteria.

    2 credits per test case

Included at no credit cost

  • Root cause and autofix

    Every failed run is investigated and comes with a likely cause and suggested fix.

    Free

  • Live sessions

    Watch and drive a test live, or debug a failure step by step.

    Free fair use

  • Tests generated from PRs

    New and updated test cases Ship writes while analysing your pull requests.

    Free

  • Knowledge base sync

    Keeps Ship’s context current with your documents and integrations.

    Free

[ How credits work ]

Simple rules, no surprises.

Monthly

Plan credits reset

Your plan’s credits refresh every billing month. Unused plan credits don’t roll over.

Top up

Additional credits never expire

Buy more any time at $0.025 a credit. They stay on your account until you use them.

Order

Plan credits go first

Ship always spends this month’s plan credits before touching additional credits.

Seats

No per-user pricing

Invite your whole team. You pay for the work Ship does, not for logins.

[ Estimate ]

What would your team use?

Enter a typical month. Most teams run their regression and promotion tests weekly, analyse PRs, and send in bugs.

Every test case execution, including reruns
Setup and login steps count too
Feature PRs and promotion PRs
Reported bugs Ship reproduces
Estimated credits a month3,800
Test runs
3,600 (8 per run)
PR impact analysis
50
Bug analysis
150
Best fitStarter · $94 / month$49 plan + 1,800 additional credits ($45.00)

[ Compare ]

Every plan, side by side.

FeatureFree trialStarterProEnterprise
Price$0 for 15 days$49 / month$249 / monthCustom
Credits3,0002,000 / month12,000 / monthVolume
Additional creditsNo$0.025, never expire$0.025, never expireBy contract
Plan credits roll overNoNoNoBy contract
Team
UsersUnlimitedUnlimitedUnlimitedUnlimited
GitHub repositories11MultipleUnlimited
Parallel test runs2510Custom
Workflows
PR impact analysisYesYesYesYes
Bug analysis and reproductionYesYesYesYes
Crawl and code analysisYesYesYesYes
Root cause and autofixYesYesYesYes
Live sessionsFair useFair useFair useCustom
Mobile real devicesNoNoComing soonDedicated
Enterprise
SSO and enterprise controlsNoNoNoYes
On-premise deploymentNoNoNoYes
Dedicated supportNoNoNoYes

Questions?

More questions?

Reach out anytime.

Talk to sales
Is Ship another test automation tool?

No. Ship is an autonomous quality engineer. It decides what needs attention, runs the appropriate quality workflow, investigates failures, and delivers actionable results without waiting for someone to manually create and execute every test.

Does Ship replace our existing tests?

No. Ship can use and maintain the testing infrastructure you already have while adding autonomous testing where coverage is missing.

How is Ship different from Claude or Codex?

Ship isn’t trying to replace coding agents. It gives them better inputs. Ship continuously observes the engineering workflow, tests deployed software, reproduces failures, finds likely root causes, and hands verified context to coding agents when it’s time to fix something.

How is Ship different from CodeRabbit or Greptile?

Code review tools primarily reason about code. Ship tests the deployed product like a quality engineer would, with context from code, tests, documentation, bugs, tickets, designs, and real product behavior.

What happens when Ship finds a bug?

Ship captures the failure, reproduces it, collects evidence, investigates the likely root cause, and creates an actionable handoff for your engineering team or coding agent.

What tools does Ship integrate with?

Ship is designed to work across your existing engineering stack, including code repositories, issue trackers, communication tools, support systems, and AI coding agents.

Can I try Ship before buying?

Yes. Start with a 15-day trial.

What is a credit?

A credit is Ship’s single unit of work, worth $0.025. Every workflow, from running a test to analysing a pull request, costs a set number of credits, so one balance covers everything Ship does.

How are test runs counted?

One credit covers four executed steps, rounded up per run. A 30-step test costs 8 credits. Setup and login steps that run before the test count too, and a run that stops early is charged only for the steps it actually executed.

Do failed tests cost more?

No. When a test fails, root cause analysis and autofix suggestions are included in the run. You only pay for the steps that ran.

What happens if I run out of credits?

Ship keeps working on additional credits at $0.025 each. Additional credits never expire, and Ship always spends your monthly plan credits first.

Do unused credits roll over?

Monthly plan credits reset each billing month and don’t roll over. Additional credits you buy never expire.

What’s included in the free trial?

Every new account starts with a 15-day trial and 3,000 credits: enough to crawl your app, analyse a repository and run your first tests, with every Starter feature.

Do you charge per user?

No. Every plan includes unlimited users. Live sessions are free under fair use, one active session per user.

Why is code analysis 1,000 credits?

Code analysis is a one-time job per repository. Ship reads the whole codebase, maps how it fits together and generates tests from it. That context is what makes every later PR impact analysis precise, so you typically run it once and only again after major changes.

Which pull requests should Ship analyse?

Any you like, at 10 credits each. Many teams analyse every promotion PR, for example dev to QA, and run the impacted tests there, which keeps credit use predictable as the number of feature PRs grows.

When should I choose Pro over Starter?

Choose Pro when your team works across more than one repository, needs 10 parallel test runs, or regularly uses more than about 10,000 credits a month. Pro’s 12,000 credits cost about $0.021 each, against $0.0245 on Starter.

Is mobile testing available?

Real-device mobile testing is coming soon as a Pro add-on. Enterprise customers can reserve dedicated devices.

Do Ship credits work like ContextQA AAT credits?

Yes. Ship credits are priced the same as ContextQA AAT credits, at $0.025 each.