Read your codebase like a senior engineer.
Releap Lens is codebase intelligence for the rest of the team. Ask natural-language questions about how your product works and get cited, file-and-line answers — then turn them into engineering tickets with real context.
Read-only access to your code. We never write to your repositories. Free plan: 1 repo, 25 queries / month.
Trial limits are enforced before query retrieval. The request is scoped to the workspace plan, then checked against monthly query usage.
We never write to your repositories. We never modify your code, your branches, or your permissions.
Lens reads, understands, and explains. Read-only is enforced at the GitHub App permission level, not at the application layer. See the full security model →
What Lens does
Lens answers questions about your codebase and turns those answers into engineering tickets. It is not an IDE plugin and not a coding agent.
Cited answers, never guesses
Every answer points to specific files and line ranges in your repo, pinned to the exact commit Lens read. No hallucinated functions, no invented APIs.
Tickets with engineering context
Turn a question into an epic with child stories, acceptance criteria, code references, and a fix prompt. Export to GitHub Issues, Linear, Jira, or Aha!.
Read-only, by design
Lens never writes to your repositories. We read code, indexes, and connected docs. We never modify your code, your branches, or your permissions.
Bring your own LLM
Route prompts and embeddings through your own OpenAI-compatible endpoint. Customer data stays under customer control, with your DPA.
How it works
Three steps from connecting a repo to a cited answer.
Connect a repo
Install the Releap GitHub App, pick the repos and branches Lens can see. Default-deny: a repo is invisible to Lens until you opt in.
Lens indexes the code
AST-aware chunking via tree-sitter — functions, classes, modules — embedded into pgvector. Webhook-driven incremental reindexing keeps the index current.
Ask. Cite. Ticket.
Ask a question, get a cited answer, optionally turn it into a structured ticket draft and export it to your tracker. No engineer required to triage.
Who Lens is for
Anyone on a software team who needs to understand the codebase without reading the codebase line by line.
Product managers
Answer "how does this actually work?" without pinging engineering on Slack. File a ticket with the right code references already attached.
Customer-facing teams
Support and CS get cited answers about behavior in the actual codebase, not last quarter’s help center article.
Engineering leaders
Triage incoming tickets faster: every defect comes with file references and a fix prompt your team or coding agent can act on.
Founders and operators
Read your own product without scheduling a meeting. Audit how a flow works, where a value is computed, what changed in a release.
Connect a repo. Ask a question. See the citation.
Free plan: 1 repo, 25 queries per month. Upgrade when your team outgrows it.