Serro (Early Access)
Temporal knowledge graphs for fast moving engineering teams
92 followers
Temporal knowledge graphs for fast moving engineering teams
92 followers
Teams are coding faster than ever, and context sharing has become a real bottleneck. Serro serves fast-paced engineering teams by helping them start harnessing the power of their temporal techno-organizational knowledge graphs. Meetings to prompts. Code to reports. Proactive context, automated rollups, and a 10x ROI on coordination overhead. Join our waitlist to lock in an early-bird discount.
Serro (Early Access)
Hey everyone, thanks for checking out Serro. We’re excited to share early access with PH today.
Everyone who signs up in the next 24 hours earns a life-time Early Adopter badge on our platform and you'll get to lock in a 50% discount for your company on the first year pricing regardless of the plan or size of team. If you're pre-funding, please leave a comment - I'll be happy to arrange a special startup discount for you :)
A little bit of context about why I started Serro:
Before Serro, I spent five years at Apple Ops building a data platform that processes production data for every Apple device across thousands of factory lines worldwide. It was deep, high-scale engineering—the kind of work I used to daydream about as a self-taught developer. Going from teaching myself to code → to Apple → to leading teams there was honestly a once-in-a-lifetime experience.
But when I moved from IC onto the management track, I immediately saw something that changed how I viewed engineering teams.
Only about 10% of middle management was actual decision-making. The other 90% was managing technical communication overhead for the team: summarizing, syncing, translating, and stitching together fragments of information just so everyone could stay aligned.
With AI, this problem has escaped management. It’s now a daily developer problem.
Every engineer is coordinating multiple AI agents while staying aligned with teammates who are all moving 10× faster. The bottleneck in modern teams isn’t execution anymore. It’s awareness. It’s how quickly humans and AI can share, understand, and reason about what matters in real time.
We quickly realized RAG alone isn’t enough. Search helps you find things, but it doesn’t help you understand how they changed, why they changed, or how they relate.
So we've taken inspiration from Git.
Git is a temporal change graph. It shows how systems evolve over time, and that simple idea has held the tech industry together for decades.
Serro applies that same idea to your organization.
We build a temporal knowledge graph that connects goals, decisions, conversations, and code into one living system of understanding.
It’s how we envision AI tools will graduate from interns to real teammates.
Git helped us understand code over time.
Serro helps you understand your organization the same way.
Thanks for being here. Start leveraging your organization's temporal context graph with Serro!
@jakejooyoung Congrats on the launch Jake. This is very interesting but I immediately want to know how you deal with infosec. Who needs to know what and how the gaps that appear from the top down will imact a middle management user?
Serro (Early Access)
@zolani_matebese Hey Zolani, thanks for the comment. It's a great question and one of our team's favorite topics to discuss.
On a fundamental layer, we have a strict tenant level isolation, and follow the inherited RBAC inherited from the data original sources (e.g. only specific meeting attendees have access to the transcript material from the meeting).
RBAC inherited from source systems
Encrypted in transit and at rest
Strict multi-tenant isolation
Read-only, scoped access
No permission expansion or lateral visibility
From a UX and product philosophy standpoint, we put a lot of emphasis on making sharing transparent and intentional, so users are always aware of what is being shared and have clear control over it.
It's such a vast topic to cover so I'm not sure if I answered your q. Please feel free to ask any follow on qs or engage with us using the Cal link on our website!
Congrats on the launch! Temporal knowledge graphs for eng teams feel spot-on.
Serro (Early Access)
@zeiki_yu Thanks Zeiki! Glad it resonates!
Pastors.ai
Congrats on the launch! 🙌.
Love the concept of an AI technical project manager working in the background to capture decisions and context 🚀
I wonder what engineering team size is the sweet spot for Serro?
Serro (Early Access)
@joe_suh thanks for the comment and support! We help small teams of 5-10 stay leaner longer regardless of whether the team is in a startup or a large enterprise
Attrove AI
That line is 🔥: “Git helped us understand code over time. Serro helps you understand your organization the same way.”
RAG/search finds artifacts, it doesn’t explain what changed, why it changed, and what it impacted across goals, decisions, convos, and code. The temporal change graph idea feels like the missing layer.
Curious: what’s your “git blame” equivalent for organizations?
Serro (Early Access)
@monzures Thank you so much!
Yes git blame alludes to a powerful concept in git. It highlights git's usefulness in traceability and helping people understand the context of code evolution. (although fun fact: Fredrik Kuivinen, the original implementer of the feature in Git, expressed in hindsight that "praise" or a more neutral name might have been better and we agree)
So Serro can tell you:
or
or
Hope that answers your question!
Just signed up. Looking forward to it!
Serro (Early Access)
@sangho thanks for signing up! Excited to chat!
Excited for this launch. This is a level of process intelligence that seems to be missing from the market right now, with everyone praying that something like Claude Code or Codex will magically become an expert in human taste and global/corporate context.
Well done, @jakejooyoung and team!
Serro (Early Access)
@lorenzo_swank_ thanks for the support!!
Dude this seems awesome. I hate digging through Slack, docs, and old meetings just to remember what was actually decided or who did what...
Serro (Early Access)
@steve_o_keneev_o Thanks Steve! We're trying to fix the part that devs actually hate