IndyKite

• Capital has been quiet since February 2022 while the company runs offices on two continents, so a hiring freeze, an office closure or a distressed round would show the pace was constraint rather than efficiency.
• Every account of the Rockwell Automation, PACCAR and Deutsche Telekom deployments traces to IndyKite or Neo4j, so any of those names leaving the customer page without replacement would leave the traction record thinner than it currently looks.
• Of the three products announced in February 2025 the current product pages name AgentControl, so another turnover of the lineup within a year would confirm the portfolio changes faster than enterprise buyers can standardize on it.
• The Agent Gateway assumes agents speak the Agent-to-Agent protocol, so a market that settles on a different agent transport would strand its enforcement point.
• Okta or Ping Identity shipping delegation-chain checks inside identity products enterprises already own would remove the reason to add a separate enforcement layer.
• The reviewed record carries one third-party technical assessment, a KuppingerCole Executive View from September 2022 covering the authorization product, so the agent work still has no independent evaluation behind it.

Enterprises putting AI agents into production hit a permission problem their existing tools were not built for. An agent is not a user with a fixed role. It acts on someone's behalf, calls other agents, and reaches data across systems that were never joined. IndyKite's head of customer and partner experience puts the point bluntly, saying the industry has been trying to make role-based access work since the early 1990s and never got it right for humans.

The buyer is a large enterprise with data spread across systems and a reason to care who touched what. IndyKite's published customer accounts sit in manufacturing and heavy equipment, where the problem it describes is reconciling licences, equipment records and customer records that live in separate systems and cannot be tied back to each other.

The pain itself is argued rather than measured. The reviewed sources carry IndyKite's framing and its graph database partner's, and no independent survey, incident record or market sizing quantifies how many enterprises are stuck where the company says they are. [s20, s1, s6]

The platform is a graph with three ways to act on it. Identities, data assets, relationships such as ownership and delegation, and contextual signals such as purpose and provenance are modelled together, and Knowledge-Based Access Control derives access decisions by walking those relationships instead of matching a role. ContX IQ exposes the same graph as a runtime API that applications can query and write to, with the authorization check applied at the service itself.

AgentControl is the agent-facing product, and its documented artifact is the Indykite Agent Gateway. One instance is deployed per protected agent, it speaks the Agent-to-Agent protocol rather than behaving as a general proxy, and on each call it introspects the caller's token, exchanges it for a delegated token, queries the graph for the workflows that caller may trigger, and checks that the requested sequence of agents matches one the workflow permits. It writes a decision record naming the human subject, the acting agent, the full chain of actors and the reason.

IndyKite Tags covers the content side. It tags unstructured material from SharePoint, OneDrive, Box, Google Workspace, Slack and Confluence, flags personal, health, financial and confidential material, and screens prompts for injection attempts before they reach a model.

The documentation carries the detail an implementer needs. The gateway ships as a container image with four published deployment layouts, a configuration reference and audit formats, and the developer resources list a Terraform provider and software development kits. [s2, s5, s4, s11, s13, s22, s23]

IndyKite competes where authorization is pulled out of applications and run as a service, beside vendors such as Cerbos and Axiomatics whose people hold the same standards-body seats. Its founder co-founded ForgeRock, which Tech.eu counts among the identity IPOs beside Okta and Ping Identity. Its difference is the substrate. Policies are evaluated by traversing relationship paths in a graph, which is the approach KuppingerCole described in September 2022 when it reviewed Knowledge-Based Access Control and called it progressive.

The company works the standards rather than around them. Its authorization interface advertises AuthZen, OAuth and OpenID, and MCP, the gateway implements the Agent-to-Agent protocol, and the OpenID Foundation lists Alex Babeanu of IndyKite as a chair of its AuthZEN working group beside chairs from Bloomberg, Axiomatics, Cerbos and CrowdStrike. Standards work buys credibility with architects and, by the same token, lowers the cost of leaving for anything built on those interfaces.

The self-description has travelled a long way. The newsroom traces an identity layer for Web3 in October 2021, an identity-powered AI enterprise data platform in February 2024, an AI Control Suite in February 2025, and a runtime control layer for agentic AI today. That 2025 suite announced RagProtect, AgentControl and TrustScore, and of those three the current product pages name AgentControl. A buyer tracking the lineup has had to re-learn what to ask for. [s2, s5, s17, s18, s19, s8, s10]

The named customers are large enterprises. Rockwell Automation, PACCAR, Deutsche Telekom and Reitan Retail appear with attributed executive quotes, and Neo4j publishes a customer story describing what IndyKite built at Rockwell Automation, where licensing data, customer records and equipment data had sat in separate systems, and at PACCAR, where the company needed data tied to truck chassis, components, wear and tear and mean time to failure brought together.

Each of those accounts originates with IndyKite or with Neo4j, the graph database vendor IndyKite lists as a subprocessor and partners with. The reviewed sources carry no independent report of a deployment, no revenue figure and no customer count, so the scale behind the names stays unmeasured.

Partnerships are what the reviewed sources document. IndyKite announced an alliance with Enterprise Knowledge in May 2026 and a Neo4j partnership in December 2025, and the Linux Foundation named it an Automotive Grade Linux member in April 2022. The pattern reads as credible enterprise motion, thinly corroborated. [s1, s20, s8, s19, s12]

Lasse Andresen founded IndyKite in 2021. Tech.eu describes him as a former Sun Microsystems chief technology officer, reports that he co-founded ForgeRock, and counts ForgeRock among the identity IPOs alongside Okta and Ping Identity. Biometric Update independently carries the ForgeRock co-founding, so the strongest claim on his record rests on outside reporting rather than on the company alone.

Scott McNealy, who co-founded Sun Microsystems, is reported by both Tech.eu and Biometric Update as a formal advisor to IndyKite. The 2024 acquisition of 3Edges brought its co-creator Derek Small into the company as head of customer, partner and developer experience, and the OpenID Foundation lists Alex Babeanu of IndyKite among the chairs of its AuthZEN working group.

Below the founder the record thins. The company lists four functional heads by name and role, and the reviewed sources carry no independent account of their backgrounds. [s15, s16, s6, s9, s18]

IndyKite runs a live trust center listing SOC 2 Type 1 and Type 2, ISO/IEC 27001:2022, GDPR, HIPAA and EU-U.S. Data Privacy Framework participation, and it publishes the underlying artifacts, including a 2026 ISO/IEC 27001:2022 certificate of registration and SOC 2 Type 2 reports. The controls list names penetration testing and cybersecurity insurance.

The certifications arrived on an ordinary enterprise schedule. The newsroom records a SOC 2 milestone in September 2024, SOC 2 Type 2 in June 2025 and ISO/IEC 27001 in March 2026, which closes a gap KuppingerCole named in September 2022 when it listed certifications in progress among the challenges.

The trust center also discloses the dependency chain, naming Google Cloud Platform as the cloud platform for production services, Neo4j Aura as the hosted graph database, and GitHub for source control. It records a customer-chosen storage location against both the cloud platform and the graph database. [s12, s7, s8, s17]

Add analyzed competitors to compare them side by side with IndyKite.

IndyKite aims at large enterprises with data scattered across systems, and its published wins name retail, manufacturing, heavy equipment and telecommunications. Rockwell Automation, PACCAR, Deutsche Telekom and Reitan Retail are the accounts the company puts forward, each represented by a named senior executive.

The segmentation is coherent but narrow in evidence. Every named account in the reviewed sources was surfaced by IndyKite or by its database partner, which is a customer list rather than a market position, and those sources say nothing about deal size, contract length or how many customers sit behind the names.

Geography is split across San Francisco, Calgary, Oslo and Stavanger. Two of the four offices are Norwegian and San Francisco is the headquarters the company gives.

The mechanism is specific enough to test. The Agent Gateway introspects a caller's token with the customer's identity provider, obtains an actor token for the protected agent, exchanges the two for a delegated token, queries the graph for workflows the caller may trigger, and rejects the call when the requested sequence of agents does not match a permitted chain. Agents are modelled as nodes with owners, skills and tools, and they hold no standing privilege of their own.

That design answers a gap the company describes. An agent calling another agent carries an actor chain, and IndyKite's own head of customer and partner experience argues that role-based access has never worked well even for humans and scales worse when agents can be created by the thousand. Placing the check in a gateway per agent, rather than inside the agent, keeps enforcement outside code the agent's author controls.

The AI in the product is the subject rather than the method. IndyKite Tags does classification work on unstructured content and screens prompts for injection attempts, but the platform's advantage is the graph and the delegation model, not a proprietary model of its own. The reviewed sources describe no model IndyKite trains.

What the reviewed sources document is partnership activity rather than a sales channel. IndyKite announced an alliance with Enterprise Knowledge in May 2026 to carry agentic delivery into enterprises, a Neo4j partnership in December 2025, and the Linux Foundation named it an Automotive Grade Linux member in April 2022.

The developer surface is real but secondary. The homepage links a documentation site, a sandbox, a forum and software development kits, and the docs carry a Terraform provider, which is the equipment of a self-serve motion. The named accounts are large enterprises, and the reviewed sources do not say how any of them was won.

What the reviewed sources do not show is a repeatable pattern. A short list of named accounts across five years, no disclosed pipeline and no partner-sourced revenue leave the motion described rather than demonstrated.

The reviewed sources carry no pricing. The documentation describes organizations, projects and service accounts without naming a unit of charge.

The absence is consistent with the buyer. The reviewed sources name large enterprise customers and publish no figure, list or otherwise, for what any of them pays.

For a reader, the consequence is that unit economics cannot be assessed from the public record at all. The reviewed sources carry no per-seat, per-decision or per-node figure.

Delivery is split between a hosted platform and software the customer runs. The trust center lists Google Cloud Platform as the cloud platform for IndyKite production services and Neo4j Aura as the hosted graph database, and records a customer-chosen storage location against each.

The gateway is the customer's to operate. It ships as a Docker image, runs as a standalone container, under Docker Compose, as a Kubernetes pod or as a sidecar beside the protected agent, and one instance is deployed per agent. That last constraint is the operational cost of the design: an estate of many agents becomes an estate of many gateways to deploy, configure and upgrade.

Prerequisites are ordinary but not trivial. The gateway needs an identity provider supporting token exchange, token introspection and the client credentials grant, plus a workflow modelled in the graph and a ContX IQ query prepared in advance.

The trust posture is complete for the stage. A live trust center lists SOC 2 Type 1 and Type 2, ISO/IEC 27001:2022, GDPR, HIPAA and EU-U.S. Data Privacy Framework participation, and it publishes the certificate of registration and the SOC 2 reports rather than only badges.

The published controls extend past the certificates. Penetration testing, cybersecurity insurance, change management and data classification appear on the controls list, and the subprocessor list names four vendors with the function each performs.

The gap KuppingerCole flagged in September 2022, certifications in progress, has closed. The trust center records that penetration testing is performed, and the reviewed sources carry no report or summary of what it found.

IndyKite advertises open standards on the surfaces buyers integrate against. Its authorization service names AuthZen, OAuth and OpenID, and MCP, the gateway implements the Agent-to-Agent protocol, and the OpenID Foundation lists Alex Babeanu of IndyKite as a chair of its AuthZEN working group beside chairs from Bloomberg, Axiomatics, Cerbos and CrowdStrike.

Content integrations are the other half of the ecosystem. IndyKite Tags connects to SharePoint, OneDrive, Box, Google Workspace, Slack and Confluence, pulling content, metadata and permissions.

Standards adherence cuts both ways for durability. A customer that adopted IndyKite through AuthZEN or the Agent-to-Agent protocol keeps those call interfaces if it moves, although the graph model, the workflow definitions, the policies and the ContX IQ queries behind them would still have to be rebuilt.

The founder's record is the strongest asset in the file. Tech.eu reports that Lasse Andresen co-founded ForgeRock, counts ForgeRock among the identity IPOs beside Okta and Ping Identity, and describes him as a former Sun Microsystems chief technology officer. Scott McNealy, who co-founded Sun, is reported by both Tech.eu and Biometric Update as a formal advisor.

The 2024 acquisition of 3Edges bought people as much as product. Derek Small, who co-created 3Edges, joined as head of customer, partner and developer experience, and now speaks for the company in its partner material.

Depth below that is undocumented. Four functional heads are listed by name and role, with no independent record of what they built before, and the reviewed sources give no headcount more recent than the roughly sixty staff the press reported in February 2022.