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

# Glossary

> Definitions of key terms and concepts used throughout Vybe

An alphabetical reference of terms you will encounter when using Vybe.

***

| Term | Definition |
| - | - |
| **Agent Mode** | The AI's default operating mode where it can create, edit, and delete files, run database queries, install packages, and make changes to your app. |
| **App** | A full-stack Next.js 15 web application built in Vybe. Each app has its own codebase, internal database, and deployment. |
| **App Router** | The routing system used by Next.js 15 (and all Vybe apps). Pages are defined as files in the `src/app/` directory. |
| **Ask Mode** | A read-only AI mode for asking questions and getting explanations about your code without modifying anything. |
| **Client Component** | A React component marked with `"use client"` that runs in the browser. Required for interactivity, event handlers, and React state. |
| **Credit** | The unit of billing in Vybe. AI interactions consume credits based on the model used, reasoning effort, and response length. |
| **Custom API** | Manually configured API credentials stored in Vybe for connecting to services that do not have a built-in integration. |
| **Data Query** | A saved, reusable query against a connected database or integration. Data queries can be shared across apps within an organization. |
| **Deployment** | The process of publishing your app to production, making it accessible at its `.vybe.build` URL for authenticated organization members. |
| **ERD (Entity Relationship Diagram)** | A visual representation of your database schema showing tables, columns, and relationships between them. Available in the Data tab of the editor. |
| **External Database** | A database you own that you have connected to Vybe through the Integrations page. Supports PostgreSQL, MySQL, and Amazon Redshift. |
| **Integration** | A connection to an external service (Slack, Jira, Salesforce, Stripe, etc.) that makes the service's data and actions available in your apps. |
| **Internal Database** | The built-in PostgreSQL database (hosted on Neon) that every Vybe app receives automatically. Managed through Prisma ORM. |
| **Locked File** | A system file that cannot be edited by you or the AI (e.g., `package.json`, `next.config.ts`, `tsconfig.json`). Locked files ensure app infrastructure stability. |
| **Organization** | Your team's workspace in Vybe. All apps, members, integrations, billing, and settings belong to an organization. |
| **Path Access** | Granular access control that restricts specific pages or routes within a deployed app to specific users or roles. |
| **Prisma** | The database ORM used in Vybe apps. Prisma provides a type-safe API for reading and writing data to the internal PostgreSQL database. |
| **Reasoning Effort** | The depth of thinking an AI model applies to a problem. Higher reasoning effort (Medium, High) produces better results for complex tasks but uses more credits. |
| **Recipe** | A pre-configured app starter with specific integrations, guided setup steps, and example database schemas. Recipes help you get started quickly with common use cases. |
| **Sandbox** | The isolated development environment where your app runs during building. Provides live preview with hot reload so you can see changes as the AI writes code. |
| **Server Component** | A React component that renders on the server (the default in Next.js 15). Server Components can access the database, read environment variables, and fetch data directly. |
| **Server Secret** | A unique secret per app (`VYBE_SERVER_SECRET`) used to authenticate server-to-server API calls between Vybe infrastructure and your app. |
| **Shadcn UI** | The component library used in all Vybe apps. Provides 50+ pre-built, accessible UI components including tables, forms, dialogs, and navigation elements. |
| **Template** | A reusable app blueprint created from an existing app. Other members of your organization can use templates to create new apps with the same structure and code. |
| **Thread** | A conversation with the AI about a specific app. Each app can have multiple threads for organizing different features or tasks. |
| **VUT (Vybe User Token)** | A short-lived JWT that authenticates users in deployed Vybe apps. Automatically minted and injected by the platform — you do not need to manage it manually. |
| **Workflow** | A background job or scheduled task powered by Inngest. Used for data syncs, notifications, batch processing, and any operation that should run outside the request/response cycle. |

***

## What's next

* Review the full tech stack: [Tech Stack Reference](/reference/tech-stack)
* Explore AI models: [AI Models Reference](/reference/ai-models)
* Get started building: [Quick Start](/getting-started/quick-start)


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