STEP 1
Create a workspace
Sign up at releap.app/signup. No credit card is required for your 30-day Pro trial.
Getting Started
From a new workspace to your first cited answer, ticket, KB page, release note, MCP-assisted agent workflow, or VS Code handoff. Releap is read-only codebase intelligence by default.
STEP 2
Connect GitHub
Install the Releap GitHub App, choose the repositories Releap can see, and pick the branches to index. Repositories are default-deny — Releap retrieves nothing you have not explicitly enabled.
STEP 3
Ask a question
Use natural language. Releap answers with citations to files, line ranges, KB pages, release artifacts, and connected product context when those sources are available.
OVERVIEW
The delivery loop
Every surface shares the same grounded context — understand, plan, capture, implement, verify, document, communicate — so teams never re-explain the codebase at each step.
- Cited answers feed tickets, epics, and KB pages
- One context spans chat, planning, docs, and release notes
ASK
Chat & cited answers
Ask how a flow works, where a limit is enforced, or what changed. Releap retrieves from the sources visible to the workspace and answers with citations you can inspect.
- Multi-source: code, KB, release notes, Jira, Confluence, Aha!
- Application and branch scope; thread memory across follow-ups
- Action hints turn an answer into a ticket, plan, or doc
PLAN
Tickets, epics & planning
Turn a question into a ticket draft or a full epic in Planning Mode, with the evidence kept close to the request.
- AC, code references, story points, and a suggested fix prompt
- Export to GitHub Issues; Jira, Linear, and Aha! on Business+
- Branch handoff + draft PR when Releap Code is enabled
KNOW
Knowledge Base
Turn durable answers and tickets into internal KB pages — searchable, retrievable in chat, and flagged stale when cited source files change.
- Generated sections you edit and publish with your team
- A first-class retrieval source for future answers
- Attachments and confirmed agent updates
PUBLISH
Public Docs
A separate publish surface for customer-facing documentation, shipped as independent Public KB snapshots that are safe to share outside the workspace.
- Snapshot publishing hides drafts and private citations
- Custom domains on Business and Enterprise
- Anonymous or token-restricted access
COMMS
Release communications
Draft audience-specific release notes from tickets, milestones, code context, and approved KB content — approvals and history preserved.
- Audience-aware drafts from one underlying change set
- Approvals, destinations, and publication records
- Retrievable history of what you told users
AGENTS
MCP & agentic tools
A Model Context Protocol endpoint at /mcp lets Claude Code, Cursor, Cline, Codex, and other agents use Releap as grounded context and workflow.
- query_codebase, read_chunk, create and compare tickets
- Drive planning, verification, and KB/release updates
- Workspace-scoped keys or OAuth — audited and plan-limited
EDITOR
VS Code extension
Brings the working queue, Releap chat, ticket handoffs, local acceptance checks, and MCP setup into the editor.
- @releap chat: /ask, /ticket, /handoff, /verify
- Copy handoff prompts and MCP config snippets
- Run acceptance checks and record results on the ticket
USAGE
Monthly AI usage
AI-powered actions draw from one workspace pool; reading existing content and exporting already-created work does not. 1M-token usage blocks:
- Pro — $10 per block
- Business — $8 per block
- Growth — $6 per block
- Enterprise — contracted usage-block terms
- Workspaces
- The tenant boundary for members, repos, queries, tickets, settings, and audit rows.
- Applications
- Product surfaces or services inside a workspace that organize sources and answers.
- Sources
- Repositories, Confluence spaces, Jira projects, and Aha! products Releap may index.
- Knowledge Base
- Authenticated team knowledge — generated, edited, searched, embedded, staleness-checked.
- Public Docs
- Intentional unauthenticated or token-restricted docs published from Public KB snapshots.
- Release comms
- Audience-specific notes, approvals, destinations, and publication records tied to tickets.
- MCP clients
- Agentic tools connected via workspace-scoped API keys or OAuth tokens.
- Releap Code
- The opt-in workflow that applies a ticket to a non-default branch and opens a draft PR.
- Citations
- File, line, and source references attached to answers and tickets.
- API keys
- Workspace-scoped credentials for MCP access and programmatic clients.
Preparing a rollout or security review? Start with the security model or contact our team — we respond within one business day.