---
title: "Heizen Studio"
description: "The AI-native SDLC workspace — requirements, backlog, sprints, wiki, QA and integrations in one project."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.heizen.work/llms.txt
> Use this file to discover all available pages before exploring further.

# Heizen Studio

Heizen Studio is where a project lives end to end: you groom requirements with an
AI business analyst, generate a backlog from them, run sprints, keep the wiki and
bug tracker beside the work, and hand the whole thing to the QA Agent for test
plans, execution and security scans.

Sign in at [studio.heizen.work](https://studio.heizen.work).

## Start here

New to Studio? [Quickstart](/studio/quickstart) takes you from an empty account
to a groomed backlog and a running sprint.

## What's in a project

The project sidebar groups everything by the phase of work it belongs to.

- **Product** — Grooming, scopes, personas and canvas — where requirements are shaped before
they become stories. [Read more →](/studio/product)
- **Delivery** — Sprint board, backlog, bug tracker and work logs — the day-to-day execution
surface. [Read more →](/studio/delivery)
- **Knowledge** — Wiki, files and e-mails — the project's durable context, indexed so the
agents answer from it. [Read more →](/studio/knowledge)
- **QA Agent** — Test plans, repository, automated cases, environments, load testing and VAPT.
[Read more →](/studio/qa-agent)
- **Integrations** — Jira, Confluence, GitHub, Figma and Gmail. [Read more →](/studio/integrations)
- **Secrets and API keys** — Per-project credentials, and keys for programmatic access.
[Read more →](/studio/secrets-and-api-keys)

> **Working from your editor**
>
> Everything here is reachable from Claude Code, Codex, Cursor and other MCP
> clients through the [Heizen MCP server](/mcp) — same data, same permissions,
> no browser.

Source: https://docs.heizen.work/studio/index.mdx