Pulsant (pulsant)
- Domain:
www.pulsant.com· Kind: operator · Priority: 2 · Enabled: yes - License / attribution: Publicly accessible operator pages; factual data only; © Pulsant — attribution “Pulsant”
- Coverage: GB
What it collects
Facility records (kind: facility) via parser(s) pulsant_facility_v1 in apps/worker/src/connectors/operators2/emea.ts.
Fields published by the pages and captured: name, code, city, countryIso2, itCapacityMw, buildingSqm, renewableClaim, coolingType, facilityType (edge), certifications.
Every field carries an extraction method in methods (e.g. json-ld:PostalAddress, regex:it_mw_v1, attr:data-value+MW, lookup:city-country) for provenance. Coordinates are only taken from JSON-LD / embedded JSON / map links published by the operator — never geocoded. Status defaults to operational unless the page uses pipeline wording (under construction / coming soon / planned).
Discovery
- Sitemaps:
https://www.pulsant.com/sitemap.xml - Include:
/colocation-[a-z-]+$,/announcements/,/news/ - Exclude:
\?,#,/colocation$,/colocation-(services|guide|pricing|buyers?-guide),/knowledge-hub/,/blog/,/faqs/,/announcements$ - Classify:
/colocation-[a-z-]+$→ facility_pages (facility_page);/(announcements|news)/.→ newsroom (press_release)
Newsroom URLs (when configured) rely on the GenericConnector news fallback (press_release → news_event when data-center relevant).
Schedule & fetch
- Schedule: facility_pages weekly, newsroom daily, sitemap weekly
- Fetch: L1→L2, 15 rpm, concurrency 2, robots.txt respected, max 20 premium credits/run. All pages are served at L1 (plain HTTP);
maxLevelis capped at 2 so false-positive “blocked” heuristics (HubSpot / cookie-consent strings) never spend Scrapfly credits.
Quirks
Facility pages /colocation-- publish a technical table (total IT power, building size, data hall space, renewable procurement, cooling redundancy).
Verification (live, 2026-09-11)
try-connector --limit N: discovered 10 URLs (facility_pages=10); sampled pages → 4 entities, 4 valid, 0 rejected, 0 premium credits.