Loading observation history…
SHIPWATCH
A closer look at who’s shipping.
Follow the websites you’re curious about. See their release history, find their rhythm, and share what you notice.
The index
| # | WEBSITE | COLLECTION | RELEASES | LAST SHIP | STATUS |
|---|---|---|---|---|---|
| Loading websites… | |||||
Anyone can add a public website. The YC directory is a starter set. How it works
Recently observed
Listening for the next ship.
New releases appear here after confirmation.
No
backfilled or estimated activity.
How it works
01
Look every five minutes
We fetch each eligible public page and compare its first-party JavaScript content or a selected public API schema. Sibling subdomain bundles and linked chunks are included within a bounded budget. Checks are spread out, with backoff for failures.
02
Confirm the change
The first successful check establishes a baseline. A different content fingerprint must persist on a follow-up check before we record it. Deployment IDs, known Sentry debug metadata, and hashed asset references do not count by themselves. Multiple changes within the same five-minute interval count once per website. Previously seen fingerprints and rollbacks don't add to the count.
03
Keep the limits visible
These are observed public code and API-schema changes, not commits, verified backend deployments, or employee working hours. A/B tests and regional rollouts can still introduce noise. Multiple releases between checks can be missed.
04
Compare what we actually saw
Rankings use 7- or 30-day windows. New companies have shorter observation histories. Every profile shows its baseline date and successful checks. Timestamps use your device’s timezone. Rate calculations use completed UTC days.
YC directory data comes from the unofficial yc-oss API. Active and public companies with usable URLs are eligible. Marketing websites may release independently of the product. We inspect up to 128 first-party assets per page, including imports and Vite-listed styles, with a 20 MB response budget. Conditional requests reuse unchanged content. Uninspected routes and third-party CDN assets can be missed. Older deployment-based observations are excluded unless their historical content can be reverified. Luna classifies code differences and summarizes application changes. Build-only, uncertain, and unclassified observations are excluded from public histories. AI classifications can be wrong.
Finding websites to watch
Passive sources suggest subdomains. Links on the submitted page, and public archives when it cannot be monitored, can suggest a few app or documentation paths on the same site. A model reviews the inspected pages and public API schemas; you choose what gets monitored. Discovery is bounded and can miss pages.
API changes
We compare API request references extracted from saved JavaScript and can monitor public OpenAPI or Swagger documents. A new client reference does not prove an endpoint was just added to the server. Private backend deployments and ordinary changing API data are not visible here.
Why a website may not be checked successfully
Some sites have no observable first-party JavaScript, block requests, or return errors. Failed checks retry with backoff. A domain count means selected monitored hosts—not all subdomains a company owns.