In short: Reco (independent; venture-backed; latest round (September 2026) not named by the company; founded 2020) and Valence Security (independent; venture-backed, Series A; founded 2021) both publish documentation for 13 of the 21 NHI capabilities we track. The public evidence differs on 3: evidence for Reco only on attribution to humans, authorization policy and lifecycle management. Records checked 16 October 2026. This is a reading of what each company has published, not a score or a recommendation.
This page puts two company records side by side. It shows what public evidence establishes for each, using the same labels as the profiles. It gives no score, no ranking and no recommendation. Read the full records for sources: Reco and Valence Security.
Company facts
Scroll sideways to see all columns.
| Fact | Reco | Valence Security |
|---|---|---|
| Record name | Reco | Valence Security |
| Ownership | Independent | Independent |
| Stage | Venture-backed; latest round (September 2026) not named by the company | Venture-backed, Series A |
| Founded | 2020 (Publicly disclosed) | 2021 (Publicly disclosed) |
| Headquarters | Altamonte Springs, Florida (US office and 2026 release dateline); offices in Tel Aviv and Chisinau (Publicly disclosed) | Not stated on the company website. Press release datelines: Tel Aviv (2021), San Francisco (2022), New York (2025) (Sources conflict) |
| Total funding | $140M (stated, September 2026) (Publicly disclosed) | $32M (as stated in October 2022) (Verified) |
| Categories in our directory | SaaS security, AI agent security, NHI discovery (SaaS) | SaaS security posture, SaaS identity threat detection, AI security posture (SaaS) |
| Record verified | 2026-10-16 | 2026-10-16 |
Why these two are compared
Each record lists the other as a direct competitor in our analysis of product scope.
- The Reco record describes Valence Security as: SaaS security with focus on integrations and non-human identities.
- The Valence Security record describes Reco as: SaaS security with AI agent coverage.
Capability evidence, side by side
Documented by vendor means the company's own documentation describes the capability. It is not independent verification and says nothing about depth. Not publicly verified means we did not find public documentation. It does not mean the product lacks the capability.
Scroll sideways to see all columns.
| Capability | Reco | Valence Security |
|---|---|---|
| NHI discovery | Documented by vendor | Documented by vendor |
| NHI inventory | Documented by vendor | Documented by vendor |
| Ownership assignment | Documented by vendor | Documented by vendor |
| Attribution to humans | Documented by vendor | Not publicly verified |
| Access analysis | Documented by vendor | Documented by vendor |
| Authorization policy | Documented by vendor | Not publicly verified |
| Least privilege | Documented by vendor | Documented by vendor |
| Lifecycle management | Documented by vendor | Not publicly verified |
| Credential rotation | Not publicly verified | Not publicly verified |
| Secrets management | Not publicly verified | Not publicly verified |
| Certificate management | Not publicly verified | Not publicly verified |
| Service accounts | Documented by vendor | Documented by vendor |
| API keys | Documented by vendor | Documented by vendor |
| OAuth apps and tokens | Documented by vendor | Documented by vendor |
| Workload identity | Not publicly verified | Not publicly verified |
| Cloud identity | Not publicly verified | Not publicly verified |
| AI agents | Documented by vendor | Documented by vendor |
| Agent governance | Documented by vendor | Documented by vendor |
| Monitoring and detection | Documented by vendor | Documented by vendor |
| Remediation | Documented by vendor | Documented by vendor |
| Audit evidence | Documented by vendor | Documented by vendor |
Where the public evidence differs
- Public evidence found for Reco and not for Valence Security: Attribution to humans, Authorization policy, Lifecycle management.
- Public evidence found for Valence Security and not for Reco: none.
- Public evidence found for both: NHI discovery, NHI inventory, Ownership assignment, Access analysis, Least privilege, Service accounts, API keys, OAuth apps and tokens, AI agents, Agent governance, Monitoring and detection, Remediation, Audit evidence.
- Not established for either from public sources: Credential rotation, Secrets management, Certificate management, Workload identity, Cloud identity.
A difference in this list is a difference in what each company has published, as read by us on the verification dates above. It is not a count of features and should not be read as a score. Confirm any capability that matters to you with the vendor and in a proof of concept.
Recent developments
Reco
- 29 September 2026: Reco announces $55M in additional funding including AT&T Ventures. The company described AT&T Ventures' participation as a strategic investment and named Forestay and Quadrille Capital as new investors. It stated total funding of $140M and quoted AT&T's CISO. [source]
- 1 August 2026: Reco named an OpenAI Select Partner. IT Brief reported the designation within OpenAI's partner network. A first-party confirmation was not located. [source]
- 25 June 2026: Reco launches Agent Security. The product discovers agents and related non-human identities and maps the access they rely on. [source]
Valence Security
- 21 July 2026: Integration with Anthropic's Claude Compliance API announced. A company post describes visibility into Claude Enterprise and Claude Platform usage, including the human and non-human identities with access. [source]
- 5 May 2025: State of SaaS Security report for 2025 to 2026 published with the Cloud Security Alliance. The company reports that 46% of organisations surveyed struggle to monitor non-human identities. These are survey figures published by the company. [source]
- 28 January 2025: Reseller partnership with GuidePoint Security announced. GuidePoint customers can buy the Valence platform through the reseller. [source]
Positioning
Reco
What the company says: Reco describes itself as an agentic security company that discovers, governs and secures AI agents across the business applications where they run. [source]
Our analysis: Agents inside SaaS platforms act through OAuth grants, API keys, service accounts and delegated user access. Reco's documented product maps those access paths per agent, names who deployed the agent, and supports scope reduction or revocation. It addresses NHI risk through the agent and SaaS integration layer, not through credential issuance or vaulting.
Valence Security
What the company says: Valence describes itself as a SaaS and AI security platform that finds and fixes risks across applications, configurations, identities and AI agents, with remediation that involves business users. [source]
Our analysis: Valence addresses non-human identities that live inside SaaS: third-party integrations, OAuth grants, service accounts and AI agents. Its documented product finds them, assesses their permissions and offers workflows to reduce or remove access. It does not present itself as a cross-environment NHI inventory or as a credential manager.
Common questions
What is the difference between Reco and Valence Security?
Agents inside SaaS platforms act through OAuth grants, API keys, service accounts and delegated user access. Reco's documented product maps those access paths per agent, names who deployed the agent, and supports scope reduction or revocation. It addresses NHI risk through the agent and SaaS integration layer, not through credential issuance or vaulting. Valence addresses non-human identities that live inside SaaS: third-party integrations, OAuth grants, service accounts and AI agents. Its documented product finds them, assesses their permissions and offers workflows to reduce or remove access. It does not present itself as a cross-environment NHI inventory or as a credential manager. In published documentation, public evidence was found for Reco and not for Valence Security on attribution to humans, authorization policy and lifecycle management. That is a difference in what each company has published, not a feature count or a ranking.
Who owns Reco and Valence Security?
Reco: Independent. Valence Security: Independent. Ownership is taken from company announcements and filings and is dated on each record.
Do Reco and Valence Security support AI agents?
AI agents: Reco, documented by vendor; Valence Security, documented by vendor. Agent governance: Reco, documented by vendor; Valence Security, documented by vendor.
Which is better, Reco or Valence Security?
We do not rank or recommend either company, and no company pays for coverage. The better fit depends on which identity types you need covered, where your credentials live, and what evidence your auditors expect. Put the questions on this page to both vendors and confirm the capabilities that matter in a proof of concept.
What are the alternatives to Reco and Valence Security?
Other companies in the same categories of our directory, listed alphabetically and not ranked: AppOmni, Cisco Identity Intelligence and Duo, CrowdStrike Falcon Next-Gen Identity Security, Grip Security, Nudge Security, Obsidian Security, Semperis and Silverfort, and 3 more in the company directory. Each has a sourced record on this site.
Questions to put to both
- Which identity types are discovered without an agent or manual import, and which need configuration?
- How is a named human owner assigned to each non-human identity, and what happens when that person leaves?
- What evidence can be exported for an audit, and in what format?
- Which capabilities are generally available today, and which are in preview?
- Who owns the company today, and what has been said about the product roadmap since any change of ownership?
See the methodology for how records are researched, and the list of all comparisons.