Acsense

**Product and problem.** Acsense addresses a failure mode that conventional disaster-recovery programs often underweight: an organization may keep its applications and databases available while losing the identity configuration that grants access to them. A corrupted Okta or Entra tenant can affect workforce logins, customer authentication, service accounts, application assignments, policies, groups, tokens, and privileged roles at once. Acsense positions itself as an Identity Control Plane above the identity provider, with continuous backup, point-in-time comparison, granular restoration, configuration governance, and tested failover. The product is therefore more specific than a generic SaaS backup service and more operational than an identity-governance dashboard. It is designed to keep an enterprise operational during the aftermath of ransomware, destructive administrator actions, accidental changes, identity-provider outages, or a compromised automation workflow.

**Core technology and operation.** The public product materials describe continuous capture of IAM objects, relationships, configuration, and tenant posture into immutable, encrypted, air-gapped storage. Acsense preserves the context needed to restore a working identity environment rather than merely exporting a list of users: administrators can investigate changes between points in time, identify drift, roll back selected configuration, or recover an entire tenant. Its architecture also includes a secondary or hot-standby tenant, continuous replication, automated failover, least-privilege controls, audit logs, and recovery-health checks. The company advertises roughly ten-minute RPO and RTO targets and drift detection in ten minutes or less; these are product claims, not independently measured benchmarks in the public record. The platform brief also describes relationship-aware rollback, sandbox seeding, configuration promotion across preview, development, and production, and automated recovery testing. Current messaging extends the model to non-human identities such as service accounts, API tokens, OAuth grants, and AI-agent credentials.

**Market, customers, and go-to-market.** Acsense sells into the intersection of identity security, IT disaster recovery, SaaS data protection, compliance, and business continuity. The likely economic buyer is a CISO, CIO, identity administrator, infrastructure-resilience owner, or regulated-enterprise compliance team that cannot accept identity as a single point of failure. The platform begins with Okta and Microsoft Entra ID coverage and is presented as extensible to additional identity providers, allowing a land-and-expand motion inside organizations with hybrid identity estates. Acsense’s public website displays customer or trust logos including Elevance, Delta Dental, Fiverr, monday.com, Aristocrat, Varonis, and Coralogix, although the public material does not disclose contract scope, revenue, deployment size, or whether every logo represents a current production customer. AWS Marketplace availability and a demo-led sales motion can reduce procurement friction for enterprises with existing cloud commitments, while U.S. sales and services, Romanian operations, and Israeli product management support an international enterprise route to market.

**Traction, funding, and validation.** Acsense announced a $5 million seed round in January 2023 led by Joule Ventures, with participation from Gefen Capital, Fusion, and independent investors. That announcement said the capital would support additional IAM-vendor integrations, market expansion, and hiring, and described the company as founded in 2020 by Dell EMC veterans. Startup Nation Finder’s public Fresh Fund portfolio page lists Acsense as an Israeli B2B company with an 11-50 employee range, seed stage, and $5 million raised. Acsense’s current website reports sub-ten-minute drift detection, approximately ten-minute RTO/RPO indicators, SOC 2 and ISO 27001 credentials, and FedRAMP High authorization in June 2026. Those compliance and public-sector signals are meaningful third-party procurement enablers, but the public record does not expose an audit report, authorization boundary, customer renewal data, annual recurring revenue, or independent performance test. The evidence supports real commercialization and validation while leaving scale economics open.

**Founders and team.** The official company page identifies Muli Motola as co-founder and CEO, Daniel Naftchi as co-founder and CTO, and Itzik Hanan as co-founder and COO. The company describes the founding team as former EMC veterans with experience implementing IAM systems and handling identity disasters, a background that fits the product’s emphasis on recovery mechanics rather than only detection. The public team page also names Ido Niv as head of R&D, Robert Tuohey as VP Sales Americas, and Brendon Rod as head of marketing. Its advisory board includes Sara Zohn, presented with EMC software-engineering operations experience; Ran Nahmias, associated with Check Point, IONIX, and Tamnoon; Tamir Harduf, associated with Kenna, Axis, Check Point, and Juniper; and Gabby Nizri, whose prior company Ayehu was acquired by Resolve. This is a relevant enterprise-security network, although biographies do not substitute for diligence on retention, engineering depth, and the founders’ ownership or prior exit outcomes.

**Competitive dynamics and edge.** Acsense competes with identity-threat-detection and directory-recovery vendors such as Semperis, broad cyber-recovery platforms such as Rubrik and Veeam, identity-governance suites such as Saviynt, and native backup or export features from Okta and Microsoft. Its strongest potential edge is the combination of provider-aware dependency preservation, independent air-gapped copies, precise tenant-level rollback, hot-standby failover, and continuous proof that recovery actually works. That package targets the gap between “the identity provider is highly available” and “the customer can restore its own tenant’s policies, relationships, secrets, and access graph after compromise.” The edge is not automatically durable: major identity providers can expand native recovery, large backup vendors can add IAM modules, and regulated buyers may prefer a consolidated platform. Acsense must also prove that recovery is safe when privileged credentials, federation trust, encryption keys, and downstream application dependencies are themselves damaged.

**Defense, security, and resilience relevance.** Acsense has credible dual-use value because identity infrastructure is a control layer for commercial enterprises, government systems, defense contractors, and critical infrastructure alike. A military logistics application, emergency-communications service, hospital network, or energy operator can remain technically online yet become operationally inaccessible if its identity tenant is altered or unavailable. Immutable recovery, independent separation from the primary provider, auditable change history, least-privilege administration, and rehearsed failover can reduce downtime from ransomware, insider action, supply-chain compromise, destructive automation, or a cloud-control-plane incident. The platform’s support for machine identities and AI-agent credentials is particularly relevant as autonomous workflows gain access to operational systems, though Acsense is not itself an AI model, weapons system, or fielded defense platform. Public evidence supports defensive cyber resilience and continuity for mission-support environments; it does not establish classified deployments, Israeli Ministry of Defense contracts, or military operational use. That distinction keeps the strategic case strong without overstating it.

**Stage, trajectory, and diligence risks.** Acsense should be classified as mid-stage: it has a named product, international sales footprint, a public seed round, listed enterprise references, compliance signals, and a current AWS Marketplace route, but no disclosed scale metrics that would justify mature status. The trajectory is attractive if the company can turn IAM recovery from an exceptional incident-control purchase into a recurring resilience standard for every human and machine identity. Key diligence questions are: 1) validate the FedRAMP High scope and whether it materially shortens federal procurement; 2) test recovery fidelity across complex Okta and Entra relationships, federation, privileged roles, tokens, and downstream applications; 3) verify RTO/RPO and drift claims under destructive scenarios; 4) separate logo-level references from paying production deployments and quantify net retention; and 5) understand pricing, gross margins, provider API dependence, storage isolation, key management, and competitive response. The main risks are long enterprise cycles, trust-sensitive access to identity systems, platform concentration, rapidly changing AI-agent controls, and the possibility that native identity vendors or broad backup suites absorb the category. The public record supports a strategically relevant Israeli cybersecurity startup, while current financial scale remains Unknown.