MeerKat

Who we are

A security product built by the people who had to live with the problem.

MeerKat is a product of Stack42, LLC, a Kansas company. It exists because the people building it spent their careers defending small and mid-size networks and got tired of finding out too late.

Shawn Wilson, founder of Stack42, LLC
Shawn Wilson
Founder, Stack42, LLC
LinkedIn

Founder

Shawn Wilson

Shawn has spent his career in information technology, and more than twenty years of it in banking, an industry where the cost of a missed intrusion is measured in regulatory findings, customer trust, and real money. That environment shaped how he works. Banking IT means running a production network under continuous examination, where every control has to be documented, defensible, and genuinely working rather than merely purchased. Along the way he has done nearly every job in the stack, from workstations and networks to servers, infrastructure, and the security program that sits over all of it, and he has done it in the kind of organization where the same person who writes the policy also answers the alert at two in the morning.

That mix is unusual, and it is the reason MeerKat exists. Shawn watched the security industry build excellent tools for keeping attackers out while the question of noticing the ones already inside stayed expensive, complicated, or both, which put it out of reach for exactly the organizations that needed it most. MeerKat is his answer: detection that an ordinary business can actually deploy, sized and priced for companies that do not have a security operations center and never will. He still spends his days inside a working IT environment, which keeps the product honest about what real networks and real staff can handle.

The team

A small, deliberate bench

Behind the founder is a supporting team of software engineers who build the proprietary tools MeerKat runs on: the Sensor software, the Portal that every Sensor and Sentry reports to, and the alerting engine that decides who hears about what, and how.

Built, not assembled

The Sensor software, the management Portal, and the alert routing are our own work rather than open-source parts with a logo on them. That is what lets us change how a Sensor behaves as attacker behavior changes.

Small on purpose

A small team ships carefully and answers its own support email. When you report something, it reaches the people who wrote the code, not a tier-one queue.

Based in the USA

MeerKat is designed, built, and supported here. The hardware ships from us, the Portal is ours, and the people answering are too.

We built the product we wanted to buy.Something that watches quietly, speaks only when it matters, and does not need a specialist to run it.

What we believe

Three convictions behind the product

Detection should not be a luxury. Prevention gets the budget, and detection is where most organizations have nothing to show an auditor. A business with no security staff still deserves to find out when someone is inside its network.

A security tool nobody runs is worth nothing. If deploying it takes a project plan, it will sit in a box. MeerKat is a device you plug in, and that is the entire installation.

Quiet is a feature. Alert fatigue is how real warnings get missed. A MeerKat Sensor is untouched by legitimate traffic by design, so when it speaks, it means something.

Want to talk?

Questions about the product, a deployment, or partnering with us are all welcome.

info@stack42.net