Skip to content
shimpilot

Legal

Status

What Shimpilot is made of, and where to report something that looks wrong.

Last updated: September 16, 2026

How this page works

This page is maintained manually. It does not yet pull a live signal from Shimpilot's own infrastructure — there is no automated uptime check behind it. We are not going to put a row of green checkmarks here that we cannot actually stand behind.

If something is degraded and we know about it, we'll say so here and update it as the situation changes. If you notice a problem before we do, the fastest way to reach us is the reporting section below.

Components

Shimpilot is made up of the following pieces:

  • Web app and API — the dashboard, sign-in, and the endpoints GitHub and Polar webhooks call.
  • Scan worker — clones and analyzes repositories to find affected Stripe and OpenAI call sites.
  • Impact worker — classifies which repositories a detected API change actually affects.
  • Migration and automation workers — generate, validate, and (in Automatic mode) merge migration pull requests.
  • Alert delivery — email and Slack notifications for detected changes and migration outcomes.

A delay in one component does not necessarily affect the others — for example, the dashboard staying fully responsive while a scan is queued behind a backlog.

Incident history

No incidents have been published on this page yet.

Reporting an issue

If a scan isn't completing, a migration seems stuck, or the dashboard isn't loading, email support@shimpilot.com with your organization name and, if you have it, the repository or migration ID involved.