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

# 07.1 overview

# Projects Overview

A **Project** is the highest-level container in BindAI.

Projects organize everything required to build, run, and deploy AI applications, including agents, workflows, tools, knowledge, memory, scheduling, and configuration.

As applications grow, projects provide a structured way to manage all resources in one place.

***

# What is a Project?

A project groups related AI components into a single solution.

Conceptually:

```text theme={null}
Project

├── Applications

├── Agents

├── Workflows

├── Tools

├── Knowledge

├── Memory

└── Configuration
```

Everything needed by an AI application lives inside a project.

***

# Why Projects?

Small prototypes may consist of only a single agent.

Production systems often include:

* multiple applications
* dozens of agents
* reusable tools
* knowledge bases
* scheduled workflows
* shared configuration

Projects provide the structure needed to manage these components together.

***

# Project Architecture

A typical BindAI project looks like this.

```text theme={null}
Project

↓

Applications

↓

Agents

↓

Tools

↓

Language Models
```

Supporting resources such as workflows, knowledge, and memory are shared across applications when appropriate.

***

# Applications

A project can contain one or more applications.

Example:

```text theme={null}
Project

├── Customer Support

├── Internal Assistant

├── Sales Automation

└── Analytics
```

Each application serves a different purpose while sharing common infrastructure.

***

# Shared Resources

Projects allow components to be reused across applications.

Examples include:

* tools
* workflows
* knowledge bases
* configuration
* scheduled jobs

Sharing resources reduces duplication and simplifies maintenance.

***

# Workflow Management

Projects own workflow registration.

```text theme={null}
Project

↓

Workflow Registry

↓

Workflow Executor
```

Applications can execute registered workflows without needing to recreate them.

***

# Tool Registry

Projects also maintain a shared tool registry.

```text theme={null}
Project

↓

Tool Registry

↓

Agents
```

Multiple agents can safely reuse the same tools.

***

# Scheduler

Projects include a workflow scheduler.

```text theme={null}
Project

↓

Scheduler

↓

Scheduled Workflows
```

Recurring automation is managed centrally rather than inside individual applications.

***

# Knowledge

Projects provide a place for shared knowledge resources.

Conceptually:

```text theme={null}
Project

↓

Knowledge

↓

Agents
```

Knowledge may include documentation, policies, manuals, or other indexed information.

***

# Memory

Projects may also contain shared memory resources.

```text theme={null}
Project

↓

Memory

↓

Applications
```

Different applications can use different memory providers while remaining part of the same project.

***

# Configuration

Project configuration defines project-wide settings.

Examples include:

* project name
* environment settings
* shared services
* provider configuration

Configuration helps keep deployments consistent.

***

# Running an Application

Applications are executed through the project.

Conceptually:

```text theme={null}
Project

↓

Application

↓

Agent

↓

Response
```

The project acts as the entry point for execution.

***

# Project Structure

A typical project directory might resemble:

```text theme={null}
my-project/

├── applications/

├── workflows/

├── tools/

├── knowledge/

├── memory/

├── configuration/

└── templates/
```

The exact organization may vary depending on the project's complexity.

***

# Scaling Projects

As projects grow, additional applications and workflows can be added without changing the overall architecture.

```text theme={null}
Project

├── App A

├── App B

├── App C

└── Shared Infrastructure
```

This modular structure supports long-term maintenance.

***

# Best Practices

* Organize related applications into a single project.
* Share reusable tools instead of duplicating them.
* Register workflows centrally.
* Keep project configuration separate from application logic.
* Store knowledge and memory as shared resources when appropriate.
* Use descriptive project names and folder organization.

***

# Summary

A BindAI Project is the foundation of an AI solution.

It organizes applications, workflows, tools, knowledge, memory, scheduling, and configuration into a single, cohesive structure that is easy to develop, maintain, and deploy.