spidey-sense

Self-healing scraper control plane

Bright Data’s docs say: “You are the detector.”

So this is the detector.

Bright Data ships one repair primitive: scraper heal. It rewrites a broken extractor — and stops at an approval gate, waiting for a human. spidey-sense builds the four stages around it that decide when to heal and whether the rewrite is allowed to ship — scored against a schema contract, not eyeballed.

  1. 01spidey-sense

    Detect

    Score every run against a schema contract.

  2. 02spidey-sense

    Diagnose

    Compile the failing fields into a heal prompt.

  3. 03Bright Data

    Heal

    scraper heal rewrites the broken extractor.

  4. 04spidey-sense

    Verify

    Re-score the preview. Approve only if it improves.

  5. 05spidey-sense

    Promote

    Commit, then re-run canaries to confirm production.

Heal Lab

one real, resolved incident — replayed on demand
Heal Lab · live incident replay
Nimbus CLI (harness) · the redesign that moved the date into an attribute
1.00
healthy
versiondatetitlepermalinktagbody
Healthy — every contract field within threshold.
  1. 01
    Detectspidey-sense
  2. 02
    Diagnosespidey-sense
  3. 03
    HealBright Data
  4. 04
    Verifyspidey-sense
  5. 05
    Promotespidey-sense
3
collectors
3
healthy
0
degraded
0
broken
0
open incidents
14
runs scored

Fleet

3 collectors under contract

Neon Changelog

neon.com · c_REPLACE_NEON

Healthy
uptime
100%
last score
1.00
runs
4

no incidents — clean since first run

Recent incidents