Free and Open-Source Visitor Identification: What Actually Works (2026)

There is no fully open-source equivalent of commercial visitor identification — and understanding why tells you exactly what you can and can't get for free. The identification stack has two halves: the tracking half (open-sourceable, and genuinely open in tools like Matomo and PostHog) and the resolution half — the databases and identity graphs that turn an IP address into "Acme Corp" or a session into "Jane Doe, Head of Growth." That second half is licensed commercial data by nature. This guide maps what open-source and free options really deliver, where the ceiling is, and the honest $0 stack for teams that aren't ready to pay.

Why the resolution layer can't be open source

Company identification requires a continuously maintained mapping of IP ranges to organizations — corporate registrations, reverse DNS, peering data, and manual verification, decaying constantly as companies move offices and clouds. Person-level identification requires consented identity graphs built from publisher networks — contractual, commercial, and privacy-bound by construction. Neither dataset can be crowdsourced to a public repo the way code can: the value is the upkeep. So "open-source visitor identification" in practice means open-source *tracking* joined to some resolution source — free, cheap, or commercial — and quality tracks the resolution source, not the tracker.

What you can genuinely do open source or free

• Self-hosted analytics: Matomo, PostHog. Full-featured, private, yours. Out of the box they show behavior, not business identity. Matomo has an IP-enrichment ecosystem (via GeoIP-style org databases) that labels some traffic with an organization name — expect coarse results: heavy ISP noise, no firmographics, no filtering.
• Reverse DNS and free IP data. A weekend project: log visitor IPs server-side, run reverse DNS lookups, match against free IP-to-org data. It will identify a slice of large-company traffic (big corporations own their IP ranges and label them) and almost no SMB traffic (which rides on ISP ranges). This is roughly year-2010 Leadfeeder, rebuilt by you, maintained by you.
• Microsoft Clarity. Free forever, unlimited traffic: session recordings, heatmaps, basic analytics. Zero identification, but the best free behavioral layer to pair with anything below.
• Server log analysis. Your web server already logs IPs and user agents. Filtering datacenter ranges and known crawlers, then reverse-resolving what remains, surfaces the most identifiable fraction of your traffic at exactly $0 and a few hours of scripting.

The ceiling on all of the above: no person-level identification whatsoever (identity graphs aren't accessible at any DIY price), high ISP noise, no intent scoring, and integration work that's all yours. For how the commercial layers actually work, see how to identify anonymous website visitors and person-level vs company-level identification.

The free tiers of commercial tools (usually the better $0)

Here's the practical secret: the free tiers of commercial identification tools beat the DIY stack for most teams, because you get the commercial resolution data — just less of it.

Ten credits sounds small until you scope it to the job: point them at your pricing and comparison pages only, and a low-traffic B2B site gets its highest-intent visitors identified — with real resolution quality — every month, free. That's also the honest way to evaluate whether paid identification would pay for itself; our evaluation guide turns that into a two-week protocol.

The honest $0 stack

For a team with no budget and some technical comfort:

1. Plausible (trial/self-hosted) or GA4 for traffic truth — or self-hosted Matomo if data ownership is the point.
2. Microsoft Clarity for session behavior.
3. VisiLead free tier for identification of high-intent pages (10 credits, person-level included on US traffic).
4. RB2B free tier for a parallel Slack feed of company resolutions (150/mo).
5. A weekly 20-minute review: identified companies vs. your target list; anything matching gets a human follow-up.

That stack costs nothing, requires no maintenance, and delivers a real (if rationed) version of what the paid stack does. When you routinely burn all the free credits and want the rest of your traffic identified, that's the signal to pay — entry pricing in this market starts at $29/mo, which is the cheapest line item in any GTM budget that generates named pipeline.

When DIY is actually the right call

Three legitimate cases: you're a developer-led company where data ownership is a hard requirement (self-hosted Matomo plus server-side enrichment keeps everything in-house); your traffic is overwhelmingly non-US and non-business (nothing commercial will identify consumer traffic anyway, so free analytics is the honest ceiling); or identification is a curiosity rather than a workflow (a monthly server-log review scratches the itch at $0). Outside those, the arithmetic is lopsided — a rebuilt-from-scratch identification pipeline costs engineer-days per month to run worse than a $29 subscription.

Frequently Asked Questions

Q: Is there an open-source alternative to Leadfeeder or VisiLead?

A: Not a complete one. The tracking layer is open-sourceable (Matomo, PostHog), but the resolution layer — commercial IP-to-company databases and consented identity graphs — is licensed data that no open-source project maintains at usable quality. The closest DIY approximation is self-hosted analytics plus reverse-DNS/IP-org enrichment, which identifies a slice of large-company traffic with heavy ISP noise and no person-level capability.

Q: How can I see which companies visit my website for free?

A: Two honest paths: the free tiers of commercial tools (VisiLead: 10 credits/mo with person-level on US traffic; RB2B: 150 company resolutions/mo; Leadfeeder Lite: last 100 companies) — the better option for most teams because you get commercial-grade resolution — or the DIY route: server logs plus reverse DNS, which surfaces some large-company visits and misses most everything else. Pointing free credits at your pricing page captures the highest-intent slice at $0.

Q: Can Matomo or PostHog identify website visitors?

A: They identify behavior, not businesses: both are excellent open-source analytics with session-level detail, and both can display an organization label on some traffic via IP-enrichment databases — coarse, ISP-noisy, and without firmographics or intent scoring. Neither offers person-level identification, which requires consented identity graphs that exist only commercially. Many teams run Matomo or PostHog for analytics alongside a commercial identification layer; the two jobs don't compete.

Q: Is free visitor identification GDPR compliant?

A: The same rules apply at $0 as at $299/mo: company-level identification (free tiers included) operates under legitimate interest with disclosure in your privacy policy; DIY server-log enrichment is likewise fine with disclosure since it processes business network data. Person-level identification remains US-traffic-only regardless of price. The compliance risk in DIY setups is sloppiness — retaining raw IPs indefinitely without a stated purpose — not the identification itself; our GDPR guide has the checklist.