Anish Karkare
Founder, AVIKORE
Identity stopped being a directory problem a long time ago — and most identity programs haven't caught up. AVIKORE exists to close that gap.
Anish Karkare is the founder of AVIKORE and an enterprise identity practitioner with more than two decades in technology consulting and over a decade focused on identity and access management. He founded AVIKORE to bring that practitioner perspective — identity strategy, architecture, governance and implementation — to enterprises navigating the shift from human to non-human and agentic identity.
The through-line is a career spent across the evolution of enterprise identity — advising on it, architecting it and being accountable for running it — now focused on the identities that don't look like employees.
- Human identityEmployees, contractors — the actor IAM was built for.
- Machine & workload identityService accounts, workloads, API clients, automation.
- Non-Human IdentityThe governed superset — not a synonym for machine identity.
- Agentic authorityActors that operate through the identities beneath them.
The next identity program has to govern actors that don't look like employees — and were never designed for the way we run identity today.
The perspective
Enterprise identity changed faster than most identity programs did. Human access was hard enough; then workloads, service accounts, machine identities and now AI agents each arrived with their own scale, lifecycle and ownership problems — and most of it was bolted onto a model designed for people.
AVIKORE is deliberately founder-led. The person who assesses your identity fabric is the person who advises on it — no pyramid of juniors, no product to sell and no reseller incentive shaping a recommendation. The independence is structural, not a slogan. The work is architecture-first and vendor-neutral, and it starts by understanding the problem before anyone buys another platform.
Experience
Depth built across the practice of enterprise identity.
Not a job history — the domains that inform how AVIKORE works. Experience spans technology consulting, enterprise delivery, architecture and executive leadership.
Identity & Access
Enterprise IAM, IGA, authentication and access governance — from directories and privileged access to identity architecture and modernization. The plumbing most programs inherit rather than design.
Security Advisory
Working alongside technology and security leadership to move from fragmented, tool-by-tool controls toward a coherent identity program with clear ownership and defensible decisions.
Enterprise Transformation
Connecting strategy to execution across security, enterprise applications, architecture and operating models — where identity has to survive contact with how the business actually runs.
Technology Leadership
Experience spanning advisory, solution architecture, delivery and executive operating responsibility — having both recommended programs and been accountable for running them.
Both sides of the table
The perspective behind AVIKORE comes from working across advisory, solution architecture, program delivery and enterprise operations — having seen security programs both as the advisor recommending them and from inside the organization accountable for operating them. That is a different vantage point from either pure research or pure sales.
- Build
- Integrate
- Govern
- Advise
From the field
Ideas that shaped the AVIKORE thesis.
Questions and observations from years spent working inside identity programs — the ideas now shaping how AVIKORE works.
Who actually owns the service account?
A recurring question in enterprise identity: who created this account, can anyone inventory it, is it tied to a lifecycle, and when was it last used? The overlooked identities are rarely the human ones.
More on LinkedInWhen governance has to become autonomous
As agentic AI enters the enterprise, identity governance is pushed to become proactive, context-aware and continuous — and to reconsider operating models built for periodic, human-paced review.
More on LinkedInIAM was designed around people
Joiner–mover–leaver, manager approvals, quarterly access reviews — the machinery of identity assumes a human on the other end. Non-human identities were bolted onto a model that never anticipated them.
More on LinkedInWriting
Written from practice, not the sidelines.
Anish Karkare authors the AVIKORE Insights — long-form conclusions on non-human and agentic identity, grounded in a practitioner's view of how identity architecture and governance actually work inside the enterprise, and the frameworks AVIKORE uses with clients.
- Non-Human IdentityWhat Is a Non-Human Identity?
- Identity StrategyHuman → Non-Human → Agentic: How Enterprise Identity Is Changing
- Agentic IdentityWhat Is Agentic Identity?
- Non-Human IdentityYou Don’t Have an NHI Tool Problem. You Have an Ownership Problem.
- Identity StrategyYour IAM Program Was Designed for People. Your Enterprise No Longer Is.
- Buying GuideBefore You Buy an NHI Platform, Answer These 10 Questions.
- AdvisoryThe NHI Assessment: What We Would Look for in Your First 30 Days
- Agentic IdentityAI Agents Just Changed the NHI Conversation
Start with a number, not a sales call.
Assess your identity program, or bring a live non-human identity problem to an independent advisor.