The problem
Security teams can't see or stop what their AI agents actually do in production, like hidden prompt injections
What they do
Runtime security that watches, governs and blocks enterprise AI agent actions
Traction Revenue up 8x and customers 5x since Jan 2026 launch (company claim); Lemonade, Dun & Bradstreet
Hiring trend
- Open roles
- n.a.
- Ops roles
- 2
- Headcount
- ~31
Headcount ~23 → ~31 since Jan 2026 launch (Calcalist); no public job board, ~4 openings seen (careers@reinsec.io)
Funding
- Last round
- $25M
- Stage
- Series A
- Date
- Oct 2026
Led by Glilot Capital, Sienna Venture Capital
- Hiring0No public job board count on file
- Funding recency+1.5Series A · $25M, Oct 2026 (this month): 6 months or less = +1.5
- Traction—Revenue up 8x and customers 5x since Jan 2026 launch (company claim); Lemonade, Dun & Bradstreet
- Red flags—None on file
- Total3.25Stored score → Steady (1.5–3.49)
Hiring and funding from the stored fields add up to +1.5. The stored score of 3.25 includes a judgment call the fields don't capture (often a boundary month or a round we don't count), so traction and red-flag points can't be split out exactly.
Distance (Unproven) is a separate read on how long the lead can last. It doesn't change the score.
Distance
Unproven · edge: hard to leave
Nine months past launch with ~31 staff and no disclosed revenue base; runtime agent security is a crowded, consolidating category with bigger security vendors moving in, so too early to judge staying power.
Sources: Rein: $25M Series A, 8x revenue since Jan 2026 launch (Oct 2026) ↗ · TechLens: Rein Series A, nine months after $8M seed; no revenue base disclosed (Oct 2026) ↗
Last checked Oct 15, 2026