I am building RepoEngine to solve a problem I encountered as a backend engineer. Once a codebase grows into multiple repositories, documents, and teams, it becomes tough to track context or find the code for a specific feature/functionality. Even if it becomes harder to know in which context a decision was taken to implement it that way.

To overcome these issues, I have started building a systematic approach in RepoEngine, which unifies your repositories, docs, and decisions into a knowledge layer you can actually build on (onboarding flows, internal agents, automated docs, etc.).

What it does: - Multiple Repositories at once. ( that's from an organisation's repositories or even from personal profiles' selected repositories) - Ask questions across repos + docs and get answers with citations. - Every answer links to the exact sources (files, Notion pages, Slack threads, Jira tickets, etc.). - It indexes structure/meaning but doesn’t store your source code. - Connect GitHub, GitLab, Notion, Google Drive, Dropbox, Confluence, Slack, Jira, and Linear.

This is early, and I’m actively seeking feedback from people working with large or messy codebases. I really want a product that captures the shared context of decisions/directions taken to build a feature.

Would love feedback on the product direction, integrations you want, and how teams want to use this day‑to‑day. https://repoengine.com