# Releavo > Releavo is a workspace where a software team and its AI take a product from idea to release. One doc chain (brief, PRD, UX spec, architecture, epics, readiness check, stories), each drafted by Releavo's agent and approved by the person whose role owns it; approval is enforced in the database. It connects to Jira, Confluence, Linear, Notion, GitHub, GitLab, Azure DevOps, Figma and Sentry, follows repositories and updates stories as code lands, and can build a story in its own dev box with Claude Code, pushing only to its own branch. Claude Code, Cursor, ChatGPT and other MCP apps connect to it at https://releavo.app/mcp. Cloud or self-hosted. ## Product - [Home](https://releavo.app/): what Releavo does, by role and by stage of delivery - [Pricing](https://releavo.app/pricing): Free, Team and Pro plans, AI credits, self-hosted licences - [Use Releavo from AI apps](https://releavo.app/connect): connecting Claude Code, Cursor, VS Code, Claude and ChatGPT over MCP ## Guides - [Connectors: how they work](https://releavo.app/guides/connectors): What a connector is, who can add one, what Releavo may do with it, and where your sign-in is kept. - [Jira & Confluence](https://releavo.app/guides/jira-confluence): Bring in issues, sprints and pages, or send this project's stories and docs out, and keep both in step. - [Linear, Notion and Sentry](https://releavo.app/guides/linear-notion-sentry): Sign in once; Releavo reads issues and cycles, pages and databases, or production errors. - [Use Releavo from your AI apps](https://releavo.app/guides/ai-apps): Claude Code, Cursor, VS Code, Claude, ChatGPT or any app that speaks MCP: it works with your projects as you, builds stories in your repo and keeps Releavo current. - [Releavo writes the code](https://releavo.app/guides/coding): Switch coding on and Releavo builds a story itself, in its own dev box, and opens a draft pull request under your name. - [How Releavo follows your code](https://releavo.app/guides/how-code-is-followed): What happens between a push or merge request and a story moving on the board. - [GitHub](https://releavo.app/guides/github): Install the Releavo app on your organization or account; pick the repositories it may see. - [GitLab](https://releavo.app/guides/gitlab): gitlab.com with a sign-in, or your own GitLab with an access token. Releavo adds the webhooks itself. - [Azure DevOps](https://releavo.app/guides/azure-devops): Paste your project's address, sign in with Microsoft, and Releavo sets up the service hooks. - [Figma](https://releavo.app/guides/figma): Show live designs in docs and stories, let Releavo read them, and pair the plugin when you want it to edit. - [Any MCP server](https://releavo.app/guides/any-mcp-server): Connect your own tools, internal APIs or docs search through a remote MCP server. - [Your own model](https://releavo.app/guides/own-model): Run a workspace's AI on your Anthropic key, Bedrock, Foundry, OpenRouter, or a model you host. - [Self-hosting](https://releavo.app/guides/self-hosting): Install Releavo on your own servers with Docker Compose, choose its model, and activate the licence. ## Templates - [Product brief template](https://releavo.app/templates/product-brief): One page that says what you're building, for whom, and how you'll know it worked. The first doc in the chain, and the one every later doc traces back to. - [PRD template](https://releavo.app/templates/prd): The product requirements document says what the product must do, in requirements you can test. It's built from the approved brief, and the UX spec, architecture and stories all trace back to it. - [UX spec template](https://releavo.app/templates/ux-spec): The UX spec turns the PRD's requirements into flows and screens, including the states designs usually forget: empty, loading, partial and error. It's what the designer draws from and the developer builds against. - [Architecture doc template](https://releavo.app/templates/architecture): The architecture doc says how the system will meet the PRD and the UX spec: what the parts are, what data they own, how they talk, and why you chose this design over the alternatives. - [Epic template](https://releavo.app/templates/epic): An epic is a body of work that delivers one outcome a user would notice and takes more than a sprint. The epic describes the outcome; its stories carry the tasks. - [User story template](https://releavo.app/templates/user-story): A user story is a slice of an epic that fits in a sprint and delivers something a user can see. Its acceptance criteria are how the team, QA and the product owner agree it's done. - [Readiness check template](https://releavo.app/templates/readiness-check): A readiness check answers one question before development starts: is everything the team needs to build this decided, consistent and approved? It ends in a verdict and a list of what blocks it. - [Test plan template](https://releavo.app/templates/test-plan): Test cases come straight from a story's acceptance criteria: at least one per criterion, plus the negative and edge cases from the PRD and UX spec. When something fails, the bug report says exactly how to see it. - [Change request template](https://releavo.app/templates/change-request): A change request is how a change to already-approved scope, behaviour or dates gets decided instead of just happening. It shows what the change touches and what it costs, and leaves the decision with the product owner. - [Release notes template](https://releavo.app/templates/release-notes): Release notes tell users what they can do now that they couldn't before. They're written from the stories that shipped, in the users' words, not the team's. ## Comparisons - [Releavo vs ChatPRD](https://releavo.app/compare/chatprd): Both write PRDs with AI and both connect to Claude Code and Cursor over MCP. ChatPRD is a writing assistant for product managers. Releavo is a workspace for the whole team, where the PRD is one doc in a chain that the right people sign off and that follows the code. - [Releavo vs BMAD Method](https://releavo.app/compare/bmad-method): BMAD Method is a free, open-source set of AI agents that runs inside Claude Code or Cursor and writes the brief, PRD, architecture and stories into your repo. Releavo follows the same chain, but as a shared workspace: product owners, designers and clients work in it without a coding tool, and every doc is signed off by the role that owns it. - [Releavo and Jira Product Discovery](https://releavo.app/compare/jira-product-discovery): Jira Product Discovery is Atlassian's tool for collecting ideas and insights, prioritising them and keeping a roadmap, with Rovo AI built in. Releavo starts where an idea is chosen: it writes the brief, PRD, UX spec, architecture and stories, has each signed off, and keeps Jira in step. - [Releavo vs Linear](https://releavo.app/compare/linear): Linear is issue tracking and project planning for product and engineering teams, with its own agent and coding sessions. Releavo is where the docs before and around the issues are written and signed off: the brief, PRD, UX spec, architecture and stories. It connects to Linear rather than replacing it.