NewCore

Name: NewCore
Brand: NewCore

AI Native

Security-first identity platform for the agentic era, rebuilt from the ground up for humans and AI agents

Est 2026|Valuation $300M|1 Ref Customers

LinkedIn 588|Website|FTEs 60|HQ Tel Aviv, Israel

01Competitive Landscape

| Aspect | NewCore | Microsoft Entra ID | Okta Workforce Identity Cloud | |--------|---------|-------------------|------------------------------| | Starting Price | Not publicly posted | Published per-user tiered pricing available from the vendor | Published suite-based per-user pricing available from the vendor | | Suitable For | Early adopters needing agent identity as a core capability; organizations exploring AI-agent governance with workforce-like identity controls | Microsoft-first shops that want tight integration with M365/Azure ecosystem and broad enterprise adoption | Vendor-neutral IAM for mixed environments; mature app ecosystem and polished admin experience | | Key Strength | Product positioning focused on AI-agent identities and split-key security architecture claims | Deep native integration into Microsoft ecosystem; widely deployed; strong baseline capabilities and roadmap velocity | Mature IAM product focus; broad SaaS integrations; strong workforce SSO/MFA/lifecycle workflows | | Key Weakness | Very early commercial maturity; limited public trust/compliance artifacts; unclear pricing; limited public customer proof | Licensing complexity; some features require higher tiers; can be sufficient for many standard use cases but may not be best-in-class in every niche | Can be costly at scale; suite/annual contract dynamics; overlaps with Microsoft licensing for Microsoft-heavy stacks | - Narrative analysis - Where NewCore appears differentiated - Managing agent identities as a primary design target, rather than a bolt-on feature. - Emphasis on reducing single points of compromise via split-key / Secure Split Key architecture (vendor-claimed; limited public technical substantiation to date). - Where incumbents may still be stronger today - Breadth and maturity of integrations, administrative tooling, and enterprise assurance artifacts (e.g., commonly expected audit and compliance reports, long track records, broader review footprints). - Proven scale: Okta and Microsoft operate very large identity footprints; NewCore has not been publicly demonstrated at that scale. - Customer evidence comparing vendors - For Microsoft vs Okta, industry peer-review summaries highlight Microsoft’s strong integration with Microsoft products in Microsoft-centric organizations, while noting that specialized products can outperform incumbents in specific functions. These comparisons do not include NewCore directly.

01Competitive Landscape

Aspect	NewCore	Microsoft Entra ID	Okta Workforce Identity Cloud
Starting Price	Not publicly posted	Published per-user tiered pricing available from the vendor	Published suite-based per-user pricing available from the vendor
Suitable For	Early adopters needing agent identity as a core capability; organizations exploring AI-agent governance with workforce-like identity controls	Microsoft-first shops that want tight integration with M365/Azure ecosystem and broad enterprise adoption	Vendor-neutral IAM for mixed environments; mature app ecosystem and polished admin experience
Key Strength	Product positioning focused on AI-agent identities and split-key security architecture claims	Deep native integration into Microsoft ecosystem; widely deployed; strong baseline capabilities and roadmap velocity	Mature IAM product focus; broad SaaS integrations; strong workforce SSO/MFA/lifecycle workflows
Key Weakness	Very early commercial maturity; limited public trust/compliance artifacts; unclear pricing; limited public customer proof	Licensing complexity; some features require higher tiers; can be sufficient for many standard use cases but may not be best-in-class in every niche	Can be costly at scale; suite/annual contract dynamics; overlaps with Microsoft licensing for Microsoft-heavy stacks

Narrative analysis
- Where NewCore appears differentiated
  - Managing agent identities as a primary design target, rather than a bolt-on feature.
  - Emphasis on reducing single points of compromise via split-key / Secure Split Key architecture (vendor-claimed; limited public technical substantiation to date).
- Where incumbents may still be stronger today
  - Breadth and maturity of integrations, administrative tooling, and enterprise assurance artifacts (e.g., commonly expected audit and compliance reports, long track records, broader review footprints).
  - Proven scale: Okta and Microsoft operate very large identity footprints; NewCore has not been publicly demonstrated at that scale.
- Customer evidence comparing vendors
  - For Microsoft vs Okta, industry peer-review summaries highlight Microsoft’s strong integration with Microsoft products in Microsoft-centric organizations, while noting that specialized products can outperform incumbents in specific functions. These comparisons do not include NewCore directly.

Aspect

NewCore

Microsoft Entra ID

Okta Workforce Identity Cloud

Starting Price

Not publicly posted

Published per-user tiered pricing available from the vendor

Published suite-based per-user pricing available from the vendor

Suitable For

Early adopters needing agent identity as a core capability; organizations exploring AI-agent governance with workforce-like identity controls

Microsoft-first shops that want tight integration with M365/Azure ecosystem and broad enterprise adoption

Vendor-neutral IAM for mixed environments; mature app ecosystem and polished admin experience

Key Strength

Product positioning focused on AI-agent identities and split-key security architecture claims

Deep native integration into Microsoft ecosystem; widely deployed; strong baseline capabilities and roadmap velocity

Mature IAM product focus; broad SaaS integrations; strong workforce SSO/MFA/lifecycle workflows

Key Weakness

Very early commercial maturity; limited public trust/compliance artifacts; unclear pricing; limited public customer proof

Licensing complexity; some features require higher tiers; can be sufficient for many standard use cases but may not be best-in-class in every niche

Can be costly at scale; suite/annual contract dynamics; overlaps with Microsoft licensing for Microsoft-heavy stacks

NewCore

01Competitive Landscape

02Market Map

01Competitive Landscape

02Market Map