Clearbit alternatives after the HubSpot acquisition

The best Clearbit alternative depends on which part of Clearbit you were using, because HubSpot didn't replace Clearbit with one thing. After the acquisition closed in December 2023, Clearbit became a HubSpot-only product, the free tools shut down on April 30, 2025, and the free Logo API went dark on December 8, 2025. If you're in HubSpot, its built-in data enrichment is the direct successor. If you're not, you need a separate replacement for each feature: a logo service, an enrichment API, and possibly a screening layer for signups.

Below is the timeline from HubSpot's and Clearbit's own announcements, then a feature-by-feature replacement map. Every price here was checked on the vendor's own page on the date of this post; they change, so check again before you buy.

What actually happened, in order

All of these come from Clearbit's changelog and HubSpot's announcement.

On the HubSpot side, HubSpot's knowledge base now documents the successor as "data enrichment". It enriches company records from the company domain and contact records from name plus work email, it is available on paid Starter, Professional and Enterprise hub subscriptions, and HubSpot states that data enrichment does not consume HubSpot Credits. It runs on records inside HubSpot. If your data lives in Salesforce, a warehouse, or your own Postgres, it doesn't help you directly.

First, find out what you were really using

Before you shop, grep. Clearbit integrations tend to be scattered across a codebase and a marketing stack, and most teams used two or three features without realising they were separate products.

# Every reference in code, templates and config
grep -rni 'clearbit' . --exclude-dir=node_modules --exclude-dir=.git

Also check: form tools (Clearbit's form shortening was usually configured in the marketing automation tool, not in code), CRM field names prefixed with clearbit_, and any Zapier or Make scenarios. Each hit falls into one of the rows below.

Replacement map

Logos

This is the one that broke the most production UIs, because it was a URL pattern you could drop into an <img> tag with no key. Those images now fail.

Clearbit's own notice pointed users to Logo.dev. Per its pricing page, the free Community plan includes 500K logo CDN requests a month, requires a link back for commercial projects on the free plan, and paid plans start at $33 a month. You'll need a key, which means the URL is no longer something you can paste into a CMS without thinking.

If you only need small icons, a self-hosted approach is often good enough: fetch /favicon.ico or the apple-touch-icon link from the company's homepage once, store it in your own bucket, and serve it from there. Either way, add an onerror fallback to a monogram so the next vendor change doesn't leave broken images in your UI:

<img src="https://img.example.com/logos/stripe.com.png"
     onerror="this.replaceWith(Object.assign(document.createElement('span'),
       {className:'logo-fallback', textContent:'S'}))"
     alt="Stripe">

Company enrichment from a domain

This was Clearbit's core API: send a domain, get name, industry, employee range, location, social links. Options outside HubSpot, with what their own pricing pages say today:

• People Data Labs: free company plan with up to 100 records a month, contact data obfuscated on that tier, paid self-serve plans from roughly $100 a month.
• Hunter: a Company Enrichment API that takes a domain. Free plan with 50 credits a month; Starter is $49 a month billed monthly ($34 a month billed annually).
• Apollo: its pricing page says API access is available on Custom plans. Worth talking to if you also want outbound tooling; overkill if you only need firmographics.
• pingutil (ours): free, community-run, 60 requests a minute per key. Classifies every domain and returns an LLM-generated company profile with a self-reported confidence score. No person-level data, no bulk endpoint, and less reliable than a commercial database on small or obscure companies.

Mapping the most common Clearbit company fields to pingutil's response, if you want to swap with minimal changes downstream:

There's no equivalent for revenue, market cap, NAICS/SIC codes, tech stack detection or traffic rank. If your scoring model used any of those, a free LLM-based profile won't replace it.

// One function that the rest of your code calls. Rename the output keys to
// whatever your old Clearbit integration wrote, so downstream code doesn't change.
export async function findCompany(domain: string) {
  const res = await fetch('https://pingutil.com/v1/lookup', {
    method: 'POST',
    headers: {
      authorization: `Bearer ${process.env.PINGUTIL_KEY}`,
      'content-type': 'application/json',
    },
    body: JSON.stringify({ input: domain }),
  });
  if (!res.ok) throw new Error(`lookup failed: ${res.status}`);
  const data = await res.json();

  const c = data.company;
  if (data.category !== 'company' || !c) return null; // free/edu/gov/etc, or enrichment failed
  if ((c.confidence ?? 0) < 0.5) return null;          // don't write weak guesses into the CRM

  return {
    domain: data.domain,
    name: c.name,
    legalName: c.legal_name,
    description: c.description,
    industry: c.industry,
    foundedYear: c.founded_year,
    employeesRange: c.employee_size_estimate,
    city: c.headquarters?.city ?? null,
    state: c.headquarters?.region ?? null,
    country: c.headquarters?.country ?? null,
    linkedinUrl: c.linkedin_url,
    twitterHandle: c.twitter_handle,
    ticker: c.ticker,
    enrichmentConfidence: c.confidence,
  };
}

Two things will likely differ from what you had. pingutil's employee buckets are fixed strings (1-10, 11-50, 51-200, 201-500, 501-1000, 1001-5000, 5001-10000, 10000+), so any rule that matched on your old range strings needs updating. And headquarters.country is the model's free-text output ("United States"), not an ISO code, so normalize it before you route on it. Testing method for any of these providers is in free company enrichment APIs.

Contact and person data

Clearbit also enriched people: title, seniority, role. That market is separate, and none of the free options above, pingutil included, fill this gap. If you need contact data, you are buying from a contact data vendor and should evaluate them on compliance and accuracy as much as price. We don't cover them here.

Signup screening

A lot of teams used a Clearbit lookup at signup as a proxy for "is this a real business email?". If that's what you were doing, you don't need firmographics at all. You need to know whether the domain is free webmail, disposable, a university or a company, which is a list lookup that takes milliseconds:

curl -X POST https://pingutil.com/v1/lookup \
  -H "Authorization: Bearer pk_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{ "input": "jane@acme-logistics.de", "skip_enrichment": true }'

category tells you the domain type and verdict.is_spam tells you whether to block. See how to tell a business email from a personal one for the full logic, and the disposable domain category for what gets blocked.

Pick by situation

• On a paid HubSpot hub, data stays in HubSpot: use HubSpot's data enrichment. It's the actual successor and it's included.
• Only used the Logo API: move to a logo service or self-host favicons. Add a fallback.
• Need firmographics in your own database at low volume: start with a free tier or a free LLM-based API, run a 50-domain accuracy test, and upgrade only if the numbers say so.
• Need contact data: budget for a contact data vendor. Free won't cover it.
• Were only screening signups: use domain classification, skip enrichment entirely.

Whichever you pick, put the vendor behind one function in your code, like the shim above. The Clearbit migration hurt most for teams who had the URL hardcoded in forty templates. The next vendor change will be cheaper if it only touches one file. If you're wiring enrichment into a lead pipeline, enriching inbound leads from an email domain covers the pipeline side.