ThreatPulsar is a seed-stage startup built by people who spent years doing external threat intelligence work and kept finding the same problem: companies didn't know what was exposed about them on the internet. We're building the tooling to fix that.
A small team with deep roots in external threat intelligence, infrastructure reconnaissance, and dark web research.
Elena spent eight years as an external threat intelligence consultant, helping companies understand what attackers could see about them before they found out the hard way. She ran dozens of attack surface assessments across financial services, healthcare, and tech — and saw the same gap in every one. No one was watching the outside continuously. She co-founded ThreatPulsar to automate what she'd been doing manually. She holds a B.S. in Computer Science from George Mason University and CISSP, CISM certifications.
Marcus built the original ThreatPulsar prototype: the subdomain enumerator, dark web crawler, and certificate transparency feed integration. His background spans internet-wide scanning systems, reconnaissance tooling, and high-throughput data pipeline engineering. He previously built distributed scanning infrastructure at two cybersecurity companies and contributed to several open-source recon tools. M.S. in Computer Science from Carnegie Mellon.
Priya leads ThreatPulsar's threat research — evaluating dark web sources for coverage and reliability, expanding the credential leak monitoring dataset, and running the Insights blog. She previously spent five years as a senior threat intelligence analyst at a government defense contractor focused on adversary infrastructure tracking and credential leak analysis across nation-state actor campaigns. She holds a B.S. in Information Security and is GIAC GCTI certified.
ThreatPulsar is at the beginning. We're a seed-stage company with an early design partner cohort, pre-launch funding, and a strong point of view on how external exposure monitoring should work.
What we don't have: a big sales team, a marketing budget, or a bloated feature roadmap. What we do have: a working monitoring platform, real findings from real customers, and direct access to the people who built it.
If you request a demo, you'll talk to someone on this page — not an SDR. If you find a bug, you'll get a response from Marcus. If you have a feature request, Elena reads every one.
Work with us directlyWe only look at what's externally visible — the same view an attacker has. This keeps us focused on real exposure, not internal noise, and means we need zero access to your environment to do our job.
Our early design partners are working security teams at mid-market companies. Their specific gaps — not abstract threat models — shape what we build. When something changes, we hear about it fast.
We see things like leaked credentials and exposed assets as part of the job. We don't expose raw passwords, we don't share findings across tenants, and we don't use your data to train shared models.
Exposure monitoring has false positives. Coverage has gaps. We document what we catch and what we miss in our Insights blog. If ThreatPulsar isn't the right tool for your situation, we'll say so.
We're a small team at an early stage. If you're a detection engineer, security researcher, or backend engineer who cares about external exposure monitoring, we'd like to talk.