Company — Rimator, LLC

The story behind the current.

Rimator wasn’t planned in a boardroom. It started in the trenches in 2019 — port scans, manual rework, and a question that wouldn’t go away: how do good teams keep missing things?

OriginConcept 2019 — to market 2026 HeadquartersNorth Royalton, Ohio Built byVirtus Cybersecurity ComplianceSOC 2 Type II — in progress
Bogdan Salamakha, founder of Rimator

Bogdan Salamakha Founder — Rimator · Virtus Cybersecurity

Founder story

From port scans to a standing loop.

Chapter 01 · 2019 — The trenches

Scan. Sift. Verify. Repeat.

In 2019 I was in the trenches — working as a penetration tester and cybersecurity engineer, splitting my time between pentests, incident response, and building the tooling that held it all together. The work had a rhythm, and too much of that rhythm was rework: re-running port scans, hand-checking service versions, reconciling results that had shifted since the week before.

And on large projects, things got missed. Not through carelessness — the team was good, and everyone was looking. There was simply more surface than any of us could hold in our heads at once.

Chapter 02 · 2020–21 — The machine

Teach the machine to read the scans.

So we started digging into machine learning — models that could create, analyze, and act on scan data instead of waiting for a human to get around to it. The rework shrank. The misses shrank.

Through 2020 and 2021 the concept became a build: piece by piece it took on more of the testing work itself, from analyzing service versions to acting on what it found. Somewhere in there it stopped being a helper and started being the searcher.

Chapter 03 — The gap

Incident response showed the other half.

Incident response showed me where breaches actually take hold: in the gaps. The organizations I walked into had tools — often excellent ones — and capable teams. But those capabilities were spread across many teams and consoles, and in the spaces between them, things got missed.

It was the same pattern from the scan work, at enterprise scale: nobody misses on purpose. There’s just more surface than attention.

Proof has a shelf life. Nobody was checking the date.

Chapter 04 · 2026 — The loop

Build the thing that closes it.

The build kept evolving until it became Rimator: a standing loop that carries the testing work end to end, then plugs into the controls you already own — EDR, SIEM, cloud, identity — to validate that every attack was actually seen.

Seven years from a frustrated port scan to going to market in 2026. Not another tool on the pile — the thing that tests the pile, continuously, kept honest by its own evidence.

Bogdan Salamakha · Founder, Rimator

Why Rimator

Years of automation. One machine.

Rimator grew out of years of automating the work — scan by scan, process by process — until the pieces started coming together into something that could search on its own. The machine came first. The name had to fit it.

from the Latin rimor — “I probe, I search, I dig into.” The one who searches. Not the one who scanned once, filed a report, and moved on.
01 — Born in the field

Built by practitioners

Rimator isn’t a thesis about attacks — it’s years of engagements, and the machine learning built to end their rework, distilled into software. Every campaign it runs is shaped by what actually worked against real estates.

02 — Proof over promises

Verdicts, not vibes

Every claim the loop makes is backed by your own telemetry. We don’t ask you to trust us — we show you what fired and what stayed silent.

03 — One current

Purple by definition

Offense and defense aren’t rival departments here. They’re the same discipline read in both directions — and the product refuses to let them flow apart.

The search never stops. Neither should the proof.

See what the loop finds in your estate — and what your defenses have to say about it.