The Connected Startup

Neo4j - Brian O'Keefe

Every startup is born to solve a problem. The hard part is everything that breaks on the way there. The Connected Startup is a monthly podcast about those roadblocks, and the founders who discovered a graph was the way through. Each episode traces one company's path from the wall they hit to what they could finally build once their data matched the shape of the problem. We ask every guest the same question: describe the moment you realized a graph was the right tool.

Episodes

  1. Aug 21

    Episode 3: Memorang

    Dr. Yermie Cohen, MD, is the Founder and CEO of Memorang. Over 15 years in education technology, he has developed the curriculum and technology behind hundreds of test-prep programs reaching millions of learners across healthcare, professional licensure, and English proficiency. He pioneered machine-learning-powered spaced repetition in the early 2010s and launched one of the first applications of LLM-generated educational content in early 2022. Today, he builds multi-agent systems and Knowledge Graphs for high-stakes assessment and adaptive learning. He holds multiple engineering degrees from MIT and a Doctor of Medicine from UCLA. Memorang is building **the AI stack for education**, a vertically integrated platform for adaptive learning and assessment. After winning the inaugural Vercel AI Accelerator from a field of thousands of companies, Memorang built an enterprise platform that powers high-stakes assessments and personalized learning experiences at scale. Its Neo4j-powered Knowledge Graph transforms fragmented curricula, content, assessments, and learner data into structured, queryable institutional memory. AI agents use that foundation to automate curriculum development, content generation, psychometric evaluation, and personalization, while web and mobile apps bring those capabilities to market. Memorang is backed by ETS Capital. Yermie has been thinking in graphs since medical school — he'd sketched a graph model for pharmacology and anatomy before graph databases existed as a cloud service. When he set out to build Memorang's AI stack for education, he started with Neptune and moved to Neo4j for Cypher's standardization, deeper traversal performance, and managed hosting. The result: learner-data retrieval that took 8–9 seconds in Postgres now runs in under 500 milliseconds.The deeper insight is how Memorang uses the graph not just to store curriculum and learner data, but to control every AI agent in the system. Rather than relying on semantic matching to route tools, sub-agents, and evaluators — which Yermie puts at around 70–80% accuracy — Memorang encodes subgraph membership in each skill's metadata so the right procedural memory and the right evaluator are called deterministically. For high-stakes assessment, where agent output has to be legally defensible in court, that precision isn't optional. Topics Covered: Building Memorang's knowledge graph from a systems-engineering mindset — why relational databases break at depth two or three in curriculum modelingFrom Neptune to Neo4j: Gremlin's lack of standardization, missing managed hosting, and the hiring challenges that drove the switchThe knowledge graph ontology: thick branches (subject areas), topical nodes, artifacts (items), and user-interaction edgesItem response theory via nearest-neighbor graph traversal: predicting mastery on content a learner has never seenInfinite content generation + graph-weighted curriculum = ROI-based study schedulingGraph-controlled agent routing: encoding subgraph membership in skill YAML front matter to replace semantic tool calling with deterministic dispatchReducing learner-data retrieval from 8–9 seconds to ~500 ms using Neo4j traversal optimization, caching, and query parallelizationHybrid architecture: Supabase (Postgres) + Neo4j + Redis, kept in sync via database triggers, each doing what it does bestApplying conditionally selected evaluators to agent traces for high-stakes, legally defensible assessment contentHill climbing from 50% to 90% agent-output alignment with fewer than 100 human annotations by optimizing narrow, graph-scoped context rather than monolithic system promptsRoadmap: high-profile enterprise launches through end of 2026, general-availability developer platform in early 2027

  2. Aug 21

    Episode 2: Icite

    Wes is the founder and CEO of Icite. Before founding the company, he was CTO at one of the largest managed detection and response (MDR) providers, where running security operations at scale showed him that identity had quietly become the attack surface no SIEM, EDR, or cloud tool could fully see. Icite is a cloud-based cybersecurity company focused on Advanced Identity Threat Detection and Response (ITDR). Where SIEMs and EDRs see events and endpoints, Icite sees identity — resolving who a user is across every IDP, SaaS app, and local account in the environment, then using that graph to power detections no traditional security tool can match. In this episode, Wes walks through how Icite built a three-database architecture — PostgreSQL for structured data, ClickHouse for time series, and Neo4j as the source of truth for identity resolution. The core problem: 90% of breaches tie back to an identity, but a SIEM can never fully resolve who a user is across dozens of IDPs and SaaS apps where the same person appears under different usernames, email formats, and provisioning paths. Graph makes that resolution fast, and it makes the detections that depend on it possible.He also covers why the team migrated from AWS Neptune to Neo4j (deep graph traversal at scale, the GDS library, and Aura's managed hosting), how AI agents writing Cypher queries instead of SQL cut token costs by nearly an order of magnitude, and where Icite is headed next: permission-structure analysis, blast radius scoring, and tracking the identities of AI agents themselves. Topics Covered: Why identity became the primary attack surface — and why SIEMs, EDRs, and cloud tools can't fully see itThe three-database architecture: PostgreSQL (structured) + ClickHouse (time series) + Neo4j (identity graph)Identity resolution: mapping one person across multiple IDPs, SaaS apps, local accounts, and SSO gapsMoving from AWS Neptune to Neo4j — deep graph traversal, the GDS library, and performance at scale- Neo4j Aura managed service as a force multiplier for a small startup teamHow the detection engine uses graph traversal to combine identity, permissions, and activity in a single queryAI agents writing Cypher via a custom tool — token efficiency vs. equivalent SQL (25k vs. 200k tokens per query)The Icite MCP server and graph as a natural fit for agentic infrastructureNon-human identities: tracking AI agent permissions and detecting drift vs. human accessWhat's next: attack path analysis, blast radius scoring, and posture based on permission structures

  3. Aug 21

    Episode 1: Papr

    Shawkat Kabbara is the founder and CEO of Papr, the context intelligence layer for AI. Shawkat has spent most of his career in search and machine learning with roles at Microsoft (Bing), Yahoo, and Meta (Facebook app search) and most recently at Apple, where he was the product founder of the App Intents Swift SDK powering Apple Intelligence Actions, helped launch Vision Pro, and optimized ML models to run on memory-constrained devices. He started Papr to solve a problem he kept hitting himself: AI systems can find similar content, but they can't reason over the relationships that actually drive business decisions. Today Papr's graph-native memory, built on Neo4j, powers AI agents for companies in regulated industries where provenance and auditability aren't optional. Papr.ai is a context intelligence platform that gives AI agents long-term memory through a graph-native architecture built on Neo4j. Papr powers memory and retrieval for customers in fintech, commerce, healthcare, and insurance, turning unstructured data into queryable knowledge graphs via developer-friendly memory policies and a GraphQL API. In this episode Shawkat walks through a before-and-after: 164 daily sales reports stuck as flat text, then the same data as a commerce graph an operator can query in real time.The core question every guest answers: *describe the moment you realized a graph was the right tool.*If your stack is straining against the questions you actually want to ask, this one's for you. What "context intelligence" means for AI agentsWhy flat text fails at scale for memory and retrievalBuilding a graph-native memory layer on Neo4j Memory policies and the GraphQL API developer experienceThe before-and-after: 164 sales reports → a queryable commerce graphServing fintech, commerce, healthcare, and insurance use case

About

Every startup is born to solve a problem. The hard part is everything that breaks on the way there. The Connected Startup is a monthly podcast about those roadblocks, and the founders who discovered a graph was the way through. Each episode traces one company's path from the wall they hit to what they could finally build once their data matched the shape of the problem. We ask every guest the same question: describe the moment you realized a graph was the right tool.