IndyKite
Identity for agents, not a shared service account.
Most agent demos run as one over-privileged user. IndyKite keeps people, orgs and permissions as data, so an agent acting for a customer, case worker or vendor sees only what that identity may see.
Founded 2022 · Founder in the Salesforce MVP Hall of Fame · Dubai HQ · Kochi studio
- 01Models · Claude, Gemini, OpenAI, Bedrock
- 02Agentic systems · Agentforce, CrewAI, ADK, A2A
- 03Agentic memory · Neo4j, Cognee, IndyKite
- 04Automation and voice · n8n, Retell
- 05Deployment and governance · identity, evals, policy, audit
What we put in
The work on this layer.
The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.
Shared account or identity
Who is the agent acting for?
One service account
Identity per request
- Sees every customer’s records
- Sees only what that person may see
- Logs say ‘agent’ did it
- Logs name the person and the agent
- One leak exposes everything
- A mistake stays inside one slice
Use cases
Where identity shows up in the work.
Typical first jobs.
Example
Vendor portal manager at a Saudi retailer
Today: Suppliers must see their own orders and nobody else’s.
After: The agent answers each supplier from that supplier’s records only, and the log names who asked.
Example
Service centre lead at a Dubai government-services provider
Today: Case workers share one login for the assistant.
After: Each worker’s request runs under their own permissions, so a case outside their team stays closed.
Questions
What we actually say.
- Is IndyKite a replacement for Okta or Azure AD?
- No. It sits with your existing IdP. The graph adds relationship-aware authorization for agents, which a directory of users does not do on its own.
- Why is this listed under memory?
- Because authorization for agents is knowledge: who is related to what, and what that allows. It is memory the agent is not allowed to ignore.
- Do small pilots need this?
- Not on day one of a single internal copilot. You need it the moment an agent acts for a customer or a partner, or when two agents share data.
The brief
Agents still sharing one service account?
We will map the identities your agents act for and tell you whether IndyKite belongs in the first production cut. The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days.