Hipocampus
AI operators that own team workflows
Start new thread

Hipocampus - AI operators that own team workflows

by•
Hipocampus is a workflow-ownership layer for teams. It deploys governed operators that automate and own team workflows across fragmented systems, with persistent workflow state, approvals, delegation, escalation, and shared context so work keeps moving across tools and time.

Add a comment

Replies

Best
Maker
📌
Hey everyone 👋 Noureddin here, co-founder of Hipocampus. We’ve been spending the last couple of years building AI systems, and one thing kept coming up over and over again — AI tools are everywhere, but actually getting real work done across them is still messy. You end up stitching workflows together by hand, jumping between tools, and babysitting everything to make sure it moves forward. So we built Hipocampus, AI operators that own team workflows. The idea is simple: give every team an swarm of operators. Instead of just generating outputs, operators actually own workflows, they carry context across tools and time, take actions, keep things moving, and only pull you in when it actually matters. Our goal is to become the single point of contact for how work gets done across your stack. We’re still working closely with teams to shape this, so if you’re dealing with messy, multi-step workflows, I’d genuinely love to hear what’s painful for you. Try it out, break it, tell us what’s missing. I’ll be here all day answering everything 🙌

Seriously cool! This feels like Zapier + Temporal + AI agents combined. Btw what’s been the hardest part in making that actually reliable in production?

Maker

 The hardest part was figuring out how to approach building Hippocampus. Since we both have a background from distributed systems, we realized this was just another distributed systems pattern. This is why we're ahead of the curve when it comes to production reliability, observability, and why we have the strongest harness given our intelligence layer.

The "approvals and delegation" piece — how does that actually work in practice? Like if an operator hits a decision point that needs human sign-off, does it pause and ping someone in Slack, open a task in a PM tool, or does it have its own notification layer? The handoff mechanism seems like where this either clicks or falls apart.

Maker

 The handoff mechanism definitely clicks and it will reply to Slack or Discord, whatever platform the team selects, on top of our own notification layer. The operators are intelligent enough to figure out what works for the team and what channels are appropriate, because it starts by mirroring their workflows exactly.

Persistent state + model-agnostic harness is the right bet — agents that live as ephemeral chats always fall off a cliff past a few hours. Handoff-as-a-task (not a chat relay) is the correct UX primitive. Curious how Hipocampus handles policy drift when the team's approval criteria evolve after the operator has already learned an older pattern.