ShipGuarde Reviews and Details

Questions & Answers

1. What makes ShipGuarde unique?

   It tests the running application on every pull request, rather than the code or a component in isolation.

   You describe a flow in plain English, for example "log in, add an item to the cart, check out". A vision model then drives a real browser through it. Because nothing is pinned to CSS selectors, the check survives a refactor that would break a conventional end-to-end suite.

   Every run ends in one line: ship or do-not-ship, with screenshots and the evidence behind each finding attached. That line is written to be read by whoever approves the release, not only by the engineer who wrote the test.

   Most tools in this space either read the diff or compare screenshots pixel by pixel. ShipGuarde does neither.

2. Why should a person choose ShipGuarde over its competitors?

   It depends which kind of competitor you mean, because ShipGuarde sits between two categories.

   Against tools that review the diff (CodeRabbit and similar): they read the patch. ShipGuarde runs the application against that pull request's preview deployment, so it finds the class of problem that only exists once the page is rendered. A checkout flow that breaks. A control that cannot be reached by keyboard. A link that leads nowhere. None of those are visible in a diff.

   Against pixel-diffing visual tools (Percy, Applitools and similar): ShipGuarde is driven by a vision model rather than image comparison, so a font rendering a pixel differently does not fail the build. Flaky failures are the usual reason teams switch visual testing off after a month.

   One honest caveat: ShipGuarde is early. If you need years of enterprise integrations and a large support organisation, the incumbents are the safer answer today.

3. How would you describe the primary audience of ShipGuarde?

   Small and mid-size engineering teams shipping a web application on a regular cadence, usually without a dedicated QA function.

   The person who feels the problem most is the one approving releases: an engineering lead, a head of engineering, or a technical founder who has to decide whether a pull request is safe to merge. Today that decision is often made by opening the preview link and clicking around for a few minutes, which does not scale and does not get done on a Friday evening.

   Teams that already employ manual QA are a good fit too. ShipGuarde takes the repetitive regression pass off them so they can spend their time on the harder bugs, rather than replacing anyone.

   It is a poor fit for anything without a web UI, and for teams that do not deploy preview environments per pull request.

4. What's the story behind ShipGuarde?

   Most teams ship web applications faster than they can check them. Unit tests pass, CI goes green, and the thing that actually breaks is a flow nobody clicked before merging.

   The existing answers all have a failure mode that shows up around month two. End-to-end suites pinned to CSS selectors break on every refactor, so people stop trusting them and then stop fixing them. Pixel diffing raises a failure every time a font renders half a pixel differently, so people turn it off. Code review tools read the patch, which means the whole category of "it looks fine in the diff and is broken on the page" goes unseen.

   ShipGuarde started from a simple bet: the check should look at the rendered page the way a person would, and it should end in a decision rather than a report. That is why a run returns one line, ship or do-not-ship, instead of a dashboard nobody opens.

   The harder half turned out to be trust, not capability. An automated reviewer that reports something real as broken is worse than no reviewer, so a lot of the work has gone into the product knowing when it cannot tell, and saying so, rather than guessing.

5. Which are the primary technologies used for building ShipGuarde?

   • Web app: Next.js and React, in TypeScript, styled with Tailwind CSS
   • API: Fastify in TypeScript, with Zod for request validation
   • Database: PostgreSQL, accessed through Prisma
   • Job queue: BullMQ on Redis, which schedules the agent runs
   • Browser agents: Python and FastAPI, driving headless Chromium through Playwright
   • Models: vision-capable LLMs, currently Gemini, Claude and GPT, routed per agent
   • Auth: Clerk
   • Infrastructure: Railway, behind Cloudflare
   • Tests: Vitest on the TypeScript side, pytest on the Python agents

   The split is deliberate. The orchestration, billing and GitHub integration are TypeScript, while anything that drives a real browser is Python, because that is where the Playwright and imaging tooling is strongest.