The whole map, and the inbox behind every pin.

LocalLeads finds every business of a type in an area on Google Maps, past the 120-result limit. It reads each one's website for emails, socials and phone numbers, and hands you a clean list to export. It runs on your own computer or server: one binary, one SQLite file, no API key, no per-lead pricing.

curl -fsSL https://raw.githubusercontent.com/seczoid/localleads/main/setup.sh | bash

Paste it into Terminal and press Enter. On a Mac it opens at localhost:7878; on a Linux server it sets up HTTPS for you.

Free and open source under AGPL-3.0 · macOS 12+, Linux, Windows, Docker

Example lead
  1. Google Maps
  2. home page
  3. /contact
  4. /about-us
  5. Mail server

Northline Roofing & Exteriors

Roofing contractor · 4.8 (212 reviews)

Address
4410 Kessler St, Houston, TX 77092
Google Maps
Phone
(713) 555-0142
Google Maps
Website
Google Maps
Socials
Facebook · Instagram · LinkedIn
Home page
Built with
WordPress · Google Tag Manager
Home page
Email
office@northlineroofing.com
/contact · mailto
Email
estimates@northlineroofing.comwritten as “estimates [at] northlineroofing (dot) com”
/contact · hidden
Email
dana@northlineroofing.comDana Ruiz, Owner
/about-us · team
Best email
dana@northlineroofing.comSafeOwn domain and a named person, so it outranks office@. The mailbox exists.
Ranked · verified
3 of up to 8 pages read · 3 emails · best email picked
Illustration with made-up details. Email checks run in builds with the verify feature.
The Searches page: a search for roofers and plumbers in Texas running, with Google Maps done and websites being read, above the list of all searches with their phone and website coverage.
The Searches page on a test install. Every screenshot on this page is the real app.

Where every field comes from.

A Maps listing gives you a name, a phone and a website. The person who answers email is on the website. LocalLeads reads it for you: the home page first, then links that look like contact, about or team pages, then common paths like /contact if nothing turned up. Up to 8 pages per site.

From Google Maps

The listing itself.

  • Name, category, address, coordinates
  • Phone and website
  • Rating, review count and opening hours
  • Claimed or not, and the Maps link

Place details, optional: reviews broken down by star, review topics, owner information and photos.

From the website

Up to 8 pages, read with browser-like TLS.

  • Emails from mailto: links and plain text
  • Addresses hidden as “name [at] domain (dot) com”
  • Cloudflare-protected emails and ones in structured data (JSON-LD)
  • Names and job titles next to an address, from team pages
  • Facebook, Instagram, LinkedIn, X, YouTube and TikTok
  • Extra phone numbers and the site title
  • Whether it runs Google Tag Manager or a Facebook Pixel

From the mail server

Asks whether the mailbox exists, without sending anything.

Email verification verdicts
SafeThe server confirmed the mailbox.
RiskyCatch-all domain, role or disposable address.
UnverifiedThe server wouldn't say.
InvalidNo such mailbox. Never picked as the best email.

Checks the 5 best emails per lead. Included when LocalLeads is built with --features verify; the release downloads and Docker image leave it out.

Hidden addresses, found

Sites hide emails from scrapers. These are the forms LocalLeads reads back into an address.

  1. <a href="mailto:office@…">office@northlineroofing.com
  2. estimates [at] northlineroofing (dot) comestimates@northlineroofing.com
  3. /cdn-cgi/l/email-protection#8beae…info@northlineroofing.com
  4. "email": "dana@northlineroofing.com"dana@northlineroofing.com

One best email per lead

Emails on the company's own domain come first, and a real person's address ahead of info@. That one becomes the lead's best email, the one your export leads with.

  1. 1dana@northlineroofing.comown domain · named personBest email
  2. 2office@northlineroofing.comown domain · role address
  3. 3northlineroof@gmail.comanother domain
A lead's detail panel: two emails with the page each was found on, the business address and phone, and what the website showed: title, description, socials, phones, the software it's built with and its tracking.
Lead detail. Every email shows the page it came from; arrow keys move between leads.

A search runs for hours. You can watch every minute of it.

Two bars move in real time. Google Maps shows leads saved, areas searched and repeats skipped. Websites shows sites read, emails found, speed and time left. Once Maps is done, every lead's website is read, as many at once as the search itself ran.

  • Pause, resume or stop whenever you like. Leads are saved as they're found, so stopping keeps everything collected.
  • Continue carries a stopped search on from the areas it already finished. Run again starts a fresh copy.
  • Restarts don't lose work. If the server restarts, updates or crashes, running searches carry on by themselves.
  • An activity log keeps every step, retry and failure, so you can see exactly what happened.
A running search's page: the Google Maps bar full at 3,000 of 3,000 leads, the Websites bar at 997 read with 427 emails, and the newest leads below.

The list is the product.

Every lead from every search sits in one table that stays quick at millions of rows. Narrow it to a search, then to the businesses you'd actually contact, and take that slice to your CRM or sending tool.

The Leads table filtered to one search and to leads with an email, 265 matching, with the Category filter open showing a count beside each category.
Leads, filtered to one search and “has email”. Every filter shows how many leads each choice leaves.
  • Filters with live counts for search, category, state, city, phone and website, email found and rating.
  • Instant search across name, address, phone, website and email.
  • Server-side paging, so the table stays fast whether it holds a thousand rows or a few million.
  • Bulk actions on the rows you select or everything that matches: export, delete, or find emails again.
  • Undo for an hour. Deleted searches, leads, proxies and groups come back with one click.

Three ways out

roofers-texas.csvClean CSV
Name,Phone,Email,Email status,Website,Hours
Northline Roofing & Exteriors,(713) 555-0142,dana@northlineroofing.com,Verified,northlineroofing.com,"Mon–Sat 7am–6pm"
Bayou City Plumbing Co.,(281) 555-0187,service@bayoucityplumbing.com,Not checked,bayoucityplumbing.com,"Mon–Fri 8am–5pm"

One row per business, readable columns, the best email first and opening hours written out. Pick the columns you want.

.csvOutscraper format

Raw fields, one row per email, for tools that expect it.

.jsonJSON

Keeps the raw Maps data. Big exports can go straight to disk.

Example rows, made up for this page.

Proxies that hold up on Google Maps.

Google limits how fast one connection can search. Add proxies and a search goes from 10 requests at once to 100 or 300. LocalLeads has the whole toolkit built in, so you know which ones actually work before a search depends on them.

The Proxies page: group tabs, a health bar of 42 healthy, 9 slow, 8 failed and 5 unchecked, and each proxy's status, latency, group, last check and last error.
Proxies, with groups across the top. The addresses shown are documentation examples.

Paste anything

http://user:pass@host:port, socks5://… or plain host:port. HTTP, HTTPS and SOCKS5. Big files import in the background, de-duplicated.

Checked against Google Maps

Every proxy is tested at once and marked healthy, slow or failed, with its latency and last error. Tune the test URL, timeout, retries, slow threshold, expected page content and exit-IP check.

Failover mid-search

A proxy that fails is set aside and the request retries through another. Only Google lookups go through proxies; websites are read directly.

Groups

Let a search use only some proxies, like a residential pool, and keep the rest for other work.

History

Every check is kept per proxy: when it ran, the status, the latency and the exit IP. You see a proxy getting slower before it starts failing searches.

Bulk tools

Enable, disable or delete a selection, or prune everything that keeps failing in one click. Deleted proxies come back with Undo for an hour.

Or ask your AI agent to do all of it.

LocalLeads includes a Model Context Protocol server. Everything the dashboard does, an agent can do: 44 tools covering searches, categories, leads, exports, enrichment, proxies, groups, backups and the server log.

  • Set up for 11 clients. The Agents page shows the exact command or config for each, with your paths and API key filled in.
  • Two ways to connect: stdio, where the agent launches localleads mcp, or Streamable HTTP at /mcp. Searches an agent starts show up on your screen in real time.
  • One key per agent. See when each was last used and revoke any of them instantly. Keys are stored only as hashes.
  • Safe by default. Delete tools are marked destructive, so agents ask first, and every delete returns an undo id that works for an hour.

Claude Code · Codex · Cursor · Claude Desktop · VS Code (Copilot) · Windsurf · Gemini CLI · Zed · Cline · opencode · any MCP client

You

Find 500 roofers in Austin, TX with websites and emails, and tell me when it's done.

  1. find_categories“roofer”Roofing contractor
  2. preview_searchAustin, TX · ZIP codeslookups counted
  3. create_searchmax 500 · has websiterunning
  4. get_searchprogressMaps done · reading sites
  5. export_leadshas email · CSVsaved to disk
Agent

Done. The search finished and the leads with an email are exported to CSV. It's in your Searches list too, so you can open it in the dashboard.

Illustration. Real tool names; the conversation is an example.

Things you can just ask

  • “Show me the dentists from my last search rated 4.5+ that have an email, as a table.”
  • “Export every lead with a verified email from the plumbers search to CSV on my desktop.”
  • “Check all my proxies and remove the ones that keep failing.”

All 44 tools

Searches 13

  • search_options
  • find_cities
  • find_categories
  • preview_search
  • create_search
  • rerun_search
  • continue_search
  • list_searches
  • get_search
  • pause_search
  • resume_search
  • stop_search
  • delete_search

Leads 7

  • browse_leads
  • lead_facets
  • lead_lists
  • get_lead
  • enrich_leads
  • export_leads
  • delete_leads

Proxies 12

  • list_proxies
  • proxy_status
  • add_proxies
  • import_proxy_file
  • check_proxies
  • cancel_proxy_check
  • set_proxies_enabled
  • delete_proxies
  • prune_proxies
  • proxy_history
  • get_checker_settings
  • update_checker_settings

Groups 6

  • list_proxy_groups
  • create_proxy_group
  • rename_proxy_group
  • delete_proxy_group
  • assign_proxies_to_group
  • remove_proxies_from_group

App 6

  • overview
  • app_info
  • list_notices
  • server_log
  • undo_delete
  • backup_database
The Agents page: API keys for Cursor, Codex and Claude Code with when each was last used, and the one-line command that sets up Claude Code, Codex and Cursor at once.
Agents. One command sets up Claude Code, Codex and Cursor together; the other eight have their own snippet.

Yours. On your laptop or your server.

LocalLeads is one program and one SQLite file. Searches, leads, proxies, settings and your account all live in that file, on a machine you control. There's no API key to buy, no per-lead price and no account with us.

One binary
Static assets are compiled in. Nothing else to deploy.
One SQLite file
Back it up while searches run; restore from the command line.
Light
Rust, Tokio and SQLite. Idles at a few MB of RAM.
Open source
GNU AGPL-3.0. Read it, change it, host it.
$ curl -fsSL https://raw.githubusercontent.com/seczoid/localleads/main/setup.sh | bash

==> Where will you open LocalLeads?
  1) From anywhere, at this server's IP address (HTTPS from Let's Encrypt, no domain needed; quickest)
  2) From anywhere, at my own domain (HTTPS from Let's Encrypt; needs a DNS record)
  3) Only on this machine
  4) Behind my own web server
==> Getting LocalLeads
  ✓ Downloaded localleads-x86_64-unknown-linux-gnu.tar.gz (checksum verified)
==> Setting up the service
  ✓ Started the localleads service (starts on boot)
==> Setting up HTTPS
  ✓ Caddy serves https://203.0.113.7
  ✓ Opened ports 80 and 443 in ufw
  ✓ Trusted certificate from Let's Encrypt; Caddy renews it every few days

  LocalLeads is running.

  Open         https://203.0.113.7
  Setup code   k7Pq-2mXa-9TzR-bW4e  (to create your account, the first time)
Abridged example run. Your address, version and code will differ.

HTTPS without the homework

On a Linux server the setup sets up Caddy with a Let's Encrypt certificate, for your domain or for the server's bare IP address, renewed on its own. Caddy already serving other sites? LocalLeads is added next to them. nginx on ports 80 and 443? It offers other ports, or a ready-made config to put LocalLeads behind it.

Hardened for the internet

A one-time setup code so no stranger can claim a fresh install, Argon2id passwords, sign-in lockout after repeated failures, Secure cookies, a Content-Security-Policy and a host allowlist.

Updates from the dashboard

When a new version is out, an Update and restart card appears. It checks the download against the release's checksums, backs up your database, and restarts. Running searches pause for a few seconds and carry on.

And the rest

A searches home with totals and coverage, a live server log you can filter and download, built-in docs for every screen, dark and light themes, and a JSON API for your own scripts.

The others charge by the lead. LocalLeads doesn't.

Outscraper, Apify and Scrap.io pull the same public Google Maps data. They run it on their servers and bill you for every place, every website and every email. LocalLeads does the same work on your own machine, starts the moment you press Start, and charges nothing per lead, however long the list gets.

The same search, run on both

One job, side by side. LocalLeads had it done in about half an hour. Outscraper took about two days to hand back the same job.

LocalLeads about 30 minutes
Outscraper about 2 days
Our own run of one search on both services, drawn to scale. Your times depend on the area, your machine and your proxies: LocalLeads makes 10 requests at once without proxies and 100 to 300 with them.
Compared onLocalLeadsOutscraperApify Google Maps ScraperScrap.io
How you payFree. No per-lead price, no plan, no credits.$3 per 1,000 places after the first 500, then $1 after 100,000.From $1.50 per 1,000 places, plus paid add-ons.A monthly plan, about $49 to $499, with a set number of export credits.
Emails from each websiteIncluded. Up to 8 pages per site, hidden and Cloudflare-protected addresses too, ranked to one best email.A separate service: $3 per 1,000 websites.A paid add-on (company contacts enrichment).Counted in export credits. The basic export keeps only the first email.
Checking the mailbox existsIncluded in builds with the verify feature.Sold separately: $3 per 1,000 emails.Another paid add-on.Not stated on its pricing page.
10,000 businesses with their emails$0 to LocalLeads. Proxies, if you use them, are billed by your provider.About $57, before checking a single email.$15 or more for the places, plus the add-ons.A plan with 10,000+ export credits that month.
When it startsRight away, on your machine, as wide as your proxies allow.On the service's servers, on its schedule and at the speed it gives you.
Where your leads liveOne SQLite file on your laptop or server.On the service's servers.
The codeOpen source, AGPL-3.0. Read it, change it, host it.A closed service.Runs on Apify's platform.A closed service.
AI agentsA built-in MCP server: 44 tools, one key per agent.Through its API.Through Apify's API and MCP server.Through its API.

Coming from Outscraper? LocalLeads also exports in Outscraper's own CSV format, one row per email with the raw fields, so the sheets and tools you already use keep working.

Install LocalLeads

Prices are from each company's public pricing page in November 2026, in US dollars before tax. Scrap.io's prices vary by region. The 10,000-business figure assumes every business has a website with one email, at each service's listed rates. Outscraper, Apify and Scrap.io are trademarks of their owners; LocalLeads isn't affiliated with them.

Running in a minute.

Pick where it should live. You can start on your laptop and move to a server later; your leads are one file.

On your Mac

Trying it out and using it yourself. About a minute.

  1. Open Terminal: press ⌘ Space, type Terminal, press Enter.
  2. Paste the setup line below and press Enter.
  3. Press Enter to accept each suggested answer.
  4. Open localhost:7878 and create your account.

It starts again by itself whenever you log in.

On a server

Open it from any computer or phone, with searches that keep running when your laptop is off. About five minutes.

  1. Log in to your Linux server, usually ssh root@your-server.
  2. Paste the setup line below and press Enter.
  3. No domain? Press Enter to use the server's IP. Have one? Point an A record at the server and type 2.
  4. Open the address it prints and enter the setup code.

Ubuntu 20.04+, Debian 10+, RHEL, Rocky, Alma, Fedora, Arch, openSUSE. x86_64 or ARM64.

On Windows

The same app on your PC. About a minute.

  1. Download the zip (or the ARM version for Snapdragon laptops).
  2. Right-click it and choose Extract All.
  3. Double-click localleads.exe. If Windows warns you, click More info, then Run anyway.
  4. Keep the window open and visit localhost:7878.

To update, download the new version and replace the .exe. Your leads are kept.

curl -fsSL https://raw.githubusercontent.com/seczoid/localleads/main/setup.sh | bash

Run the same line again to update, change settings or uninstall. Prefer to read it first? Read setup.sh. Also: Docker and self-hosting · build from source · all downloads.

Every pin on the map is somebody you could be emailing.

Free, open source, and running on your own machine.