# Introduction

> What Buff is: one platform with three entry points — development, the knowledge space and Buff Code — and where each team should start.

**Buff** is a company AI platform with three entry points. **The knowledge space**: an employee of any department asks a question about the company’s documents and gets an answer with a link to the document, orders a research and keeps a knowledge base — no code needed. **Development**: you set a task in plain language, and an AI agent formulates it, breaks it into subtasks, writes the code, passes the checks and prepares a finished change for acceptance in your repository; a person approves the plan before the start and approves the result. **[Buff Code](/en/docs/buff-code)**: engineers who write code themselves work in the terminal and in the app, on their organisation’s models, knowledge and connections.

## Who it is for

- **Departments without code** — support, sales, legal, HR, finance, marketing, management and product managers — whose answers to “how do we actually do it here” are written down in policies, contracts, spreadsheets and wikis, but finding them takes longer than asking a colleague.
- **Engineering teams** that want to delegate routine, well-defined work — features, refactorings, migrations, test coverage, backlog clean-up — while keeping control over how tasks are set and accepted.

## The basic model

Everything in the product is built around a few entities:

- **Organisation** — the team’s workspace; isolated from other organisations.
- **Development project** and **Repository** — where the work happens and what is connected as code sources; **Space** — a workplace without code, built on the department’s documents (see [Space](/en/docs/quickstart/space)).
- **Task** — the unit of work in a development project: from the request through formulation and decomposition to development and review.
- **Question** and **research** — the units of work in a space: an answer with links, or a verified document based on the company’s documents.

More in [Core concepts](/en/docs/concepts) and the [Glossary](/en/docs/glossary).

## How it works (in brief)

You work in a web application. It is built to keep your code and documents safe: code changes only with your consent, documents are only read — and only those the connection has been given access to. What this means in practice is covered in [Security and privacy](/en/docs/security).

_Illustration: Development: the main screen for working with a task._

_Illustration: Space: a question about the department’s documents and knowledge, an answer with links — read-only._

## Where to start

- **With a repository** — [Quick start](/en/docs/quickstart#with-a-repository): in a few steps you connect a repository, prepare the project and set your first task.
- **Without code** — [Buff without a repository](/en/docs/no-code): an account, a space, the department’s documents and your first question.
- **From a phone** — the [mobile app](/en/docs/mobile) for iPhone and Android: approvals, answers and notifications when you are away from your computer.