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

# Customer Dashboard Concepts

> Key concepts for models, projects, credentials, observability, and billing

## Concept Map

```mermaid theme={null}
graph TB
    P[Project] --> K[API Keys]
    P --> U[Usage and Billing]
    M[Model Catalog] --> PL[Playground]
    M --> API[API Integrations]
    API --> L[Logs: Metrics and Requests]
    L --> A[Audit and Governance]
```

## Projects as your ownership boundary

Projects are the operational container for keys, usage visibility, and team workflows. Keep environments and teams separated with project-level organization.

## Models and published endpoints

Models in Customer Dashboard are the published, customer-consumable interfaces exposed for downstream use. Model details provide endpoint context and usage snippets.

## Playground-first validation

Playground allows prompt and response iteration before integrating with production code. It reduces integration risk by validating behavior earlier.

## API keys and secure access

API keys provide authenticated access to model endpoints. Keys should be scoped, rotated, and revoked through defined lifecycle workflows.

## Logs: metrics + requests

Logs combine high-level trends and request-level detail:

* **Metrics view**: latency, throughput, token trends, geographic distribution.
* **Requests view**: per-inference details for troubleshooting and verification.

## Usage and billing controls

Usage summarizes spend, tokens, and request volume. Billing alerts enforce proactive guardrails with threshold-based notifications.

## Audit and governance

Audit history provides traceability for operational and security-sensitive actions, helping teams with compliance and incident response.

## Design Principles

<Check>**Self-service first**: users can discover, test, and integrate without waiting on manual ops steps.</Check>
<Check>**Security by default**: key management and project scoping are central workflows.</Check>
<Check>**Operational visibility**: logs, usage, and audit create a complete feedback loop.</Check>