What we're building at Othercrew

Othercrew is being built to take care of the work around your work: setting up useful checks, keeping a small set of critical browser journeys healthy, and making failures easier to understand.

The goal is straightforward. Your team connects a supported GitHub repository, reviews a proposed plan, and decides which checks should run. When a check fails, Othercrew should preserve the original result, gather evidence, and suggest a bounded maintenance fix when the cause is in scope. Your team reviews the change. A real product regression stays failed.

A small set of checks, with clear limits

The first product scope is managed CI plus a few owner-approved end-to-end journeys for supported web applications. The exact support boundary is still being developed. A handful of journeys cannot prove that an entire application works, and missing or skipped checks must remain visible.

Othercrew is not live yet. This site includes a simulated walkthrough of the intended experience; it does not connect to GitHub, execute tests, or create pull requests. The examples are there to show the distinction between a workflow setup problem and a product bug that needs a developer.

People keep the final say

Othercrew is designed to propose reviewable changes, not merge them automatically. The expected behavior of your product and the assertions in your tests should stay intact. A passing result only matters when the relevant approved checks ran against the exact change being reviewed.

That is the bar we want the service to meet. It is a product goal, not a claim that the system already does this today.

Early access

We are collecting early-access interest while the product is being built. Joining the list records your interest; it does not create an account, install a GitHub App, or provide access to a live service.

If this sounds useful, join the early-access list. We’ll keep the first release focused and be clear about what it can—and cannot—support.