Rivora - The open source engineering memory layer

by
Engineering tools have become increasingly intelligent, but they still don't remember. Rivora is an open source, local first engineering memory layer that connects your engineering activity into durable, searchable memory. Investigate incidents, verify conclusions, learn from previous work, and continuously improve without sending your engineering knowledge to someone else's cloud.

Add a comment

Replies

Best
Maker
📌
Hi everyone! 👋 I'm Sergio, the creator of Rivora. Over the past few years I've watched software engineering become filled with incredible tools. GitHub. IDEs. AI coding assistants. CI systems. Kubernetes. Observability platforms. The problem isn't the tools. The problem is that none of them share memory. Every investigation, debugging session, deployment, architecture decision, and hard-earned lesson gets scattered across pull requests, dashboards, terminal output, chat history, and documentation. The context that helped solve yesterday's problem rarely helps solve tomorrow's. That's why I built Rivora. Rivora is an open source, local first engineering memory layer. Instead of replacing your existing tools, Rivora helps them operate as one engineering system. It turns engineering activity into durable, structured memory by connecting observations, investigations, evidence, conclusions, execution plans, receipts, and outcomes into a searchable history you actually own. What ships today • Local-first runtime • Investigation Workspace • Conversation-first terminal interface • One-shot CLI for humans and coding agents • GitHub, GitHub Actions, Kubernetes, and Sentry connectors • Evaluation, verification, improvement, and learning workflows • Apache 2.0 open source Your data stays yours. There is no required hosted Rivora account. No cloud control plane. Bring your own AI model if you want one. Run everything locally or self-host it yourself. Why launch now? Because I don't want to build dozens of integrations based only on assumptions. I'd much rather build the future of engineering memory alongside the engineers who will actually use it. If you try Rivora, I'd love to hear: • What integrations should come next? • What engineering workflows lose the most context today? • What would make an engineering memory layer genuinely useful for your team? Thanks for checking it out and I can't wait to hear what you think ✌️

finally something that keeps my debugging context across machines without me copy pasting notes everywhere. the local first angle is what sold me, glad i can actually own my engineering memory