Building organisational intelligence.
Companies forget what they learn, and AI made it worse: agents that can't explain what they remember or prove they forgot. OctaMem turns what your company knows into memory that is typed, auditable, and removable.
§ 01Principles
Four convictions we keep coming back to.
These are the calls we make whenever a product decision is close. They predate the company. Some are heretical in the vector-database orthodoxy. We’re comfortable with that.
- 01
Memory is infrastructure.
Storage, retrieval, and policy belong at the platform layer, not stuffed into the prompt. The same way databases became infrastructure two decades ago.
- 02
Provenance over similarity.
An agent's answer should be traceable to the records that produced it. Similarity alone is not enough when a legal or real estate decision has to be explained years later.
- 03
Typed beats opaque.
Semantic, episodic, and procedural memory each serve a distinct purpose. Treating them as one bucket of embeddings throws away the structure.
- 04
Audit is not optional.
If your security team can't see what your agents remember, your agents shouldn't be in production. Every read and write is logged, scoped, and removable.
§ 02Origin
Why this exists.
I come from a third-generation real estate family. My grandfather built the family business the old way: every tenant, every negotiation, every hard lesson lived in his ledgers and in his head. When he stepped back, the firm didn’t just lose its founder. It lost recall. I grew up watching a company relearn things it already knew, and pay for the same lesson twice.
Years later I moved from real estate finance into AI. Trading infrastructure, research tools, then agent systems, and the same failure followed with better technology: context drifted, retrieval couldn’t be explained, and nothing could be provably forgotten. I went looking for the layer that should handle this. It didn’t exist. The market optimised for retrieval accuracy, and none of it could answer the question a compliance officer actually asks: what does this agent remember about my client, where did it come from, and can you prove it’s gone?
OctaMem is the layer I wish both generations had. We built it backwards from the compliance requirement. Audit-first. Typed memory: semantic, episodic, procedural. A decay engine that can prove forgetting. The problem is structural, not academic. For my family it was also personal.
Noor Ayob, Founder & CEO
§ 03The team
The team behind it.
Operator-led. The team built persistent systems at scale before agents: databases, audit pipelines, regulated infrastructure. Same discipline, new stack.
Noor Ayob
Founder & CEO
Third-generation real estate background. Masters in Real Estate, real estate finance background. Four years building AI infrastructure, from trading systems to agent tooling. Leads product, GTM, and investor relations.
Ali Parker
CTO
MSc from LMU Munich. Machine learning and NLP. Leads OctaMem's core platform architecture, the FDE engine, and the memory type system.
Gaurav Singh
Backend Engineer
Senior software engineer building agentic AI systems. Owns OctaMem's storage layer for semantic, episodic, and procedural memory. Docker, AWS ECS, agent orchestration.
For procurement, security, or partnership conversations, the fastest path is a direct call.
§ 04In production
Trusted where it counts.
OctaMem is deployed with design partners across real estate and legal, with enterprise pilots in progress. SOC 2 Type II and ISO 27001 audits are underway, with controls in place today. Every deployment ships with full audit logging from day one.
Want to talk?
We’re open to serious conversations.
Whether you’re evaluating us for production, considering joining the design partner cohort, or writing about the space, reach out directly.