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

# Core concepts

> The eight things Devic is made of, and how they fit together.

Devic has a small number of building blocks. Everything else is a combination of them.

***

## The two things that do work

> [card] Assistant
>
> Converses. Someone — or something — sends a message and gets an answer, in a conversation that persists. Real-time, embeddable, the natural fit for support, sales and any interface a person uses.

> [card] Agent
>
> Executes. It is given a task and works through it in a **thread**: planning, calling tools, pausing for approval, finishing. Long-running, autonomous, the natural fit for processes.

The dividing line is not the model or the tools — both have the same access to those. It is the shape of the work: a conversation with turns, or a task with a beginning and an end.

***

## The four things they use

| Block | What it is | Page |
| - | - | - |
| **Tools** | What an agent can *do*: MCP servers, built-in tools, connected apps. | [MCPs](https://docs.devic.ai/devic/mcps/index.md) |
| **Knowledge** | What it can *read*: documents you write and files you upload. | [Knowledge](https://docs.devic.ai/devic/knowledge/index.md) |
| **Memory** | What it *remembers* between conversations. | [Memory](https://docs.devic.ai/devic/memory/index.md) |
| **Environment** | Where it *runs*: shared tools, variables and a real Linux sandbox. | [Environments](https://docs.devic.ai/devic/environments/index.md) |

***

## The two things that organise it

> [card] Project
>
> How work is divided **inside** your account: access, cost and traceability follow the project. See [Projects](https://docs.devic.ai/devic/projects/index.md).

> [card] Tenant
>
> How work is divided **outside** it: your own customers, and the users inside them. See [Multi-tenant](https://docs.devic.ai/devic/multi-tenant/index.md).

> [!NOTE]
>
> These two are easy to confuse and are not the same axis. A project is your internal organisation — who on your team works on what. A tenant is your customer. A single project usually serves many tenants.

***

## How they compose

A support assistant, embedded in your product:

**1. An assistant**

with a prompt and a model.

**2. Knowledge**

attached — return policy, product catalogue, tone of voice.

**3. Tools**

from a connected app, so it can look up a real order.

**4. Memory**

scoped by subtenant, so it remembers each customer and only that customer.

**5. Embedded**

with `@devicai/ui`, authenticated with a [tenant session](https://docs.devic.ai/devic/multi-tenant/tenant-sessions.md) so the customer's identity is proven rather than declared.

An overnight reconciliation process, instead:

**1. An agent**

with a plan and a schedule.

**2. An environment**

with the database CLI installed and the credentials as encrypted variables.

**3. A sandbox snapshot**

so each night starts where the last one left off.

**4. Human in the loop**

on the step that writes, so a person approves before anything moves.

**5. A trigger**

or a schedule, so nobody has to start it.

***

## Three ways to reach all of it

> [card] [Console](https://docs.devic.ai/devic/quickstart.md)
>
> app.devic.ai — build, watch, review.

> [card] [Public API](https://docs.devic.ai/api-reference/introduction.md)
>
> Everything the console does, and what your product calls.

> [card] [CLI and SDK](https://docs.devic.ai/devic/cli/index.md)
>
> The same API from a terminal or a Node backend.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.